team-design

To convert an approved requirements brief into a design document, the Skill generates a structured design draft by applying constraint analysis and option evaluation against project context loaded from CLAUDE.md.

The best way to evaluate architectural options is to generate 2-3 design alternatives and a decision log, ensuring traceability and supporting choice for features that introduce new architectural patterns.

Yes, you need an approved brief or pasted requirements to generate architecture documentation, as the Skill uses these inputs to produce a grounded, production-ready design document.

To create a decision record for multi-file feature designs, the Skill updates docs/specs/<feature>/decisions.yaml with a decision log, while the design document is written to docs/specs/<feature>/design.md.

You should use a constraint-driven design document when a feature touches multiple files or introduces new architectural patterns that require structured constraint analysis and option evaluation before implementation.

Yes, you can use templates to structure design docs; the Skill references templates from references/design-template.md to ensure the generated document follows a standardized, production-ready format.