Brainstorm Ideas New Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/phuryn/pm-skills --skill brainstorm-ideas-newThe instruction itself
5 sections, as written by the authorBrainstorm 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
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
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.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take phuryn/brainstorm-ideas-new from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.