design

You can generate a reviewable technical design by running a workflow that transforms your spec's requirements.md into a structured design.md artifact. This process snapshots your active spec, loads context, and delegates architecture generation to a reviewer.

A two-stage review workflow runs parallel spec-compliance and code-quality checks against your generated design.md. It uses explicit pass/fail verdicts stored in verification blocks to prevent silent drift from your original requirements.

To ensure architecture review aligns with spec requirements, use a workflow that applies a specCompliance hard gate. This blocks progress until the generated design passes verification checks against the original requirements.

Yes, you can request changes during the approval workflow. The system presents a structured walkthrough summary and supports approval, review reruns, or request-for-changes loops before updating the phase state and proceeding to tasks.

Yes, the design generation process requires state management to snapshot your active spec and update phase state. This ensures the delivery workflow remains reviewable, resumable, and verifiably aligned before proceeding to tasks.

Automated technical design generation stops for explicit approval before tasks, meaning it cannot proceed without human intervention. It also relies entirely on the completeness of your requirements.md and optional research.md inputs.