councildesignlisted

# /council design ## Instructions Specialised council mode for **design documents, ADRs, and architecture proposals**. Wraps `/council default files:<paths>` (or `/council default prompt:"…"`) with the `design` mode neutrality preamble that focuses members on architectural risk rather than line-level correctness. ### 1. Resolve the artefact The user invoked `/council design <path>` or `/council design`. If no path was supplied, ask (one question per turn): > Which design artefact should the council review? > > 1. A file path (ADR, design doc, RFC) > 2. Multiple files / a directory (the bundler will gather them) > 3. A free-form proposal 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 originating ask Look for the artefact's stated goal — the first paragraph after the title, or a `## Goal` / `## Problem` section if present. That goal is the `original_ask` for the handoff preamble. If the artefact has no goal section, ask the user (one question per turn): > What is the goal of this design? (one sentence — used as neutral > framing for the council, not their analysis) ### 3. Run /council default with the design mode preamble Invoke the matching `/council default` form: - `files:` → `/council default files:<paths>` with `--prompt-mode design`. - `prompt:` → `/council default prompt:"<artefact text>"` with `--prompt-mode design`. `--prompt-mode` is the