sddlisted

# SDD: Spec-Driven Development project runner SDD is a way of working with a coding agent where structured spec files, written before any code, drive the agent's behaviour instead of ad-hoc prompting. This skill scaffolds that setup into a repo and runs the loop. It folds in the IDSD refinement: the spec is split by ownership so the human who wanted the outcome keeps owning intent and definition-of-done, and the agent never quietly decides "done" for them. The method in one line: **a permanent constitution gives the agent guardrails, dated feature specs define one shippable phase at a time, and every phase starts with a short intent interview so nothing is built from assumptions.** This skill has two modes. Decide which one applies first. ## Mode detection 1. Look for a `specs/roadmap.md` (the roadmap is the marker of an SDD repo), searching: the current working directory, then a folder the user named, then one level down. 2. Found one and the user's request is about continuing the work (or they just said "let's get started" / "what's next"): **Resume mode**. 3. Otherwise: **Bootstrap mode**. If a `specs/` folder exists but is incomplete (missing mission, tech-stack, or roadmap), treat it as a half-finished bootstrap: fill the gaps rather than starting over. ## Bootstrap mode: set a repo up for SDD ### Step 1: read the ground first Before interviewing, look at the target repo so the questions are informed, not generic: - Is this a new (empty or near-empty) repo or an