dev-brainstormlisted

# Developer Pre-Implementation Brainstorm > **Adapted from `superpowers:brainstorming`** — the original skill is the authoritative > source for the full collaborative design process. This adaptation narrows scope to > code-specific decisions a Developer agent must make before executing an implementation loop. Turn a task description into a concrete, approved spec before writing a single line of code. <HARD-GATE> Do NOT write code, create files, scaffold components, or enter any implementation loop until you have presented a spec and the human has explicitly approved it. This applies to every task — bug fixes included. </HARD-GATE> ## Why This Matters "Simple" tasks are where unexamined assumptions waste the most work. A two-sentence spec for a one-function change is fine — the discipline is what matters, not the length. --- ## Checklist Create a task for each item. Complete them in order. 1. **Load project context** — read `docs/project-status.html`, recent commits, affected files 2. **Confirm scope** — is this one task or multiple independent sub-tasks? Decompose if needed 3. **Ask clarifying questions** — one at a time (see rules below) 4. **Propose 2–3 approaches** — with trade-offs and your recommendation 5. **Present spec** — section by section, get the human's confirmation after each 6. **Write spec doc** — save to `docs/specs/YYYY-MM-DD-<slug>-spec.md` and commit 7. **Spec self-review** — scan for placeholders, contradictions, ambiguity (fix inline) 8. **Human