decision-brief
Skill2 starsChanged 3 months agoMITView on GitHub
Builds a structured decision brief (decision memo) from quantitative survey data (CSV): situation, options with pros/cons backed by data, a reasoned recommendation, risks and assumptions. Result as Markdown to reports/. Use when a decision is due that should be grounded in research evidence. Invoke with your request as the argument, e.g. /decision-brief <decision / question>.
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
- tmusser/context-to-action-skillstheir own version, first seen Sep 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
- tmusser/context-to-action-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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- data-checkSkill
- daten-checkSkill
- entscheidungsvorlageSkill
- executive-summarySkill
- freitext-themenSkill
- hypothese-checkSkill
- hypothesis-checkSkill
- management-summarySkill
- segment-profileSkill
- segment-profilSkill
- survey-contextSkill
- survey-reportSkill
- umfrage-kontextSkill
- umfrage-reportSkill
- verbatim-themesSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Run these from the project root.
- Very specific: line 34
If a context document sits next to the CSV (<name>.context.md, or survey-context.md when the folder holds exactly one CSV), read it first — …
- Distinctive: line 47
If not given, derive 2–4 realistic options (include "status quo / do nothing" as a baseline).
- Distinctive: line 95
Use significance/effect size where group differences drive the decision.
“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 (Decision Memo)
Goal: For the decision named in the user's request, build an actionable brief
in which every option is backed by data and a clear recommendation is given. For
decision-makers, not analysts. Result as Markdown in reports/.
Tool
python3 scripts/survey.py <cmd> [...] [--file CSV]Run these from the project root. If scripts/survey.py is not there, check .claude/scripts/survey.py or locate survey.py in the project.
profile— column overview (always first).freq COL [--by COL2] [--filter "COL=VALUE"] [--sig]— distribution/cross-tab,--sigfor significance + effect size (single × single).text COL [--filter ...] [--sample N]— verbatims/free text as evidence.
COL = index (from profile) or an unambiguous name part.
Survey context
If a context document sits next to the CSV (<name>.context.md, or survey-context.md
when the folder holds exactly one CSV), read it first — this skill benefits from it more
than any other, because it names the pending decision and the audience the brief is for.
Take the situation, the subject and the glossary from it; the figures still come only from
the engine. Its recruiting route and "Who is missing" section belong under risks and
assumptions: an option that looks strong among the people who answered may look different
among those the survey never reached. Expectations listed there are something to test,
never something to support — never let one decide which option wins. If no such document
exists, proceed as before and mention survey-context once at the end.
Approach
- Sharpen the decision. What exactly is being decided? Which options are plausible? If not given, derive 2–4 realistic options (include "status quo / do nothing" as a baseline).
- Profile and find the decision-relevant variables.
- Gather evidence per option. For each option, query the data that argues for or against it (distributions, cross-tabs, significance where relevant, free-text needs). Also quantify the size of affected user groups (impact).
- Weigh and recommend. Compare options on the evidence, give a reasoned recommendation. Expose trade-offs, don't hide them.
- Save the report to
reports/(date +%F+ kebab title, never overwrite) and state the recommendation + path in your reply.
Report format
# Decision brief: <decision>
**Data basis:** <file> · n = <…> · <date>
## Recommendation
Clear statement in 1–2 sentences: which option, and why.
## Situation
Why is the decision due? Relevant data context in 2–4 sentences.
## Options compared
| Option | For (data) | Against (data) | Affected (impact) |
|---|---|---|---|
| A … | … (number) | … (number) | … % of users |
| B … | … | … | … |
| Status quo | … | … | … |
## Rationale
Why the recommended option wins the trade-off — with the decisive numbers.
## Risks & assumptions
What must hold? What could go wrong? Data gaps/uncertainties, including whom the survey
could not reach (from the survey context) and what that could mean for the recommendation.
## Next steps
2–4 concrete, prioritized steps.
## Method
Columns/filters/tests used, in one paragraph.Rules
- Every option needs data (pro and con) — no gut calls.
- State the recommendation unambiguously, but make trade-offs and uncertainty transparent.
- Use significance/effect size where group differences drive the decision.
- Quantify impact (how many users / what share affected).
- Report language = language of the request (default English). Decision-maker tone: short, concrete.
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.

