log-decision
Skill34 starsChanged 22 days agoMITView on GitHub
Record a strategic decision with its reasoning, the alternatives considered, and a date to review the outcome. Use for "/log-decision", "log this decision", or after a significant choice is made.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- holgerleichsenring/specification-first-agentic-developmenttheir own version, first seen Oct 28, 2026
- triet4p/coding-agent-stackstheir own version, first seen Oct 25, 2026
- calven-ai/marketing-as-codetheir own version, first seen Oct 7, 2026
- azborgonovo/ai-skillstheir own version, first seen Sep 7, 2026
- TheKontextCo/kontext-claude-plugintheir own version, first seen Aug 26, 2026
- RndmCodeGuy20/ordnancetheir own version, first seen Aug 25, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- holgerleichsenring/specification-first-agentic-development★ 41same name
- calven-ai/marketing-as-code★ 10same name
- Jerovino/EngineeringOS-template★ 2same name
- azborgonovo/ai-skills★ 1same name
- TheKontextCo/kontext-claude-plugin★ 1same name
- RndmCodeGuy20/ordnance★ 0same name
- triet4p/coding-agent-stacks★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-agentSkill
- build-listSkill
- chart-tufteSkill
- councilSkill
- design-precheckSkill
- document-exportSkill
- handoverSkill
- index-memorySkill
- mcp-debugSkill
- meeting-prepSkill
- memory-debtSkill
- merge-contactsSkill
- morning-briefSkill
- post-callSkill
- reflectSkill
- setupSkill
- system-auditSkill
- tasksSkill
- visual-explainerSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 45
When /log-decision review is run, list decisions whose review_on date has passed, and for each ask: did it work out?
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Log Decision
Capture a decision while the reasoning is fresh, so it can be reviewed honestly later. The point is calibration: a decision logged with its expected outcome can be checked against what actually happened.
Steps
- Gather the decision: what was decided, when, and by whom.
- Capture the reasoning: the key factors, and the single most important one.
- Capture the alternatives: what else was on the table, and why it lost. "Do nothing" counts.
- State the expected outcome and a review date (usually 30 to 90 days out).
- Write to
vault/Decisions/YYYY-MM-DD-<slug>.md.
Format
---
title: [decision]
date: YYYY-MM-DD
review_on: YYYY-MM-DD
status: open
tags: [decision]
---
# [Decision]
**Decision**: [what was decided]
**Why**: [the reasoning, most important factor first]
**Alternatives considered**:
- [option]: rejected because [...]
**Expected outcome**: [what success looks like, concretely]
**Review on <review-date>**: _(left blank until the review)_Reviewing
When /log-decision review is run, list decisions whose review_on date has passed, and for each ask: did it work out? Fill in the review section and set status to validated, mixed, or wrong. Honest reviews are the whole value.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.