decision-brief
Skill2 starsChanged 59 days agoMITView on GitHub
Create a lightweight decision snapshot from messy workplace context and supporting evidence.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- parker-brown-family/agent-skillstheir own version, first seen Nov 8, 2026
- rajasdevel/outcomeboundtheir own version, first seen Nov 1, 2026
- zommuter/dotclaude-skillstheir own version, first seen Oct 28, 2026
- hollandkevint/thinkhaven-method-kittheir own version, first seen Oct 20, 2026
- oswarld/notion-skillstheir own version, first seen Sep 23, 2026
- kayspiegel/survey-insight-skillstheir own version, first seen Aug 16, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- oswarld/notion-skills★ 11same name
- ryancproduct/product-ai-toolkit★ 4same name
- zommuter/dotclaude-skills★ 4same name
- kayspiegel/survey-insight-skills★ 2same name
- Ootto-AI/claude-reporting-skills★ 1same name
- parker-brown-family/agent-skills★ 1same name
- hollandkevint/thinkhaven-method-kit★ 0same name
- rajasdevel/outcomebound★ 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brief-meSkill
- clear-askSkill
- follow-up-draftSkill
- meeting-to-actionsSkill
- reduce-to-factsSkill
- status-updateSkill
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 7 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 29
Treat analytics outputs as evidence, not as a separate analytics workflow.
- Distinctive: line 36
Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the …
- Distinctive: line 38
Use the smallest useful output.
- Distinctive: line 40
When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a …
- Distinctive: line 43
Keep unresolved approvals, owners, timing, and blockers explicit in the recommendation.
- Distinctive: line 44
Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.
“Common” is measured: kept by at least 6 in 10 of the 7 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-brief
Purpose
Build a lightweight decision snapshot from mixed workplace context, ticket history, and evidence.
Use For
- Lightweight decision support
- Recommendation requests
- Turning debate and evidence into a clear next step
Inputs
- Notes or context thread
- Ticket or project context
- Supporting evidence
- Hex or other data output
- A
reduce-to-factsledger or conversation-state record
Guardrails
- Read before write.
- Treat analytics outputs as evidence, not as a separate analytics workflow.
- Separate source-backed evidence from assumptions.
- Make trade-offs and reversal cost visible.
- Surface source gaps and uncertainty.
Portable Output Contract
- Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the suggested next action.
- Use the smallest useful output.
- Label assumptions and preserve source gaps, source anchors, and confidence labels.
- When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a fact, decision, commitment, owner, or deadline without new source support.
- Keep unresolved approvals, owners, timing, and blockers explicit in the recommendation.
- Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.
Output
- Recommendation
- Decision needed
- Options
- Trade-offs
- Evidence
- Risks
- Reversal cost
- Next step
Success Standard
The snapshot should help someone make or frame a decision within 5 minutes.
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.