Spec-Driven-Development: Instructions file for Claude Code

CLAUDE.md

Auto-read by Claude Code at session start.

Generated by the spec-driven-development skill.

Session startup — read in this order

1. If CONTEXT.md exists — read it first

   • Resume the active task from the resume block
   • Announce which session this is and what you're picking up
   • Do not ask what to work on unless the user interrupts

2. Read requirements.md — the contract for what the system does

3. Read design.md — the blueprint for how it is built

4. Read tasks.md — find the next incomplete [ ] task

If none of these files exist yet, the project has not been specced. Offer to run the SDD skill interview to create them.

---

Hard constraints

• Never implement requirements not in requirements.md
• Never alter the data model without updating design.md first
• Never create files not listed or implied in design.md
• Never mark a task [x] without verifying its acceptance criterion
• Never guess when a requirement is ambiguous — ask instead

---

Divergence protocol

If implementation must deviate from design.md:

1. Stop
2. Describe the conflict clearly
3. Wait for explicit user approval
4. Update design.md FIRST, then implement
5. Record the divergence in CONTEXT.md

---

CONTEXT.md update rules

At the end of each session (or at a natural stopping point):

• Add a session log row: date, one-line summary, files changed
• Update the resume block with the next active task
• Record any divergences from design.md
• Resolve any open questions that were answered

At the start of each session:

• Read CONTEXT.md before doing anything else
• Announce: "Session [N] resuming. Last worked on [task]. Picking up at [task]."

---

Skill mode

If the user wants to generate or update spec files, or set up AI config files, apply the full SDD skill from SKILL.md (if present in this folder). Otherwise operate as a spec-aware coding assistant using the existing files.