create-architectural-decision-record

What problem does it solve? Teams often lose track of why architectural choices were made, leading to repeated debates and inconsistent documentation. This Skill produces a consistently formatted ADR that captures context, decision, consequences, and rejected alternatives in a machine-parseable Markdown file. ## Core Features & Use Cases - Standardized ADR Template: Generates a complete ADR with YAML front matter (title, status, date, authors, supersedes fields) and required sections for context, decision, consequences, alternatives, implementation notes, and references. - Coded Bullet Structure: Uses 3-4 letter codes with 3-digit numbers (POS-001, NEG-001, ALT-001, IMP-001, REF-001) so items can be referenced and parsed programmatically. - Sequential File Naming: Saves output to /docs/adr/ using the adr-NNNN-[title-slug].md convention with the next sequential 4-digit number. - Use Case: After deciding to adopt PostgreSQL over MongoDB, ask the assistant to record the decision; it produces adr-0001-database-selection.md documenting rationale, trade-offs, and rejected alternatives. ## Quick Start Create an ADR documenting our decision to use event-driven architecture for the order processing service, including the alternatives we rejected.