← ClaudeAtlas

decision-historylisted

Record a design decision as a dated, past-tense entry in the repo's docs/decision-history/, or decide whether it clears the filing bar or belongs in the commit body. Use when recording a decision (経緯を残して / ADR にして), or when context-sync finds a buried decision.
shimo4228/claude-harness · ★ 4 · AI & Automation · score 83
Install: claude install-skill shimo4228/claude-harness
# Decision History Write one dated entry per design decision in `docs/decision-history/`. An entry records what was decided, why, and what was known on that day, in the past tense. The current design is the thing itself — rules, skills, hooks, tests, code — and the author's current instruction; an entry is read for the history behind it. A new decision may contradict an older entry; the older entry stays as written. The skill handles the boilerplate (directory detection, sequence numbering, index update) in scripted steps, and the main loop writes the prose. ## Why the main loop writes Deterministic concerns — where the entry goes, what number it gets, which index needs updating — are easy to get wrong silently (number collisions, sub-directory cwd confusion, index drift), so they live in scripted steps. The prose is written by the main loop that holds the decision: rendering to the house template is cheap for it, and the decision packet (Step 3) is the discipline that keeps *decide* and *render* apart — the packet is settled first, the file is a faithful expression of it, nothing is inferred while writing. A writer renders a decision; it does not make one. The evidence script (Step 4.5) is the fidelity check. ## When to Use (filing conditions — canonical) Write a new entry only when the decision meets **all three**: - **hard to reverse** — undoing it means changing other artifacts (skills, rules, hooks, scripts) or public outputs too. Being revertible with git alone