brainstormlisted

# brainstorm Turn a fuzzy problem into a structured set of candidate ADRs and plan items. This skill is **generative and read/propose-only** — it never writes ADRs or plan files directly. On approval it hands each candidate to the **new-adr** and **new-plan** skills. ## Step 0 — Preconditions and context 1. Confirm the repo is bootstrapped (or note that the output can seed a fresh run of the **bootstrap** skill). 2. Read `CONVENTIONS.md` for ADR shape and lifecycle, and skim `INDEX.md` + existing ADRs so candidates don't duplicate or contradict what already exists, and so dependencies point at real ADRs. ## Step 1 — Understand the problem Ask for the goal/feature/problem if not given. Probe for scope boundaries, constraints, and the regulatory/quality concerns that matter for this repo. Do not start decomposing until the goal is clear. ## Step 2 — Decompose Produce a candidate list. For each candidate ADR: - Proposed number (next available, contiguous), working title, shape (capability vs. technology if the repo splits). - One-line scope — the single decision it captures. - Dependencies on other candidates or existing ADRs. **One decision per ADR.** If a candidate bundles several decisions, split it and say why. If a candidate is really an existing ADR needing revision, say that instead of proposing a new number. ## Step 3 — Order the work Propose a plan ordering (which `plan/todo/` items, in what sequence) respecting the dependency edges. Note where w