What problem does it solve? Decisions made during planning, implementation, or review often go unrecorded, leaving future readers unable to understand why the code or scope looks the way it does. This Skill captures those decisions consistently as versioned markdown entities with proper templates, frontmatter, and git history. ## Core Features & Use Cases - ADR vs D-NNNN selection: Guides the choice between an architectural decision record (durable, cross-cutting) and a project-scoped decision entity tied to an epic or milestone. - Template-driven drafting: Drafts the decision body from the canonical templates at .claude/templates/adr.md or .claude/templates/decision.md, then creates the entity with aiwf add so id allocation, frontmatter, and commit trailers are handled in one step. - Supersession handling: Retires replaced decisions with aiwf promote <id> superseded, writing the supersession links only after the replacement is accepted. - Use Case: Mid-implementation you realize a default changed; invoke this Skill to draft an ADR from the template, run aiwf add adr --title ... --body-file ..., promote it to accepted, and mirror the new id back into the milestone spec. ## Quick Start Ask the assistant to record the decision we just made about the authentication approach as an ADR using the aiwf record-decision workflow.
