architectural-decision-log

What problem does it solve?

Capture and preserve the rationale behind major technical and architectural choices so future teams understand the "why" and avoid costly re-evaluation or architectural drift. This skill ensures decisions are recorded with context, alternatives, trade-offs, and explicit status so that design intent survives staff turnover and evolving codebases.

Core Features & Use Cases

• Structured ADR authoring: Guides the user through Context, Decision, Alternatives Considered, Consequences, Status, and links to superseded ADRs.
• Validation rules: Enforces at least two alternatives, requires a clear Status (Proposed/Accepted/Deprecated/Superseded), and mandates consequences for each decision.
• Persistence & traceability: Produces filesystem-safe ADR filenames, saves ADRs under docs/adr, and appends a summary line to docs/skill-outputs/SKILL-OUTPUTS.md for auditability.
• Use Case: When a team chooses a new database or cloud vendor, run this skill to capture the decision rationale, alternatives rejected, and the expected operational trade-offs.

Quick Start

Ask the agent to "Record an ADR for choosing SQLite over PostgreSQL for our internal single-user tool, include context, alternatives considered, consequences, status, and a suggested filename."