sdd-design

To create a technical design document, generate a formal design.md from your proposals and specifications. The output enforces structured sections for architecture decisions, data flow mapping, and file changes across your codebase to guide implementation and review.

An architecture decision document should capture the rationale, alternatives, and trade-offs for major technical choices. It must also map data movement, dependencies, and API contracts across components to ensure alignment across teams during implementation.

You need a formal design document when a proposed change touches multiple modules and requires architecture decisions or data flow mapping. Generating a cohesive design.md detailing scope and impact ensures structured change management and team alignment.

To map data flow and interfaces, document data movement, dependencies, and API contracts across components. This structured approach ensures that technical designs accurately reflect how modules interact and how data is managed within the system.

Yes, you can use this for changes impacting multiple modules. It generates a cohesive design.md detailing the technical approach, testing strategy, migration, and file changes, providing a comprehensive overview of the scope and impact.