design

Author a codebase-grounded feature design document by following a four-phase flow: explore and interview, draft, resolve open questions, and iterate. This process ensures your design defines concrete requirements, architecture references, and acceptance criteria.

Iterate on a design doc by triggering the iteration flow, which revisits open questions and updates the design file. This refines the existing architecture references and requirements to produce an updated, kickoff-ready pipeline state.

Codebase exploration works by grounding the design interview and drafting phases in actual project code. This mechanism ensures the generated design document references existing architecture and accurately defines concrete feature requirements.

Yes, the design process generates a .design/<slug>.md file and a pipeline state file specifically ready for kickoff. This output ensures your feature design transitions directly into downstream development workflows.

No, the design process explicitly captures unresolved items as open questions to resolve during iteration. This approach lets you finalize the initial draft while tracking specific architectural or requirement uncertainties for later.

Authoring design docs without codebase exploration risks missing concrete architecture references and accurate acceptance criteria. Grounding the document in actual code ensures the feature design defines feasible requirements and resolves true open questions.