software-architecture-document

To generate a software architecture document, this Skill automates the creation of the 4+1 views: Use Case, Logical, Development, Process, and Physical. It fills a document skeleton with your architecture decisions and required diagrams.

Linking requirements to architecture decisions is handled through an automated traceability matrix. The Skill connects your requirements to architecture decisions and ensures consistency with defined quality attributes for governance.

The best way to enforce a pair-programming workflow for architecture sign-off is to mandate it during final compliance checks. This Skill requires a pair-programming review process to validate ownership boundaries and approve the final document.

Yes, you can use this for compliance checks across multiple iterations. The Skill applies to architecture teams producing documentation iteratively, ensuring mandatory 4+1 views, traceability, and final validation checks are maintained over time.

To start creating a software architecture document from scratch, assemble your inputs and open a document skeleton. The Skill then guides you to fill each of the 4+1 architecture views with your specific decisions and diagrams.