create-adr

An Architecture Decision Record (ADR) documents major architectural decisions with their context, alternatives, rationale, and consequences. ADRs create a traceable history of why design choices were made, helping teams understand trade-offs and avoid repeating past mistakes in database design, technology selection, and architectural patterns.

Create an ADR by capturing the decision context, listing alternatives with pros and cons, stating your chosen option with rationale, and documenting consequences. The Skill generates a numbered ADR document with decision tracking, assigns a decision number, and outputs the file path for version control and traceability.

Yes. ADRs support linking to code references and establishing ADR-to-ADR relationships for traceability. This lets you connect architectural decisions to implementation, reference earlier decisions, and build a decision chain that guides future architecture choices.

Document the decision context (problem you're solving), all viable alternatives with their trade-offs, your chosen technology or approach with reasoning, and expected consequences for the system. This creates a complete record for future maintainers reviewing why that database or framework was selected.

Yes. The Skill adheres to ADR-001 conventions for numbering and naming, ensuring consistent formatting and structure. Following these conventions makes ADRs discoverable, comparable, and easy to reference across projects and teams.