brainstorming

# brainstorming Refine the idea before it touches code. Routed to by `/feature` (before `tdd`) and by `/sprint` (the planning front). ## Pre-flight Read these, or STOP and surface the gap — never guess scope or stack: - `<project-root>/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value), domain vocabulary, and what the project is NOT building. - `<project-root>/.codearbiter/tech-stack.md` — the stack the feature must fit; rule out incompatible designs early. - `<project-root>/.codearbiter/open-questions.md` — existing `[CONFIRM-NN]` items; new ones number sequentially from here. Per-feature and light. NOT decompose's whole-project six-layer interview — one feature, four phases. ## Phase 1 — Frame the problem · gate: BLOCK Take the one-line idea and pin its boundaries before asking anything else: - State the problem in one sentence — the concrete pain, not the proposed solution. - Name the user or caller who feels it, and what "done" looks like to them. - Name what this feature explicitly does NOT do — the boundary that keeps scope honest. - Check the framing against `CONTEXT.md`: it never contradicts the NOT-building list or redefines domain vocabulary. A contradiction is a conflict — surface it, do not reconcile it silently. Gate: problem, caller, and out-of-scope boundary stated and consistent with `CONTEXT.md`. ## Phase 2 — Socratic refinement loop · gate: BLOCK One focused question at a time. Never advance on a hand-wavy answer. Run every a...