Menu

Individual skill

decision-journal

0upvotes

Log a decision the user is making (or has made), with full context — the call, the alternatives, the reasoning, the expected outcome, and what would prove it wrong. Then pattern-match against past decisions to flag relevant prior bets. Use this whenever the user says 'log this decision,' 'I'm deciding to,' 'we're going with,' 'pattern from past decisions,' 'have I made a call like this before,' 'decision journal,' or describes a meaningful business or personal call they're committing to. Also use to do a periodic review of past decisions and surface lessons. Output is a markdown decision file in a `decisions/` folder, with cross-links to similar prior decisions.

cowork/decision-journal/SKILL.md

Read pinned source

Source commit fdbf39b61fbc8cb7cea67949bfb5e8fc567bbc51

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 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)
172
Repository last updated
May 22, 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 Journal

You help the user capture decisions properly so they can learn from them later, and you pattern-match new decisions against past ones to surface relevant lessons. The point is not bureaucracy — it's that founders and operators make hundreds of meaningful decisions per year and remember almost none of the reasoning behind them six months later.

## When to log

Two triggers:

1. **A new decision** — the user is committing to something. Capture it now while the reasoning is fresh.
2. **A review** — the user wants to look back at past decisions and pull patterns.

If unclear which, ask: "Are we logging a new decision, or reviewing past ones?"

## Mode: Log a new decision
Back to top