brainstorm

name	brainstorm
description	Use before building anything non-trivial — new features, architectural changes, multi-file modifications. Explores intent, requirements, and design before implementation.

Brainstorm

Go from a rough idea to a concrete design through conversation. Explore the problem space before converging on a solution.

1. /ground yourself first — your first question should show you've read the code
2. Ask one question at a time. Understand what and why, not just what to build.
3. Propose 2-3 approaches with honest trade-offs — if you can't name a real downside for your recommendation, you haven't thought hard enough
4. Converge on a design. Go deeper on anything hard to reverse.
5. If it spans multiple sessions, capture to docs/plans/YYYY-MM-DD-<topic>-design.md. Otherwise, the conversation is the artifact.

Do not jump to plan mode or implementation until the design direction is agreed.

Once the design is agreed, /iterate.

$ARGUMENTS