architecture-decision-record

# Architecture Decision Record (ADR) Skill This skill produces a complete Architecture Decision Record (ADR) following the Nygard format — the most widely adopted standard. ADRs document the reasoning behind significant technical decisions so future team members understand not just *what* was decided, but *why*. ## Required Inputs Ask the user for these if not provided: - **ADR number** (sequential number in your ADR registry — e.g. 012; or "next available" if unknown) - **Decision title** (brief, e.g. "Use PostgreSQL as primary datastore") - **Context** (what situation led to this decision needing to be made?) - **Options considered** (at least 2; if only 1 is given, prompt for alternatives that were considered or ruled out) - **Decision made** (which option was chosen) - **Reason for choice** - **Status** (Proposed / Accepted / Deprecated / Superseded) - **Author and date** - **Team context** (optional — team size, relevant experience, org constraints; helps calibrate formality and depth of the Context section) ## Output Format --- # ADR-[NNN]: [Decision Title] **Date:** [YYYY-MM-DD] **Status:** [Proposed / Accepted / Deprecated / Superseded by ADR-NNN] **Author(s):** [Name(s)] **Deciders:** [Who had final say — individual or team] --- ## Context [3–6 sentences. Describe the situation, constraints, and forces at play that made this decision necessary. Include: the problem being solved, relevant system state, team constraints, timeline pressures, or non-negotiable ...