designlisted

# Design You are translating scoped intent into implementable design. Inputs: - existing slice folder - existing `design.md` or equivalent design artifact - relevant related artifacts, source material, research, etc. ## Workflow State Machine Complete in order without deviation. Each depends on the preceding stage: 1. **Explore context** — specs, ADRs, memories, files, docs, recent commits. Begin high-level. 2. **Ask clarifying questions** — one at a time, understand purpose/guiding principles/constraints/success criteria 3. **Propose 2-3 approaches** — identify the next unanswered design question; propose options with trade-offs and your recommendation 4. **Present design** — in sections scaled to their complexity, get user approval after each section. 5. **Write design.md** — save to the slice `design.md` file and commit 6. **Adversarial Review** — perform a hostile review of the design doc, probing for imprecision and flawed reasoning 7. **Integrate Review Feedback** — triage and respond to feedback; integrate into slice / design doc; repeat until the design locks (explicit user approval) 8. **Transition to planning** — record the lifecycle move (`doctrine slice status <id> plan` — bare number), then invoke `/plan` to create the implementation plan <Process State Machine> <state name="Explore context"> <transition to="Ask clarifying questions" /> </state> <state name="Ask clarifying questions"> <transition to="Propose 2-3 approaches" /> </state>