brainstorm

When this skill is invoked:

1. Parse the argument for an optional product type or problem hint (e.g., productivity app, API service, developer tool, marketplace). If open or no argument, start from scratch.

2. Check for existing concept work:

   • Read design/docs/product-concept.md if it exists (resume, don't restart)
   • Read design/docs/product-pillars.md if it exists (build on established pillars)

3. Run through ideation phases interactively, asking the user questions at each phase. Do NOT generate everything silently — the goal is collaborative exploration where the AI acts as a product thinking facilitator, not a replacement for the human's vision.

   Use AskUserQuestion at key decision points throughout brainstorming:

   • Constrained taste questions (product type, target users, scope)
   • Concept selection ("Which 2-3 concepts resonate?") after presenting options
   • Direction choices ("Develop further, explore more, or start sprint planning?")
   • Pillar ranking after concepts are refined

   Write full analysis in conversation text first, then use AskUserQuestion to capture the decision with concise labels.

   Professional product brainstorming principles to follow:

   • Withhold judgment — no idea is bad during exploration
   • Encourage unusual ideas — outside-the-box thinking sparks better products
   • Build on each other — "yes, and..." responses, not "but..."
   • Use constraints as creative fuel — limitations often produce the best ideas
   • Time-box each phase — keep momentum, don't over-deliberate early

---

Phase 1: Creative Discovery

Start by understanding the person and their context, not the product. Ask these questions conversationally (not as a checklist):

Problem anchors:

• What's a frustrating problem you personally experience that no existing tool solves well?
• Is there a workflow, process, or task you've always wished was easier or more automated?

Experience profile:

• What 3 products (apps, tools, APIs, services) do you use most? What keeps you coming back?
• Are there product categories you love or actively avoid? Why?
• Do you prefer products that save time, reduce complexity, enable creativity, or connect people?

Practical constraints (shape the sandbox before brainstorming):

• Solo developer or team? What skills and resources are available?
• Timeline: weeks (MVP), months (v1), or years (full product)?
• Any platform constraints? (Web only? Mobile? API-first? Desktop?)
• First product or experienced builder?
• Revenue model in mind? (SaaS, open source, freemium, one-time purchase?)

Synthesize the answers into a Product Brief — a 3-5 sentence summary of the person's goals, experience context, and constraints. Read the brief back and confirm it captures their intent.

---