Individual skill

decision-log-setup

Set up the team decision log that ends relitigation — the one-line-per-decision format (what, why, who, when, reopening rule), the capture moments wired into existing rituals, and the lookup habit that makes it pay. Use when asked set up a decision log, we keep re-deciding the same things, where do decisions get recorded, or new people keep asking why we do X. Produces the log format, the capture wiring, the reopening rule, and the retrieval habits.

skills/decision-log-setup/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Decision Log Setup Skill

Teams re-decide because decisions evaporate: made in a meeting, mentioned in a thread, remembered differently by everyone, and relitigated the moment someone new (or someone persistent) asks "wait, why do we…?" The decision log is the cheapest institutional memory there is — one line per decision (what, why, who, when, and the reopening rule) — but logs fail as shelf-ware unless *capture is wired into existing moments* (the meeting's last five minutes, the thread's landing) and *retrieval becomes reflex* ("checked the log?" as the first response to why-questions).

## What This Skill Produces

- **The format** — the five-field line, with the two-sentence-why discipline and the option-we-rejected field that does the anti-relitigation work
- **The capture wiring** — the existing moments ([decision-meeting-format](../decision-meeting-format/SKILL.md) closes, [thread-to-decision](../thread-to-decision/SKILL.md) landings, 1:1 calls) that now end with a log line
- **The reopening rule** — what reopens a decision (new information) and what doesn't (new mood, new people)
- **The retrieval habits** — the log-first reflex, the onboarding tour, the link-not-relitigate response

## Required Inputs

Ask for these if not provided:
Back to top