decision-logger
Skill3 starsChanged 18 days agoMITView on GitHub
Capture durable product decision records — choice, evidence, rejected alternatives, boundary, owner, expiry. Use after PRD calls, scope changes, launch/kill, autonomy changes, or when asked to log a decision.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- Hassaan146/claude-skillstheir own version, first seen Jul 25, 2026
- mahiunfiltered/claude-code-skillstheir own version, first seen Jul 8, 2026
- Hussain-Elfalah/Agentic-Skillstheir own version, first seen Jun 4, 2026
- ianklassen/ai-pm-systemtheir own version, first seen Apr 12, 2026
Used with
Projects with it also use andreessen, business-investment-advisor and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Hussain-ElfalahSkillandreessen
Also in 4 projects that use this
Hussain-ElfalahSkillbusiness-investment-advisor
Also in 4 projects that use this
csiddhant796-blipSkillkarpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.
Also in 4 projects that use this
csiddhant796-blipSkillself-eval
Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.
Also in 4 projects that use this
- +8 more from Hussain-Elfalah
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Hassaan146/claude-skills★ 18same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
- ianklassen/ai-pm-system★ 1same name
- mahiunfiltered/claude-code-skills★ 1same name
- darkweb19/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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- company-product-signalsSkill
- company-researcherSkill
- company-strategySkill
- pm-os-onboardingSkill
- brainstormingSkill
- continual-learningSkill
- eval-briefSkill
- exec-communicatorSkill
- experiment-designerSkill
- experiment-writeupSkill
- knowledge-updaterSkill
- launch-postSkill
- launch-readinessSkill
- meeting-to-actionsSkill
- one-pagerSkill
- pptx-creatorSkill
- prd-writerSkill
- stakeholder-updateSkill
- strategy-connectorSkill
- what-ifSkill
- working-backwardsSkill
- writing-clearlySkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
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
- Distinctive: line 8
Write a record only when a future person or agent would make a worse call without it.
- Distinctive: line 19
Do not log status, standup, or reversible trivia.
- Very specific: line 67
If the decision is product-level, also add a one-line row to knowledge/products/<product>/brief.md Key Decisions.
“Common” is measured: kept by at least 6 in 10 of the 5 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 Logger
Write a record only when a future person or agent would make a worse call without it. This is judgment, not meeting minutes.
When to use
- PRD approved or killed
- Scope, ICP, or pricing call
- Launch / iterate / kill
- Autonomy change on an AI surface (alone / confirm / forbidden)
- Eval bar that gates a ship
- "Log this decision" / "why did we decide"
Do not log status, standup, or reversible trivia.
Six fields
- Decision — one sentence
- Evidence — the signal that carried the weight, and what was missing
- Rejected — one or two credible alternatives and why they lost (stops agents re-proposing them)
- Boundary — what the product, agent, or team must not decide alone
- Owner and next test — who watches; smallest evidence that would change the call
- Expiry — date, metric, or event that forces a revisit
Also capture date, type, and tags for retrieval.
Write to
memory/decisions/YYYY-MM-DD_short-slug.md
# [Decision title]
**Date:** YYYY-MM-DD
**Type:** [PRD | Scope | Launch/Kill | Autonomy | Prioritization | Other]
**Tags:** [product, pillar, metric]
## Decision
[1 sentence]
## Evidence
- [What carried the weight]
- **Missing:** [what we still don't know]
## Alternatives rejected
1. **[Option]** — [why it lost]
2. **[Option]** — [why it lost]
## Boundary
[What must not be decided autonomously]
## Owner and next test
- **Owner:**
- **Next test:**
## Expiry
[Date, metric threshold, or event]Show the draft. Confirm before saving. Never overwrite an existing record — if the call changed, write a new one and point at the old.
If the decision is product-level, also add a one-line row to knowledge/products/<product>/brief.md Key Decisions.
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.

