sdd-system-design

To generate architecture and deployment documentation from a SPEC.md, use the SDD methodology to transform your requirements into ARCHITECTURE.md, DEPLOYMENT.md, SECURITY.md, and COMPLIANCE_MATRIX.md. This approach ensures traceability by linking technical decisions directly to your original requirements.

The SDD methodology for software design traceability is a structured process that transforms a SPEC.md into technical documents while enforcing traceability. It ties architecture, deployment, security, and compliance decisions directly to specific EXG-xxx and ENF-xxx requirements defined in the specification.

Yes, you can use a spec-to-docs workflow to create a security document and compliance matrix. By processing your existing SPEC.md through the SDD methodology, it generates SECURITY.md and COMPLIANCE_MATRIX.md, linking each security decision back to your original functional and non-functional requirements.

Yes, the SDD design phase supports iterative refinement of architecture decisions. After generating the initial ARCHITECTURE.md and DEPLOYMENT.md from your SPEC.md, you can engage in an iterative dialogue to further refine the architecture, security constraints, and technical decisions while maintaining requirement traceability.

You should not use a SPEC.md to architecture generator when you need to write the initial SPEC.md, write application code, perform code reviews, or plan project EPICs. This tool is strictly for producing architecture, deployment, security, and compliance documentation from an already completed specification.