design-doc

Automate design document creation by initiating a workflow that requires a product brief and PRD review. The process guides you through generating design documents with required sections, multiple design alternatives, and trade-offs before storing them in docs/design/.

Enforce design discipline by integrating an automated workflow that mandates PRD review and formal design-document generation. This ensures alignment checks and approval steps are completed before development begins, preventing missing upfront design.

Yes, you need a product brief and a PRD to start the design documentation workflow. The process targets feature planning by requiring these inputs to guide the generation of design documents and validate necessary trade-offs.

Validate design documents by checking YAML frontmatter, section structure, and approval steps. The workflow ensures compliance with documentation standards by verifying these elements during the formal design-document creation process.

Yes, the design document workflow ensures multiple design alternatives with trade-offs are included. It guides design leads to generate these alternatives alongside alignment checks and approval steps within the formal document.

Generated design documents are stored in the docs/design/ directory. The workflow references PRD and design templates to ensure the resulting design files comply with documentation standards and required section structures.