Guides · Updated 2026-11-03
Spec-driven development with Claude Code
Spec-driven development in Claude Code means writing the intent down first (a spec), turning it into a plan and small tasks, and having the agent build one task at a time with a review between steps. To close the loop, give the spec a target number and ship it behind a flag, so the work ends in a verdict, not just a merge.
The loop
Spec: what and why, in plain words. Plan: the decisions that are hard to undo, written before code. Tasks: thin slices that each ship. Review: a second reader on every change.
Keeping it on track across sessions
Claude Code forgets between sessions; files do not. Keep the spec and plan in the repository, so every session starts from the same written intent.
Closing the loop
Add one line to the spec: the number this should move, and by when. Ship behind a flag, measure, and record whether it worked. Golden Frijoles does this inside the same Claude Code session.
claude plugin marketplace add golden-frijoles/skills
claude plugin install golden-frijoles@golden-frijolesQuestions
Do I need a plugin for spec-driven development in Claude Code?
No; plan mode and files in the repo get you most of the way. Plugins add structure and keep the plan persistent.