capture-architecture-decisions

To document architectural decisions consistently, use structured Architecture Decision Records (ADRs) that capture rationale, alternatives, and consequences. This Skill automates ADR generation using templates and lifecycle management protocols to ensure consistent recording across software projects.

An Architecture Decision Record (ADR) tracks significant software design choices, including platform selection, security models, and deployment strategies. You need to create an ADR when making technology selections, evaluating system design trade-offs, or defining operational constraints for engineering teams.

To manage the lifecycle of outdated architecture decisions, supersede old ADRs by referencing previous decisions in newly generated records. This Skill maintains decision history by linking superseded documents, ensuring clear documentation for future reference without losing context.

Yes, you can automatically generate ADRs from your current project context. This Skill identifies key architectural decisions in the existing environment and produces corresponding decision records using structured templates, streamlining documentation for technology selection and system design trade-offs.

The best way to record system design trade-offs and operational constraints is through structured ADR templates that explicitly document the rationale, alternatives considered, and consequences. This Skill enforces structured documentation to prevent knowledge gaps and inconsistent decision records.