What problem does it solve? Teams often make significant technical decisions without documenting the reasoning, alternatives, and trade-offs, leaving future maintainers guessing why a technology or pattern was chosen. This Skill guides the creation of well-structured Architecture Decision Records (ADRs) that capture the full decision context. ## Core Features & Use Cases - Structured ADR Template: Produces ADRs with Context, Decision, Alternatives Considered, and Consequences sections, saved as docs/adr/NNNN-<slug>.md. - Decision Quality Guidance: Enforces best practices such as documenting at least two rejected alternatives, setting an explicit status, and writing in present tense. - Antipattern Detection: Warns against retroactive justification ADRs, bundled unrelated decisions, and records stuck in "proposed" status. - Use Case: When your team chooses PostgreSQL over MongoDB for a new service, use this Skill to draft ADR-0012 capturing the constraints, the rejected options with their trade-offs, and the follow-up actions linked to affected requirements. ## Quick Start Ask the assistant to draft an ADR for a specific architectural decision, for example choosing an event-driven architecture over synchronous REST calls.
