decision-logger

ADR (Architecture Decision Record) format logs architectural decisions with structured metadata including context, decision rationale, consequences, and alternatives. This Skill automates ADR creation with automatic numbering and appends entries to docs/DECISIONS.md, capturing trade-offs from technology stack selections and library choices.

Document architectural decisions when selecting technology stacks, choosing libraries, defining project structure, or making significant trade-offs. ADRs preserve project history and reasoning, helping teams understand why past decisions were made and their consequences for future choices.

Yes. This Skill integrates with /craft and /why commands, automatically capturing decisions during those workflows and logging them as ADR entries with consistent structure, metadata, and automatic numbering in your project documentation.

An ADR captures context (situation and constraints), the decision made, consequences (benefits and drawbacks), and alternatives considered. This Skill generates ADRs with automatic numbering and appends them to docs/DECISIONS.md for persistent project history.

This Skill provides standard ADR templates that structure entries consistently with required sections: context, decision, consequences, and alternatives. The template ensures uniform documentation across all architectural decisions in your project.