| name | brainstorm-ideas-new |
| description | Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation. |
Brainstorm Product Ideas (New Product)
Multi-perspective ideation for initial product discovery of a new product. Generates specific feature ideas from PM, Designer, and Engineer viewpoints.
What You'll Need
| Input | Required? | Example |
|---|
| Product idea or problem to solve | ✅ Required | "AI writing assistant for non-native English speakers" |
| Target audience | ✅ Required | B2B teams, freelancers, students |
| Market or competitive context | 🟡 Recommended | Existing competitors, market research notes |
| Business model hypothesis | ⚪ Optional | SaaS subscription, freemium |
Don't have everything? Start anyway — the skill will work with what you provide and flag where richer input would improve the output.
Context
You are supporting initial product discovery for a new product: $ARGUMENTS.
If the user provides files (market research, competitive analysis), read them first. Use web search to understand the market if needed.
Domain Context
Initial Discovery vs Continuous Discovery: Initial Discovery focuses on vision, business model, and market validation — you're testing whether the product should exist. Continuous Discovery runs in parallel with delivery — you're constantly learning and iterating on a live product. This skill is for initial discovery.
Instructions
The user will describe their target segment, opportunity, and desired outcomes. Work through these steps:
Phase 0: Context Confirmation
Before proceeding, review what's been provided in $ARGUMENTS and the conversation context. Only ask about what's missing — don't re-ask what's already clear.
- Summarize what you understand from the provided context — restate the product, feature, or situation back to the user in 2-3 sentences.
- Identify gaps — if any of the following are unclear, ask:
- What problem space or opportunity are we ideating for?
- Who is the target user?
- What constraints or principles should guide ideation?
- Confirm: "Here's my understanding: [summary]. I plan to [brief description of what the skill will produce]. Does this look right, or would you like to adjust anything before I proceed?"
If the user provides additional context, incorporate it. If the user confirms, proceed.
-
Understand the opportunity: Confirm the product concept, target market segment, and what the users want to achieve.
-
Ideate from three perspectives — generate 5 specific feature ideas each from:
- Product Manager: Focus on market fit, value creation, and competitive advantage
- Product Designer: Focus on user experience, onboarding, and engagement
- Software Engineer: Focus on technical innovation, API integrations, and platform capabilities
-
Prioritize the top 5 ideas across all perspectives. For a new product, weight heavily toward:
- Core value delivery (does it solve the primary problem?)
- Speed to validate (can we test this quickly?)
- Differentiation potential
-
For each prioritized idea, provide reasoning and key assumptions to test.
Think step by step. Save substantial output as a markdown document.