questionslisted

# /questions — Populate docs/questions.md Draft or maintain a project's `docs/questions.md`: the small set of policy-relevant questions the research answers. Each question aggregates evidence from multiple hypotheses and maintains a current working answer that evolves as new results come in. These are **synthesis** questions — the "so what?" that motivates the paper and frames the contribution. They sit above the hypothesis layer: hypotheses are testable predictions; questions are what the predictions collectively tell us. ## What questions.md is NOT - Not a staging area for half-formed ideas (that's `thinking.md`) - Not a list of descriptive queries ("what share of cases have X?") - Not a restatement of hypotheses (those have their own doc) - Not a research agenda (keep it to what THIS project answers) ## Arguments - `/questions` — infer project from CWD - `/questions <project-slug>` — run against a specific project - `/questions --update <Q:slug> [--artifact <path>]` — update one question's working answer after new evidence (e.g., from `/connect-results`) - `/questions --audit` — check for stale answers, missing hypothesis refs, orphan questions with no tested hypotheses - `/questions --extend` — propose a new question (requires justification) ## Finding the workspace root The workspace root contains `CLAUDE.md` alongside `projects/`, `pipelines/`, `ideas/`, `research/`. If inside a project, search upward. `$ROOT` for paths; `$PROJ = $ROOT/projects/<slug>/`. ##