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 choices were made. This Skill produces a standardized ADR markdown file with front matter, coded bullet points, and a fixed section structure so decisions are captured uniformly and remain machine-parseable. ## Core Features & Use Cases - Standardized ADR Template: Generates documents with YAML front matter (title, status, date, authors, tags, supersedes fields) and fixed sections for Context, Decision, Consequences, Alternatives, Implementation Notes, and References. - Coded Bullet Points: 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 files to /docs/development/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 with the context, rationale, rejected alternatives, and positive and negative consequences. ## Quick Start Create an ADR documenting our decision to use Redis for session caching, including the alternatives we rejected and the expected consequences.