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. **Recorded intent — fail-soft, exempt from the read-or-STOP rule above (ADR-0025).** Also consult, when present: the `decisions/` index (titles via `decision-log.md` or the filename listing — load a full ADR body only when its subject touches this feature) and `plans/02-phased-build-plan.md`'s section headings (plus `plans/01-architecture-breakdown.md` when the feature touches component boundaries or integrations). Index-first, never a bulk read. A missing file or directory here is NOT a gap to surface and never a STOP: record `intent: silent — no decomposition record` in the running notes and proceed. Per-feature and light. NOT decompose's whole-project six-layer interview — one feature, five phases. Depth scales with the feature, not the ceremony: a small feature earns a short pass through every phase, never a skipped one. A spec can be five sentences; it cannot be zero — ...