sdd-design

To generate a design document, provide a change proposal and specs to translate them into architecture decisions and data flow. This creates a structured design.md file capturing technical considerations and file changes.

Maintaining traceability requires linking design decisions directly to original proposals and specs. This ensures an auditable change history by generating a design document that references the source artifacts.

Enforcing consistent design templates is achieved by generating documents under a strict directory structure like openspec/changes/{change-name}/design.md. This enforces the project's persistence contracts, interfaces, and validation rules.

Yes, this design document generator works without external dependencies. It directly translates proposals into architecture decisions and data flow using the existing OpenSpec structure without requiring additional components.

You need to create a design.md file when translating a proposal and specs into a coherent technical design. It is required to capture architecture decisions, data flows, and the rationale behind software changes.

A technical design document should include architecture decisions, data flow descriptions, file changes, and technical considerations. Synthesizing proposals and specs ensures these elements capture the rationale behind the changes.