decisionlisted
Install: claude install-skill radozaprazny/attest
# /decision — why we chose X over Y (DECISIONS.md)
This skill maintains **`DECISIONS.md`** — an **append-only, ADR-lite** log of the project's
notable decisions. Its reason to exist is the **roads not taken**: the alternatives that were
weighed and why they lost — which a git commit message does not preserve queryably.
The skill is **generic** — work with what you actually find in the repo, and assume nothing
about the specific project.
## The control documents — keep them separate
**Anti-duplication:** status → `PROGRESS.md` · rules → `CLAUDE.md` · why-it-exists →
`BUSINESS.md` · why-we-chose-X-over-Y → `DECISIONS.md` · under-what-rules → `COMPLIANCE.md`.
Write each fact in exactly one place. (full table: GUIDE PART 1)
The three "why" docs are the collision point — fence them:
- **BUSINESS.md** = *why the project exists* — a boundary it will never cross is a **non-goal**.
- **DECISIONS.md** = *why this choice beat the alternative* — a technical how/which.
- **COMPLIANCE.md** = *which external rule forces it* — a standing regulatory obligation.
> If you catch yourself recording, as a decision, a boundary the project will never cross →
> that is a Non-goal (`BUSINESS.md`); a rule that binds all future code → `CLAUDE.md`; a
> standing regulatory obligation → `COMPLIANCE.md` (record the *choice* here, cross-reference
> the obligation there by ADR id).
## What rises to a decision (the threshold)
Record **only** a choice with **lasting rationale AND discarded alternatives