design-doc-generate

To generate a formal design doc for high-complexity engineering work items, invoke this Skill during the plan-review phase to automatically produce a structured document capturing decisions, domain models, and implementation checklists.

A checkpoint-ready architecture design document should include structured sections for decision rationale, domain models, identified risks, API contracts, and an implementation checklist to guide stakeholders through validation.

You need to create a formal design document before coding when a high-complexity work item requires capturing decisions, risks, and implementation steps upfront for checkpoint review and approval in the planning flow.

To structure API contracts and domain models for a requirements checkpoint review, apply a template-driven approach that enforces formal sections for decision rationale, risks, and implementation checklists.

Yes, you can automate design document generation for software architecture planning by invoking this Skill during plan validation to output a reusable, checkpoint-ready artifact for selected work items.

Yes, this design doc template captures risk assessment and decision rationale, enforcing a structured format that includes domain models, API contracts, and implementation checklists for formal validation.