counciloptimizelisted

# /council optimize ## Instructions Specialised council mode for **optimization targets**: hot paths, slow queries, allocation profiles, or the output of an `/optimize-*` command (`/optimize-skills`, `/optimize-agents`, `/optimize-augmentignore`, `/optimize-rtk-filters`). Wraps `/council default` with the `optimize` neutrality preamble, which focuses members on **ranked**, **evidence-based** suggestions instead of generic "you should profile" advice. ### 1. Resolve the target The user invoked `/council optimize <target>` or `/council optimize`. If nothing was supplied, ask (one question per turn): > What should the council optimize? > > 1. A file or directory of code (perf hot path) > 2. A query / SQL / DB call (paste it now) > 3. The output of an `/optimize-*` command — re-run it now and feed > the report to the council > 4. A free-form description of the bottleneck Pick **1** → `/council default files:<paths>` with `--prompt-mode optimize`. Pick **2** → `/council default prompt:"<query + context>"` with `--prompt-mode optimize`. Pick **3** → run the chosen `/optimize-*` command first, then feed its report file to `/council default files:<report>` with `--prompt-mode optimize`. Pick **4** → `/council default prompt:"<description>"` with `--prompt-mode optimize`. ### 2. Capture the constraint Optimization is meaningless without a target metric. Ask **once** (one question per turn) before invoking `/council default`: > What does "better" mean here? > > 1. Latency (