Interactively refine a feature idea through Socratic questioning before planning.
Refine a feature idea through structured critical thinking before it becomes a plan. This is a conversation, not a monologue — ask questions, wait for answers, push back, iterate.
Get the idea: Use $ARGUMENTS as the starting point. If empty, ask the user what they want to build.
Explore the codebase first: Before asking anything, use Read, Grep, and Glob to understand the relevant parts of the codebase. Ground every question in reality, not hypotheticals.
Run the brainstorm loop — repeat until the idea is solid:
a. Restate the idea in your own words to verify understanding. Expose any ambiguity.
b. Ask hard questions (2-4 at a time, not a wall of 10):
c. Don't move forward until the user responds.
d. Push back when answers reveal:
e. Propose alternatives when you see a better path. Compare trade-offs concretely.
Spawn the brainstorm agent (via Task tool with subagent_type: brainstorm) if deeper analysis is needed — for example, when the feature touches many files and you need a thorough risk assessment before continuing the conversation.
Converge: When the idea is well-defined, produce a summary:
Problem: [What user problem this solves]
Solution: [Concrete approach, grounded in the codebase]
Scope: [What's in v1, what's deferred]
Key decisions: [Choices made during brainstorm and why]
Risks: [Remaining concerns to watch for during implementation]
Ready for: /blueprint <one-line goal>
path/file.ts:42, this pattern suggests..."/blueprint is for/blueprint invocation