doc-generate-adr

An Architecture Decision Record (ADR) is a document that captures significant architectural decisions, their rationale, and consequences. ADRs create a permanent knowledge base, ensuring team members understand past choices and their trade-offs without relying on tribal knowledge or scattered discussions.

Use this Skill to generate a new ADR file with automatic numbering (ADR-001, ADR-002, etc.). Provide a title, and the Skill creates a structured template in docs/adr with sections for Context, Decision, Rationale, Consequences, Alternatives, Status, Date, and Deciders ready to fill in.

ADRs follow a standardized format including Context (problem background), Decision (what was chosen), Rationale (why), Consequences (impacts), Alternatives (options considered), plus metadata like Status, Date, and Deciders. This consistency makes ADRs discoverable and comparable across your codebase.

Create an ADR for significant architectural decisions—technology choices, major refactors, framework selections, or design patterns that affect the system long-term. Use ADRs when decisions involve trade-offs, alternatives, or knowledge that the team needs to reference later.

Yes. Generate an ADR retroactively to document past decisions. Fill in the historical Context, Decision, and Rationale to capture why a choice was made. This creates a record even if the decision predates your Skill adoption.