sdd-design

To generate an architecture design document, provide the change name and artifact mode. The system reads the relevant proposal and spec, then writes a formal design artifact capturing technical approach, data flows, and testing strategy to your filesystem or Engram.

A comprehensive architecture design document should include sections for Technical Approach, Architecture Decisions, Data Flow, File Changes, Interfaces or Contracts, Testing Strategy, Migration or Rollout, and Open Questions to ensure reviewable engineering guidance.

This design documentation approach works across Engram, openspec, hybrid, or none modes. It reads available proposals and specs, then persists the generated design artifact to the appropriate location based on the selected mode.

You can automate creating technical design docs by specifying a change proposal. The system validates content against project conventions and outputs a structured document detailing migration plans, file changes, interfaces, and open questions automatically.

You need a formal design document for change management when implementing modifications that require consistent, reviewable technical guidance. It captures architecture decisions, data flows, and rollout strategies to align engineering teams before implementation begins.

To validate architectural decisions against existing project conventions, the design generation process checks the proposed technical approach, data flows, and file changes against current patterns, ensuring clear rationale and actionable guidance for engineers.