technical-design

You generate a technical design by providing a validated brief.md and acceptance.feature in your directory, which produces a publication-ready technical_design.md documenting scope, API design, and implementation plans.

Creating a technical design requires validated brief.md and acceptance.feature files in the same directory, ensuring the generated design aligns with real code, component docs, and public contracts.

You need a technical design document when planning software projects, design tasks, or architecture changes, converting high-level requirements into actionable design artifacts for implementation execution.

The technical design process validates input prerequisites by checking for brief.md and acceptance.feature before generating, ensuring outputs align with real code and updating state.yaml accordingly.

No, the technical design workflow requires both brief.md and acceptance.feature as inputs, with the acceptance contract ensuring the generated design aligns with public contracts and real code components.

The best way to document API and data design is generating a technical_design.md from validated briefs, referencing existing components and producing actionable artifacts for implementation execution.