sdd-design

You can automatically draft architecture design documentation by analyzing your codebase and a proposed change name to generate a design.md file. This process captures architecture decisions, data-flow diagrams, and file-change rationale tailored to your project.

The best way to generate data-flow diagrams and file-change plans is to use an automated design doc tool that reads your codebase and orchestrator inputs. It directly produces design rationale and architectural artifacts ready for team review.

Yes, this design doc generator supports persisting architecture decisions via Engram, OpenSpec, or hybrid backends. It emits the generated design.md content directly to your chosen backend for consistent document storage and retrieval.

Yes, you can use this to create a design rationale document when evaluating a proposed change. It requires access to the codebase and the orchestrator's change-name to produce comprehensive architecture documentation and file-change plans.

To document architecture decisions and data flows after a change proposal is approved, trigger an automated design generation skill against your codebase. It instantly produces a complete design.md capturing all rationale and data-flow diagrams for review.

Generating technical design documents for large codebases requires sufficient access to the project files and accurate orchestrator mode inputs. If codebase access is incomplete, the resulting data-flow diagrams and file-change plans may lack necessary context.