Capture a significant decision in one short document — the context, the options, the choice and its consequences — so nobody relitigates it from memory. Use when making an architecture decision, an ADR, or a hard call worth recording.
--- name: write-a-decision-record category: productivity description: >- Capture a significant decision in one short document — the context, the options, the choice and its consequences — so nobody relitigates it from memory. Use when making an architecture decision, an ADR, or a hard call worth recording. --- # Write a Decision Record Six months after a decision, nobody remembers the constraints that produced it. So it gets relitigated from scratch, or worse, quietly reversed by someone who assumed it was arbitrary. A decision record is a page that survives the people who wrote it. It is cheap to write and it is the difference between an organisation that compounds knowledge and one that rediscovers the same things forever. ## The format ```markdown # 014 — Store session state in Postgres, not Redis Status: Accepted Date: 2026-03-14 Deciders: platform team ## Context What is true that forces a decision now. Constraints, requirements, what we already run, what we cannot change.
You are reading the opening of this skill.
The rest is open to any signed-in account — free included. Reading the library costs nothing.
Shared publicly by the author and open for any use. See the Terms.