spec-phase-orchestrationlisted

# Spec Phase Orchestration ## When to invoke - Starting a new project and deciding which documents the spec phase produces. - Multiple documents / sections are in flight and you need to decide the order of progress. - User asks "design or foundations first", "can we proceed with prerequisites unresolved". ## Default decisions ### 5 files + `meetings/` directory ``` <repo>/ ├── README.md # Project entry point ├── docs/ │ ├── foundations.md # Engineering substrate (language version, modules, CI, L10n, secrets) │ ├── design.md # Product spec §What + technical design §How (unified) │ ├── plan.md # TDD-ordered checklist │ └── methodology.md # Claude agent application practices (living doc) └── meetings/ └── {YYYY-MM-DD}_{topic}.md ``` Default: these live in the same repo as the code. A separate `<project>-spec` repo is a deviation for teams that need spec review gated independently of the code repo — not the default. Don't split further: - No separate spec.md / rfc.md / tasks.md (folded into design.md / plan.md) - No `adr/` directory; major decisions land directly in design.md or foundations.md (open one only if real need arises) ### Progression order ``` foundations.md §1..§N (one section at a time) → design.md §What (product spec) → design.md §How (technical design) → plan.md (TDD-ordered) → implementation phase begins ``` **Rule**: don't write §How before design.md §What passes; don't write imple