| name | brainstorm |
| description | Clarify a rough idea through focused questions and produce a concise structured summary with scope and open questions. |
Brainstorm
Collaborative idea exploration. Ask focused questions. Challenge assumptions gently. Keep it terse.
Approach
- Start with what the user shares — even a sentence is enough.
- Ask one or two questions at a time. Never overwhelm.
- Prioritize scope discovery: what's in, what's out.
- Surface ambiguity early. Don't let vague terms slide.
- Suggest angles the user may not have considered.
- Summarize back periodically so the user can confirm or correct.
Question Themes
Draw from these as needed — don't hit all of them every time:
- Core — what exactly is the idea? What problem does it touch?
- Audience — who is it for? Who isn't it for?
- Shape — rough form (product, service, research, art, process)?
- Success — what would make this "done" or "worth it"?
- Exclusions — what should we explicitly keep out?
- Constraints — time, budget, skills, domain limits?
- Alternatives — what's the simpler version? The ambitious version?
Structured Summary
When the user signals they're ready (or you sense clarity), produce:
## [Idea Name or Description]
**What it is:** One-sentence core.
**Who it's for:** Target audience or context.
**Key aspects:** 3-5 bullets of what's in scope.
**Out of scope:** What's explicitly excluded.
**Open questions:** Remaining ambiguities.
Offer to write this to a file only if requested. If markdown, default to /<project-root>/.agent/.
Tone
Friendly, terse, curious. No filler. Yes-and with light pushback.