What problem does it solve? Technical decisions made during development are often forgotten or poorly documented, leaving future maintainers without context on why a technology or pattern was chosen. This Skill captures those decisions in a structured Architecture Decision Record (ADR) format. ## Core Features & Use Cases - Structured ADR Generation: Produces records with status, context, decision statement, positive/negative/neutral consequences, and alternatives with rejection reasons, based on MADR and Nygard (2011). - Automatic Numbering and Filing: Scans docs/adr/ for existing records, assigns the next ADR number, saves to docs/adr/ADR-{NUMBER}-{slug}.md, and updates the ADR index. - Use Case: After deciding to adopt PostgreSQL over MongoDB in a design discussion, ask for an ADR and receive a complete, numbered record documenting the context, trade-offs, and rejected alternatives. ## Quick Start Ask the assistant to create an ADR documenting your recent technology or architecture decision, providing the title, status, and deciders.