councilanalysislisted

# /council analysis ## Instructions Specialised council mode for **local analysis artefacts** — `/project-analyze` output, audit reports, codebase scans under `agents/evidence/analysis/`. Wraps `/council default files:<path>` with the `analysis` neutrality preamble that focuses members on **critiquing the analysis itself** (dedup, evidence quality, roadmap-readiness) rather than re-reviewing the underlying code. The synthesis output is shaped for direct consumption by `/roadmap-create` — Top-N consensus findings + per-finding metadata (`evidence-grade`, `roadmap-ready`, `supporting-citation`). ### 1. Resolve the analysis artefact The user invoked `/council analysis <path>` or `/council analysis`. If no path was supplied, ask (one question per turn, per `ask-when-uncertain`): > Which analysis artefact should the council review? > > 1. A file path under `agents/evidence/analysis/` (`.md` or `.json`) > 2. Multiple files (one analysis split across sections) > 3. Free-form analysis text in the chat — paste it now Pick **1** or **2** → use `files:` mode of `/council default`. Pick **3** → use `prompt:` mode of `/council default`. ### 2. Capture the upstream-analysis goal Look for the artefact's stated goal — the first paragraph after the title, a `## Goal` / `## Scope` section, or the analyzer command that produced it (often in the file header). That goal is the `original_ask` for the handoff preamble. If absent, ask the user (one question per turn): > What was the goal o