create-architectural-decision-record

What problem does it solve? Documenting architecture decisions is often inconsistent or skipped entirely, leaving teams without a record of why technical choices were made. This Skill produces a standardized ADR markdown file with a fixed template, sequential numbering, and machine-parseable structure. ## Core Features & Use Cases - Standardized ADR Template: Generates documents with YAML front matter (title, status, date, authors, tags, supersession links) and required sections for context, decision, consequences, alternatives, and references. - Structured Consequence Tracking: Uses coded bullet points (POS-001, NEG-001, ALT-001, IMP-001, REF-001) so both positive and negative outcomes are machine-parseable and easy to reference. - Sequential File Naming: Saves output to /docs/adr/ using the adr-NNNN-[title-slug].md convention with the next available 4-digit number. - Use Case: After choosing PostgreSQL over MongoDB for a new service, provide the context, decision, alternatives, and stakeholders to produce adr-0003-database-selection.md ready for review and version control. ## Quick Start Create an ADR for our decision to adopt event-driven architecture, including the context, chosen approach, alternatives considered, and the stakeholders involved.