capability-brainstormlisted

# Capability Brainstorm ## Kill criteria (read before running) After ≥8 invocations, compute two rates over `state/proposal-metrics.jsonl`: - **Triage-survival rate** — `grep '"type":"triage-verdict".*"evidence_source":"capability-brainstorm"' state/proposal-metrics.jsonl` to find all `triage-verdict` events from this skill. Rate = `CREATE` count ÷ total. Kill if < 25%. - **PROP-acceptance rate** — `grep '"type":"created".*"tags":.*"capability-brainstorm"' state/proposal-metrics.jsonl` to find `created` events tagged `capability-brainstorm`. Cross-reference their `proposal_id` against `responded` events with `"action":"accept"`. Rate = accepted ÷ created. Kill if < 30%. If either rate is below threshold, cut this skill rather than tune it — the signal-to-noise ratio isn't there. ## 1. Gather inputs Read all four sources in parallel — they are independent. **Memory** Read `MEMORY.md` (the index). For each entry whose title or description keyword-matches the current project domain or recent session topics, read that topic file. Aim for 3–5 relevant files; don't read the full corpus. **Capabilities** (issue these three reads simultaneously) - *Skills:* use the harness available-skills list loaded in your context — that is authoritative. Sibling-scan `${CLAUDE_PLUGIN_ROOT}/../*/.claude-plugin/plugin.json` for plugin presence and version metadata only (not skill lists). - *MCPs:* call `ListMcpResourcesTool` to enumerate currently online MCP tools. - *Channels:* read `confi