Spec-Driven Development Specs live in . They are the source of truth for architectural decisions, API contracts, and implementation scope. Implementation and specs must stay in sync — neither leads exclusively. Core Loop Before Starting Work 1. Find the spec. Search for files matching the feature: 2. Read the full spec. Understand scope, decisions, API contracts, and open questions before writing code. 3. If no spec exists and the task is non-trivial (new module, new API, architectural change), ask the user whether to create one first. During Implementation - Reference spec decisions — don't…