decision-log
Skill0 starsChanged 17 days agoMITView on GitHub
Capture product and cross-functional decisions as clean, searchable log entries — what was decided, by whom, why, what was ruled out, and when to revisit. Use when someone pastes meeting notes, a Slack thread, or an email chain and wants the decisions pulled out, asks to "log this decision," or wants to check whether something was actually decided.
46 other projects use a version of this.
Adopted by
Most recently taken up by
- MichinaoShimizu/kirokutheir own version, first seen Nov 1, 2026
- Nomanriaz786/claude-consulting-teamtheir own version, first seen Nov 1, 2026
- aya-taleb/productivity-skillstheir own version, first seen Nov 1, 2026
- warstellar/agent-skillstheir own version, first seen Oct 24, 2026
- Evan-Daruwalla/claude-skill-suitetheir own version, first seen Oct 20, 2026
- rterakedis/leanwheel-skillstheir own version, first seen Oct 17, 2026
Used with
Projects with it also use product-brief, pre-mortem 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.
erik-kroonSkillproduct-brief
Turn conversation context, codebase findings, and product intent into a PRD-style brief without assuming a specific issue tracker. Use when the user wants a PRD, product brief, feature spec, or implementation-ready product artifact.
Also in 3 projects that use this
Ingramradical235Skillpre-mortem
Pre-mortem analysis, scenario planning, future state narratives, and contingency frameworks. Use before finalizing any Strategy Kernel, when planning major initiatives, or when preparing Plan B triggers.
Also in 3 projects that use this
MicrosoftSkillretrospective
Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.
Also in 4 projects that use this
OpenAISkillmeeting-prep
Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.
Also in 3 projects that use this
Microsoft AzureSkilltest
Also in 3 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 3 projects that use this
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 46
- davekilleen/Dex★ 509same name
- zrosenfield/sharepoint-ai-skills★ 96same name
- GTMify/aigtm★ 25same name
- Sapere-IA/sdd-onboarding-kit★ 19same name
- ulises-jeremias/agent-toolkit★ 19same name
- Fadi88/one-man-startup★ 16same name
- Unabyss/unabyss-skills★ 15same name
- WupfAGI/claude-investment-skills★ 14same name
- lglucas/ai-dev-operating-system★ 12same name
- carlkibler/agent-skills★ 6same name
36 more not listed
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 repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- beta-program-managerSkill
- cross-team-dependency-mapSkill
- customer-advisory-board-prepSkill
- data-request-routerSkill
- deprecation-planSkill
- duplicate-request-mergingSkill
- experiment-logSkill
- feature-flag-trackingSkill
- feedback-taggingSkill
- information-debt-auditSkill
- internal-enablement-briefSkill
- kpi-health-checkSkill
- launch-readiness-checklistSkill
- meeting-to-action-converterSkill
- new-pm-onboarding-packSkill
- pricing-packaging-change-logSkill
- process-documentationSkill
- product-metrics-definitionsSkill
- product-ops-contextSkill
- quarterly-planning-prepSkill
- raci-builderSkill
- release-notes-draftingSkill
- request-intake-triageSkill
- retro-facilitationSkill
- ritual-calendarSkill
- roadmap-hygieneSkill
- sprint-review-summarySkill
- support-escalation-patternsSkill
- tool-stack-auditSkill
- vendor-evaluation-scorecardSkill
- voice-of-customer-digestSkill
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 39 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 18
Read the source and sort every candidate into one of three groups:
- Distinctive: line 24
Only Decided items become log entries.
- Distinctive: line 26
When in doubt, it is not decided.
- Distinctive: line 44
Use the source's reasons. Never add your own rationale.
- Distinctive: line 45
If "Ruled out" or "Why" isn't in the source, write "Not recorded" rather than filling it in.
- Distinctive: line 56
If asked whether something was decided, search the log and the source.
“Common” is measured: kept by at least 6 in 10 of the 39 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 log
A decision log answers "why did we do it this way?" six months from now, when nobody remembers the meeting. Its value depends on separating what was truly decided from what was only discussed.
Before you start
If .agents/product-ops-context.md exists (or .claude/product-ops-context.md), read it first. Use the team, owners, tools, meetings, and metric definitions it already has, and only ask for what's missing or specific to this task. If it doesn't exist, go ahead with what you're given, and suggest running product-ops-context once so the next skill doesn't have to ask.
Step 1: Find the decisions
Read the source and sort every candidate into one of three groups:
- Decided: someone with the authority to decide said yes, and the source shows it.
- Leaning: the group agreed in principle, but nobody confirmed it or a condition is still open.
- Discussed only: raised, debated, or suggested, with no conclusion.
Only Decided items become log entries. List the other two under "Not yet decided" so they don't get lost or mistaken for decisions.
When in doubt, it is not decided. Agreement in a meeting is not a decision unless the source shows who made the call.
Step 2: Write each entry
### [Short decision title, written as the decision itself]
- **Date:** [when it was decided]
- **Decided by:** [person, not team]
- **Decision:** [one or two sentences, specific enough to act on]
- **Why:** [the reasons given in the source]
- **Ruled out:** [alternatives considered and why they lost]
- **Affects:** [teams, products, or documents that need to change]
- **Revisit:** [date or trigger, e.g. "if churn rises above X," or "none set"]
- **Source:** [link or where it came from]Rules:
- The title is the decision: "Launch to all customers on Nov 4," not "Launch timing discussion."
- Use the source's reasons. Never add your own rationale.
- If "Ruled out" or "Why" isn't in the source, write "Not recorded" rather than filling it in.
Step 3: Close with open items
## Not yet decided
- [Topic] — Status: Leaning / Discussed only — Needs: [who has to decide, and what's missing]Checking an existing log
If asked whether something was decided, search the log and the source. Answer with the entry if one exists, or say plainly that no decision is recorded and who would need to make it.
Related skills
- meeting-to-action-converter — capture the actions from the same meeting
- raci-builder — check the decider had the authority
- retro-facilitation — review past decisions in a retro
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.

