decision-records
Installation
SKILL.md
Decision Records
A decision is not made until a future maintainer can read it. Log it before the task continues — the record is part of the work, not an afterthought.
The log is the agent understanding
Code and plans show what was built; only the record carries why. A fresh agent, or a subagent about to be dispatched, that reads docs/adr/ and docs/fdr/ inherits the reasoning behind the codebase — how and why it is the way it is — and builds on it instead of re-deciding. Process skills run the work; this pack keeps its reasoning for the next agent.
Route every decision to its record
| What was decided | Skill |
|---|---|
| Architecture or tech: stack, storage, data models, protocols, APIs, security, deployment | adr |
| A feature: what it does for users, its design choices, permissions, rationale | fdr |
| Audit all architecture records for drift | adr-review |
| Audit all feature records against the codebase | fdr-review |
Ambiguous call? The axis is reach: a choice that other features or services inherit is architecture (adr); a choice only this feature feels is a feature decision (fdr).