decision-journal
Skill114 starsChanged 10 months agoMITView on GitHub
Create structured records of decisions with expected outcomes, probabilities, and quit conditions. Use for important decisions.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- crissmoldovan/agent-skillstheir own version, first seen Oct 15, 2026
- megandmartin/agent-skills-repotheir own version, first seen Jul 24, 2026
- ba0918/claude-skillstheir own version, first seen Jul 9, 2026
- Xipher-Labs/walter-ostheir own version, first seen May 21, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Xipher-Labs/walter-os★ 8same name
- megandmartin/agent-skills-repo★ 3same name
- crissmoldovan/agent-skills★ 2same name
- ba0918/claude-skills★ 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 repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assumption-mappingSkill
- assumption-prioritizationSkill
- atlassian-jira-syncSkill
- backend-designSkill
- brainstormingSkill
- challenging-stakeholder-questionsSkill
- competitor-analysisSkill
- crux-diagnosisSkill
- davciSkill
- decision-reversibilitySkill
- difficult-conversationsSkill
- executive-update-reviewSkill
- experiment-designSkill
- frontend-designSkill
- google-calendar-schedule-checkSkill
- granola-meeting-syncSkill
- hidden-agendasSkill
- hypothesis-designSkill
- ideas-summarySkill
- influence-strategiesSkill
- interview-cleanupSkill
- jtbd-clusteringSkill
- jtbd-extractionSkill
- limit-based-strategySkill
- linear-issue-syncSkill
- llm-coding-guardrailsSkill
- mece-analysisSkill
- meeting-power-dynamicsSkill
- message-framing-commsSkill
- opportunity-solution-treeSkill
- ost-intakeSkill
- ost-target-selectionSkill
- power-mapSkill
- prd-writingSkill
- problem-structuringSkill
- root-cause-analysisSkill
- signal-identificationSkill
- slack-message-checkSkill
- spec-writingSkill
- stakeholder-risk-reviewSkill
- structured-product-strategySkill
- systematic-debuggingSkill
- tddSkill
- value-chain-mappingSkill
- verificationSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create structured records of decisions for learning and accountability.
- Distinctive: line 12
When making important decisions that you want to track and learn from.
- Distinctive: line 23
Consider short and long-term
- Distinctive: line 49
Leave blank initially, fill in later:
- Distinctive: line 56
After outcomes are known:
- Distinctive: line 63
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Decision Journal
Create structured records of decisions for learning and accountability.
When to Use
When making important decisions that you want to track and learn from.
The Framework
Record these components for each decision:
1. Expected Outcomes
List 3-5 possible outcomes:
- Best case scenario
- Most likely scenario
- Worst case scenario
- Consider short and long-term
2. Probability Estimates
For each outcome, estimate likelihood (must sum to 100%):
- Outcome A: X%
- Outcome B: Y%
- etc.
3. Key Assumptions
List 3-5 critical assumptions:
- What beliefs underlie this decision?
- Which, if wrong, would change the outcome?
4. Base Rates
Research relevant statistics:
- What's typical for this type of decision?
- Historical data or industry averages?
- What do similar situations suggest?
5. Quit Conditions
Define 2-3 triggers to abandon or change course:
- Clear, measurable indicators
- Specific thresholds
- Timeline checkpoints
6. Actual Results
Leave blank initially, fill in later:
- What actually happened?
- Which outcome occurred?
- Were assumptions valid?
Review Process
After outcomes are known:
- Compare predictions to reality
- Identify where thinking was wrong
- Extract lessons for future decisions
When Not to Use
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
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.