architectural-decision-records

Document architecture decisions by generating lightweight ADRs that capture context, consequences, and risk tracking. This skill reviews your system descriptions to surface missing rationale and alternatives for technology or pattern choices.

Identify missing architecture decisions by checking your system design for gaps across observability, resilience, security, scalability, consistency, deployment, testing, and performance. This skill analyzes your diagrams to surface undocumented areas and prompt focused questions.

Yes, you can generate an ADR from an existing architecture diagram. The skill applies to architecture diagrams, system descriptions, and codebases where rationale or risk areas are missing, producing sequential ADRs by prompting one focused question at a time.

Track risk areas and consequences by producing lightweight ADRs following an architecture review. The generated ADRs record the trade-offs behind choices like PostgreSQL or REST, documenting what risks remain and why specific boundaries were chosen.

You need to create an Architecture Decision Record when you want to capture the why behind technology, boundary, and pattern choices. It is particularly useful after architecture discussions to ensure rationale, alternatives, and trade-offs are formally documented.