Spec-driven development workflow for Claude Code: brief → design → tasks → implement (optionally as an autonomous loop) → review → ship.
/plugin marketplace add hamochi/claude-spec-plugin
/plugin install spec@spec
| Command | Purpose |
|---|---|
/spec:init |
Initialize .spec/ in the current project |
/spec:new |
Start a new feature spec (creates a worktree) |
/spec:design |
Technical design from the brief |
/spec:tasks |
Generate the implementation plan — review it before running |
/spec:implement |
Start or resume implementation |
/spec:loop [id] [--max-iterations N] |
Autonomous implement loop until all gates pass |
/spec:cancel-loop |
Cancel the active loop |
/spec:review |
Review implementation against the spec |
/spec:ship |
Merge into the source branch, clean up worktree |
/spec:amend, /spec:realign, /spec:status, /spec:switch |
Maintenance |
/spec:spec |
Pick up where you left off |
Specs moved from spec/ to .spec/. An existing project needs:
git mv spec .spec
and its CLAUDE.md paths updated (spec/design.md → .spec/design.md, and so
on). Specs whose .cursor still reads tasks keep working — the loop accepts
that phase and advances it.
Also in 2.0: team mode and the parallel-execution annotations are gone (they
never fired); /spec:loop starts from either the tasks or implement phase;
and it now refuses a plan that was edited after the loop started.
commands/– slash commandsreferences/task-format.md– how tasks.md is writtenhooks/– Stop hook that keeps/spec:looprunningscripts/– helpers (list-open-specs.sh,setup-spec-loop.sh)
Requires jq for the loop hook.