design-doc-generate

To generate a design doc for high-complexity work items, run the design-doc-generate workflow from a Validate-mode work item. It automates the creation of formal design documents, reducing hand-written planning time and improving traceability.

An automated design document includes a structured summary, key decisions, technical approach, risk assessment, and an implementation checklist. It requires capturing options, trade-offs, and justifications to guide implementation.

You need formal design documents with rationale and risk analysis for high-complexity work items requiring checkpoint design. This ensures decisions across domains are captured with options, trade-offs, and justifications for traceability.

Yes, you can use design-doc-generate to manage domain modeling and implementation plans. It implements a structured process with decision capture and domain modeling to produce a comprehensive implementation checklist.

Generated design document artifacts are saved at the designated checkpoint path for review and iteration. The output artifact is automatically saved at .specs-fire/intents/{intent-id}/work-items/{id}-design.md.

The best way to capture technical decisions and trade-offs is using a rationale-driven design generation process. It requires capturing options, trade-offs, and justifications within a formal document to guide implementation effectively.