Brainstorm

Answer WHAT to build. do-plan answers HOW. This skill does not implement and does not write the plan.

Done: the requirements file is written, the Ready check passed or the user stopped with Open questions listing what is unsettled, and the Next block was shown or a caller return was sent.

Start

The invocation's idea is the subject. If it carries mode:return-to-caller, strip that token and remember caller mode. If no idea was given, ask what to explore and wait.

No idea yet, meaning they asked for options or what to build: ask one question for the area or constraint. Then a short ideas pass. Read the repo's top-level docs and the area that question names, and stop once 3 to 5 options are grounded in what is already there. Each option is one sentence. The user picks one. That pick is the idea. "Surprise me" is a real pick. Take the option most grounded in the repo and say so. Do not write an ideas file. Do not plan. A second question means they need to name an idea. Ask for that instead of interviewing.

If that read finds nothing, say so and ground the options in what the user said.

A flow tree is do-ux-flow-plan, if installed. A throwaway visual is do-show-me, if installed. Attacking the idea is do-redteam, if installed. Name the neighbor and stay on requirements unless the user switches.

Dialogue

One question per turn. Use the harness's blocking question tool when it has one. Ask only a decision the request and the repo cannot settle. Do not re-ask a decision already made.