Design to Build
Step 1 — Mode Detection
Before anything else, check the repo for existing docs.
Fresh start — neither CONTEXT.md nor docs/ARCHITECTURE_PLAN.md exists:
→ Go to phases/DESIGN.md
Resume — both files exist:
→ Read CONTEXT.md, KNOWLEDGEBASE.md, docs/ARCHITECTURE_PLAN.md, and docs/PROGRESS.md
→ Identify the current active phase in docs/PROGRESS.md
→ Jump directly to phases/BUILD.md at the correct phase
Phases
| Phase | Purpose | Sub-skill references |
|---|---|---|
| Design | Grill session → lock decisions → create docs | /grill-me, /systems-design, /architecture-and-api |
| Build | Per-phase TDD implementation + clean code review | /tdd, clean-code-reviewer |
| Review | Pre-merge review + security audit before shipping | frontend-pre-merge-reviewer, backend-pre-merge-reviewer, security-auditor |
Full instructions for each phase:
- Design session → document creation
- Per-phase build workflow
- Review and ship workflow
Document Roles
| File | Purpose | Lifecycle |
|---|---|---|
CONTEXT.md |
Domain language glossary — canonical terms for this project | Established in Design phase; updated only when new terms are resolved |
KNOWLEDGEBASE.md |
Working memory of product intent + relevant engineering context for the current initiative | Created in Design phase; updated when decisions are confirmed or new constraints surface |
docs/ARCHITECTURE_PLAN.md |
Full plan: all decisions, phases with checkboxes, risks, future work | Created in Design phase; checkboxes tick as phases complete; nothing else changes |
docs/PROGRESS.md |
Active working state: current phase, open tasks, what is next | Created in Design phase; shrinks as phases complete; deleted or archived when done |
Templates for all documents: templates/