---
name: brainstorm
description: Voice-friendly interview that turns a new project, feature, or task into a brainstorm document or task brief, then builds and verifies v1 unless the user chooses another stopping point. Use when the user says "brainstorm", "I have an idea", or wants to talk something through before building it.
---

# Brainstorm

Interview the user about a new project, feature, or task, then turn the conversation into an actionable artifact. Voice-compatible: ask **one open-ended question at a time in plain conversational prose** — no structured question tools, option lists, or bullet walls the user would have to read.

## How to Interview

1. **Open:** "Tell me about the idea — what do you want to build and why?" Skip this if they already explained it.
2. **One question per turn.** Cover, in whatever order the conversation flows: who it's for and the problem it solves, what the v1 must do (and explicitly won't), how they'll know it works, technical constraints or stack preferences, and anything already existing (code, docs, prior attempts).
3. **Reflect back** every few turns: "So what I'm hearing is..." — let them correct you. Push back gently when scope balloons: "Is that v1 or v2?"
4. **Stop interviewing when the goal, v1 scope, and success criteria are clear.** Record unresolved technical choices as open questions rather than prolonging the interview. Distinguish user decisions from assumptions.

## Output

Pick the artifact by size:

- **Project or large feature** → draft a brainstorm doc using [references/brainstorm-template.md](references/brainstorm-template.md).
- **Small feature or task** → write a task brief: goal, requirements, acceptance criteria, out of scope, and any user-specified stopping point.

Read back a 3–4 sentence summary and ask "did I miss anything?", then save to the path they gave or a descriptively named file in the project's usual docs/specs location.

## Continue to the Outcome

**Default next step:** Build the MVP/v1 and keep working until success is verified against the artifact's success criteria. Create a spec or do focused research as needed to support the build; use `create-spec` or `research` if available.

The user can override this default with a different next step or stopping point, such as "brainstorm only", "only create the spec", or "research the options, then discuss with me". Respect that boundary.

Resolve open questions by making a call when there is enough context and the decision falls within the agent's autonomy boundary, researching factual unknowns, or asking the user when their input is needed. Record the resolution and settle blocking questions before dependent implementation. Follow repository instructions and tool permissions; if verification is blocked, explain what remains unverified and what is needed to continue.

## Guidelines

- Conversational and short — your turns should be shorter than the user's.
- Capture their words; don't translate everything into jargon.
- One idea per session. If a second idea emerges, note it and offer a separate round.

Any text supplied with the invocation is starting context.