architecture-docs

Architecture documentation drift is prevented by applying drift-detection checks alongside C4 diagrams and runbooks to keep architecture knowledge synced with system changes. This skill provides templates and signals to maintain living docs.

Architecture Decision Records for complex systems are best structured using Michael Nygard style templates to capture decisions that are hard to reverse. This skill provides ADR format guidance to document and audit these choices effectively.

C4 model diagrams are generated using provided diagram templates and references to keep system boundaries clear for teams building complex software. These templates synchronize visual models with the architecture narrative.

Runbook templates can onboard engineering teams quickly by providing README scaffolds that maintain consistency across architecture documentation. This skill generates runbook skeletons to scaffold your repository documentation.

Formal architecture documentation is needed when building complex software systems that require synchronized architecture narratives and visual models. It ensures ADRs, C4 diagrams, and runbooks remain accurate and auditable.