sdd-design

To generate a technical design document, you need to provide the proposal and specification documents as input. The skill reads these files and produces a structured markdown design document that captures architecture decisions, data flow, file changes, and technical rationale.

A technical design document should include architecture decisions, data flow, file changes, and technical rationale. Automating this process ensures all necessary information is captured consistently by utilizing your established project standards and conventions during document generation.

Yes, you can enforce project standards and conventions when generating code documentation and design documents. The skill utilizes your project's established standards to ensure the resulting markdown technical design document remains consistent with your existing engineering practices.

The best way to document architecture decisions and data flow is to automate the process using your proposal and specification documents. This ensures the technical rationale and file changes are captured comprehensively in a markdown design document without manual formatting overhead.

Yes, you need to provide proposal and specification documents before automating design document creation. The skill requires reading these inputs to accurately generate a technical design document in markdown format that reflects the proposed software changes.