decision-log
Skill1 starsChanged 19 days agoLicence not identifiedView on GitHub
Maintain a lightweight DECISIONS.md log of durable, material decisions in persistent agent workspaces. Use when a decision has actually been made and preserving its rationale would matter to future work, especially when it changes or clarifies prior requirements, structure, workflows, conventions, strategy, or other lasting assumptions. Applies to software projects, product and design work, research, knowledge bases, and other persistent workspaces. Do not use for routine execution choices, cleanup, formatting, naming, transient fixes, or brainstorming before a decision is made.
46 other projects use a version of this.
Adopted by
Most recently taken up by
- CharleneTStrain/product-ops-skillstheir own version, first seen Nov 8, 2026
- 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
- 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 repository3 other files it gives its agents.
- brand-naming-to-handoffSkill
- deslopSkill
- diataxis-checkSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. 0 are common, 18 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 39 edited versions we read keep these.
18
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“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.
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.