What problem does it solve?
Architectural decisions and trade-offs are often discussed informally and lost in PRs, issue threads, or personal notes; this Skill provides a consistent, discoverable record so teams can understand what decisions were made, why, and when to revisit them. It prevents ad-hoc changes from drifting the architecture and makes rationale available for future contributors and code reviews.
Core Features & Use Cases
- Create ADRs: Fill the project's ADR template and save a sequentially numbered file under docs/adr with a clear title, status, confidence, context, decision, consequences, and alternatives.
- Query & Summarize: Search existing ADRs or summarize the current architectural stance before implementing or reviewing code.
- Supersede & Maintain: Guide the workflow for creating superseding ADRs, updating statuses immutably, and regenerating the ADR index to keep the decision log accurate.
- Standards & Quality Checks: Enforce naming conventions, template completeness, diagram standards (structured text diagrams), and the ADR quality checklist before finalization.
- Seed & Bootstrap: Assist bootstrapping ADRs from seed files and guide initial review and contextualization for a new project.
Quick Start
Create a new ADR titled Use Modular Monolith as Default Architecture using the ADR template and save it to docs/adr/0002-use-modular-monolith-as-default-architecture.md.