decision
Skill0 starsChanged 4 months agoMITView on GitHub
Record a durable decision with context, options, rationale, consequences, and a future review trigger. Use when the user asks to document a choice that has actually been made; do not trigger for an unresolved question.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- sohaibt/product-modetheir own version, first seen Nov 8, 2026
- lulufoo/lulu-workflowtheir own version, first seen Nov 6, 2026
- qbicus/skillstheir own version, first seen Oct 25, 2026
- emiljuchnikowski/ai-os-templatetheir own version, first seen Oct 20, 2026
- tsukumogami/shirabetheir own version, first seen Oct 15, 2026
- chrisalehman/bionictheir own version, first seen Oct 13, 2026
Used with
Projects with it also use plan, audit and 1 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.
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 4 projects that use this
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 4 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- sohaibt/product-mode★ 176same name
- aleksander-dytko/ai-pm-workspace★ 34same name
- chrisalehman/bionic★ 9same name
- mhxie/Atelier★ 5same name
- lulufoo/lulu-workflow★ 3same name
- madebypx/PXOS★ 3same name
- Jsnnmsc/10000x-engineer★ 2same name
- roethlar/AgentGovernanceBootstrap★ 2same name
- Tamircohen28/tamirs-superpowers★ 2same name
- yacb2/aidex★ 2same name
7 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 repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- briefSkill
- closeoutSkill
- deskSkill
- doctorSkill
- editorSkill
- grillSkill
- handoffSkill
- morningSkill
- openSkill
- recentSkill
- researchSkill
- rfcSkill
- setupSkill
- shapeSkill
- specSkill
- weekly-reviewSkill
- briefSkill
- closeoutSkill
- decisionSkill
- deskSkill
- doctorSkill
- editorSkill
- grillSkill
- handoffSkill
- morningSkill
- openSkill
- recentSkill
- researchSkill
- rfcSkill
- setupSkill
- shapeSkill
- specSkill
- weekly-reviewSkill
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 16 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
- Very specific: line 8
Read the owner binder, active workstream, related artifacts, and library/templates/decision.md.
- Distinctive: line 14
If linking the artifact changes the workstream, follow the state protocol and create a receipt only for that workstream revision transition.
- Distinctive: line 17
Use the date of the actual decision.
“Common” is measured: kept by at least 6 in 10 of the 16 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
- Read the owner binder, active workstream, related artifacts, and
library/templates/decision.md. - Distinguish a real decision from an unresolved question. If the decision has not been made, capture it in the workstream instead of fabricating an outcome.
- Record context, decision, considered alternatives, rationale, consequences, reversibility, owner, and revisit trigger.
- Store project-specific decisions in the binder. Store truly cross-project, durable decisions in
memory/decisions/. Link rather than duplicate. - Link the decision from the workstream artifact index when it affects active work. Do not create a receipt for the decision document.
If linking the artifact changes the workstream, follow the state protocol and create a receipt only for that workstream revision transition.
Use the date of the actual decision. Separate evidence from inference and do not retrofit certainty.
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.