Brainstorm ideas new skill
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives.
by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗
npx degit phuryn/pm-skills/pm-product-discovery/skills/brainstorm-ideas-new#main ~/.claude/skills/brainstorm-ideas-newChecked ·commit main
Files of Brainstorm ideas new
Show the full text47 lines
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.
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:
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.
Further Reading
| 1 | |
| 2 | name brainstorm-ideas-new |
| 3 | 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." |
| 4 | |
| 5 | |
| 6 | ## Brainstorm Product Ideas (New Product) |
| 7 | |
| 8 | Multi-perspective ideation for initial product discovery of a new product. Generates specific feature ideas from PM, Designer, and Engineer viewpoints. |
| 9 | |
| 10 | ### Context |
| 11 | |
| 12 | You are supporting initial product discovery for a new product: **$ARGUMENTS**. |
| 13 | |
| 14 | If the user provides files (market research, competitive analysis), read them first. Use web search to understand the market if needed. |
| 15 | |
| 16 | ### Domain Context |
| 17 | |
| 18 | **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**. |
| 19 | |
| 20 | ### Instructions |
| 21 | |
| 22 | The user will describe their target segment, opportunity, and desired outcomes. Work through these steps: |
| 23 | |
| 24 | **Understand the opportunity**: Confirm the product concept, target market segment, and what the users want to achieve. |
| 25 | |
| 26 | **Ideate from three perspectives** — generate 5 specific feature ideas each from: |
| 27 | **Product Manager**: Focus on market fit, value creation, and competitive advantage |
| 28 | **Product Designer**: Focus on user experience, onboarding, and engagement |
| 29 | **Software Engineer**: Focus on technical innovation, API integrations, and platform capabilities |
| 30 | |
| 31 | **Prioritize the top 5 ideas** across all perspectives. For a new product, weight heavily toward: |
| 32 | Core value delivery (does it solve the primary problem?) |
| 33 | Speed to validate (can we test this quickly?) |
| 34 | Differentiation potential |
| 35 | |
| 36 | **For each prioritized idea**, provide reasoning and key assumptions to test. |
| 37 | |
| 38 | Think step by step. Save substantial output as a markdown document. |
| 39 | |
| 40 | |
| 41 | |
| 42 | ### Further Reading |
| 43 | |
| 44 | [Startup Canvas: Product Strategy and a Business Model for a New Product] |
| 45 | [Product Innovation Masterclass] (video course) |
| 46 | [Continuous Product Discovery Masterclass (CPDM)] (video course) |
| 47 |
Discussion
Alternatives
Academy guideStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Analyze feature requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Advocacy program designerUse when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规Act as a product managerGuides the AI to act as a product manager, assisting in writing product requirement documents and addressing product-related queries.Browse more free Claude skills or everything in Product.