decision-brieflisted

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>.
kayspiegel/survey-insight-skills · ★ 2 · Data & Documents · score 76

Install: claude install-skill kayspiegel/survey-insight-skills

# 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, `--sig` for 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 dec