architecture-skill

To create software architecture documentation, input your current system description to generate a detailed plan capturing architecture layers, decision rationales, risks, and dependency mappings. This structured documentation ensures team alignment and reduces system ambiguity.

The best way to retrofit existing systems is through retrospective analysis, which supports retrofitting current architectures to validate accuracy and identify gaps. This process improves clarity and ensures your documented decisions remain falsifiable and ownership-bound.

System documentation enforces decision discipline by ensuring architectural decisions are falsifiable, ownership-bound, and well-annotated with switch criteria. This discipline integrates directly into phased planning to facilitate safer deployment and multi-year system alignment.

Yes, you can use this for both greenfield design and system retrospection. It facilitates the creation and validation of architectural documents, supporting new system builds while allowing existing systems to be retrofitted for improved accuracy and gap identification.

No specific dependencies are required to generate an architecture plan. You simply input your current system description, and the tool guides you through capturing architecture layers, decisions, and dependencies without needing external frameworks or libraries.

Automated system documentation does not replace human architectural validation but structures it. While it guides capturing layers and enforcing decision discipline, architects must still manually verify dependency mappings and switch criteria to ensure safer deployment planning.