brainstorm-ideas-new

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.

3,304
installs: 0 up / 0 down, score 0.00
votes: 27,300
repo stars
Updated: less than a month ago
In the catalog since: 1 Oct 2026
From: phuryn/pm-skills

Get it through your agent npx skills add phuryn/pm-skills@brainstorm-ideas-new

Skill instructions

Rendered from the published SKILL.md, 42 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.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "brainstorm-ideas-new"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository phuryn/pm-skills
Listing on skills.sh

From phuryn/pm-skills via skills.sh

Related skills

brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
405,153 installs
inspired-product
Build empowered product teams using discovery and delivery dual-track. Use when the user mentions "product discovery", "empowered teams", "feature factory", "opportunity assessment", "product vision", "product strategy", "what should we build", or "our roadmap is just a feature list". Also trigger when restructuring teams away from output-driven models, or deciding what to build next based on outcomes. Covers discovery techniques, team structure, opportunity assessment, vision/strategy, and continuous delivery. For customer interviews, see mom-test. For ongoing discovery systems, see continuous-discovery.
5,105 installs
ce-brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.
3,918 installs
game-changing-features
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
3,929 installs
domain-name-brainstormer
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
5,181 installs

More from phuryn/pm-skills

create-prd
Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
10,782 installs
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
10,179 installs
prioritization-frameworks
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
9,945 installs
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
9,927 installs
strategy-red-team
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
9,247 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.

Skill instructions

Brainstorm Product Ideas (New Product)

Context

Domain Context

Instructions

Further Reading