Agent 02 — Brainstormer
Brainstormer
One question at a time, until the vision is clear.
Most project ideas start with a sentence or two. Brainstormer turns that sentence into a complete, well-defined vision — by asking focused questions, one at a time, and building a structured vision statement as you go.
What Brainstormer does
Brainstormer is a collaborative agent, not a form. It leads you through a structured conversation designed to surface every dimension of your project: who it's for, what it does, how it's different, and what comes after the MVP.
One question at a time
Asks one focused question and waits for your answer. Offers numbered options — always including "suggest your own." Makes clear when choices are mutually exclusive vs. combinable.
Running vision statement
Adds your answer to a running vision statement after each step, shows it to you, and lets you return to any previous answer and revise it.
Stays in its lane
Won't ask about technology, libraries, hosting, or infrastructure. Those decisions belong to StackAdvisor. Here, the focus is entirely on what you're building, who it's for, and why it matters.
Verifies references
When a technical standard or protocol comes up, searches for the canonical documentation, confirms the reference with you, and adds it to the vision statement's reference list.
Example conversation
Starting from a single paragraph about a healthcare app:
Starting prompt
"I'd like to create an application to help healthcare professionals in regions where limited resources are available to be as efficient as possible — providing knowledge, advice, and helping to streamline processes and paperwork."
Brainstormer
That's a meaningful problem to solve. Let's start by understanding your primary user. Who will be using this app day-to-day?
1. Physicians and nurses at the point of care
2. Community health workers with limited formal training
3. Administrative staff managing records and paperwork
4. Suggest your own option
Pick one or more — you can combine them.
Brainstormer
Good — that covers both clinical judgment and community-level delivery. Given that community health workers may have limited formal training, will the app need to adapt its language and guidance to different literacy or expertise levels?
1. Yes — detect or ask about the user's role and adjust accordingly
2. No — design for the lowest common denominator throughout
3. Partially — a single simplified interface with optional depth for trained users
4. Suggest your own option
Brainstormer
(after several more questions) Here's the vision statement as it stands. Would you like to revise anything, or does this feel complete?
Purpose: A mobile-first clinical decision support and workflow tool for physicians, nurses, and community health workers in resource-limited settings...
What the vision statement includes
The final vision_statement JSON covers:
Purpose
A clear statement of what the software does and who it serves.
Target Audience
Specific user groups with their distinct needs and contexts.
Key Features (MVP)
Each feature with a description and concrete example of what it looks like in practice.
Differentiators
What makes this different from existing solutions in the market.
Monetization
Current model and future options, if applicable to the project.
References
Canonical URLs for every technical standard mentioned during the conversation.
