comet-design
Comet Phase 2: Design
After the entry returns layout, use comet-classic/reference/classic-layout.md to resolve each logical root. Reuse this protocol if it is already in context. Route all OpenSpec CLI calls through the adapter and use the bound <classic-*> roots for file paths; do not run an extra root show first.
Prerequisites
- An active change exists and its required Open artifacts have passed checks.
- Runtime is in the design phase. Resume existing design work where applicable; a design file alone does not replace user confirmation.
Document responsibilities: proposal records goals and scope; spec defines behavior and acceptance requirements; the Design Doc records technical decisions; the plan describes implementation steps; tasks.md records completion. Extend an existing
design.mdin place instead of creating another copy of the design. Use the file referenced bydesign_docas the formal technical design, preserving a different path already recorded for an older change. Other files reference that design rather than maintaining duplicate decisions.
Steps
0. Entry Check
Use the supported Comet CLI described in comet-classic/reference/scripts.md. When resuming from any entry, first follow comet-classic/reference/context-recovery.md to check recovery state: