Example walkthrough

The repo ships a complete worked example — a Todo CRUD API taken from vision → spec → clarify → plan → tasks → approve → implement — so you can see real output before running the kit yourself.

Browse it on GitHub: examples/todo-api/.

What to read, in order

1. inputs/vision.md — the human’s WHAT/why.
2. inputs/tech-environment.md — language, framework, constraints.
3. constitution.md — the project’s principles.
4. specs/001-todo-crud/spec.md — the feature spec (WHAT).
5. plan.md — the technical plan (HOW) + companions.
6. tasks.md — the executable checklist.
7. state.md — the gate source of truth (spec + plan approved → gate OPEN).

The gate moment

In state.md, note that 001-todo-crud’s specify and plan rows read approved. That — and only that — lets the PreToolUse hook allow code edits for this feature. Before those approvals, any attempt to edit application code is blocked with an explanation. That is the whole point: AI proposes, a human approves, and approval is enforced, not hoped for.

SpecForge builds itself

Beyond the example, the repo carries a committed specforge/ store produced by running the full lifecycle on the repo itself to ship its Operations phase — constitution, audit trail, and specs/001-operations-phase/. The kit eats its own dog food.

Reproduce it

/specforge:init
/specforge:specify   "Todo CRUD API with list, create, complete, delete"
/specforge:clarify   # answer the questions file
/specforge:approve specify
/specforge:plan
/specforge:approve plan     # ← gate opens here
/specforge:tasks
/specforge:analyze
/specforge:implement