pm-discovery-brainstorm
Skill1 starsChanged 6 days agoUnlicenseView on GitHub
Brainstorm product ideas or experiments from Product Manager, Designer, and Software Engineer perspectives. Use when the user asks to brainstorm ideas, design experiments, ideate features, or mentions 'brainstorming', 'ideation', or '/brainstorm' for new or existing products.
In this repository76 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ad-copy-writerSkill
- ae-inspect-describeSkill
- algorithmic-artSkill
- animation-directorSkill
- assembly-guideSkill
- brainstorming-and-ideatingSkill
- brainstorming-research-ideasSkill
- brainstormingSkill
- brief-to-tasksSkill
- canvas-designSkill
- cli-designSkill
- cli-output-hierarchySkill
- commit-messageSkill
- craft-uiSkill
- creative-directorSkill
- design-briefSkill
- design-flowSkill
- design-mock-auditSkill
- design-reviewSkill
- design-system-patternsSkill
- design-tokensSkill
- deslopifySkill
- diagnoseSkill
- diagramming-app-routesSkill
- doc-restructureSkill
- eval-criticSkill
- formatting-open-markdownsSkill
- frontend-designSkill
- frontend-slidesSkill
- gdocs-tab-writerSkill
- gemini-apiSkill
- gif-creationSkill
- github_repo_researchSkill
- grill-meSkill
- grill-with-docsSkill
- hallmarkSkill
- handoffSkill
- html-presentationSkill
- humanizerSkill
- i-have-adhdSkill
- improve-codebase-architectureSkill
- information-architectureSkill
- install-skill-from-githubSkill
- markdown-output-hierarchySkill
- marketing-psychologySkill
- merge-latestSkill
- modern-web-performanceSkill
- motion-designSkill
- pdf-readerSkill
- pm-brainstormingSkill
- product-marketingSkill
- prototypeSkill
- pull-requestSkill
- ralph_loopSkill
- react-best-practicesSkill
- review-loopSkill
- sandbox-explainerSkill
- skill-creatorSkill
- skill-optSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
If either dimension is missing, ask the user.
- Distinctive: line 36
Ask the user for context. Be conversational — ask the most critical question first:
- Distinctive: line 68
After presenting initial results, offer:
- Distinctive: line 122
If the user uploads a research doc or interview transcript, extract insights before brainstorming
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/brainstorm -- Multi-Perspective Ideation
Generate creative product ideas or experiment designs from three perspectives (PM, Designer, Engineer), tailored to whether you're working on an existing product or building something new.
Invocation
/brainstorm ideas existing Mobile banking app engagement
/brainstorm ideas new AI-powered meal planning for busy parents
/brainstorm experiments existing Onboarding flow redesign
/brainstorm experiments new Marketplace for freelance designers
/brainstorm # interactive mode — asks what you needWorkflow
Step 1: Determine Mode
Parse the arguments to identify two dimensions:
- What to brainstorm:
ideas(feature concepts) orexperiments(validation tests) - Product stage:
existing(continuous discovery) ornew(initial discovery)
If either dimension is missing, ask the user. If both are missing, ask:
- "Are you brainstorming ideas for what to build, or experiments to validate assumptions?"
- "Is this for an existing product or a new product concept?"
Step 2: Gather Context
Ask the user for context. Be conversational — ask the most critical question first:
For existing products:
- What is the product? Who are current users?
- What opportunity area or problem space are you exploring?
- Any constraints (technical debt, platform limitations, team capacity)?
- What has been tried before?
For new products:
- What is the product concept? What problem does it solve?
- Who is the target user? What's their current alternative?
- What stage are you at? (napkin sketch, validated problem, early prototype)
- What are the riskiest assumptions?
Accept context from uploaded files (PRDs, research docs, strategy decks), pasted text, or conversation.
Step 3: Generate Output
If brainstorming ideas — apply the brainstorm-ideas-existing or brainstorm-ideas-new skill:
- Generate ideas from three perspectives: Product Manager (user value, business impact), Designer (UX, delight, accessibility), Engineer (technical innovation, platform leverage, scalability)
- For each idea: name, description, target user impact, feasibility assessment
- Rank the top 5 ideas with rationale
- Flag which ideas could be quick wins vs. strategic bets
If brainstorming experiments — apply the brainstorm-experiments-existing or brainstorm-experiments-new skill:
- For existing products: suggest A/B tests, prototypes, fake-door tests, wizard-of-oz, concierge experiments, and spikes
- For new products: create XYZ+S hypotheses and suggest pretotype experiments (landing pages, explainer videos, pre-orders, concierge MVPs)
- For each experiment: hypothesis, method, success criteria, effort estimate, expected timeline
- Rank by learning-per-effort ratio
Step 4: Deepen and Iterate
After presenting initial results, offer:
- "Want me to detail any of these ideas into a fuller spec?"
- "Should I identify assumptions behind the top ideas?" (chains into the
identify-assumptions-existingoridentify-assumptions-newskill) - "Want to design experiments to validate the top ideas?" (chains into experiment mode)
- "Should I prioritize these against your current backlog?" (chains into the
prioritize-featuresskill)
Output Format
For Ideas:
## Brainstorm: [Product/Feature Area]
**Mode**: Ideas for [existing/new] product
**Context**: [1-2 sentence summary]
### PM Perspective
1. **[Idea Name]** — [description] | Impact: [H/M/L] | Effort: [H/M/L]
2. ...
### Designer Perspective
1. **[Idea Name]** — [description] | Impact: [H/M/L] | Effort: [H/M/L]
2. ...
### Engineer Perspective
1. **[Idea Name]** — [description] | Impact: [H/M/L] | Effort: [H/M/L]
2. ...
### Top 5 Recommendations
| Rank | Idea | Why | Quick Win? |
|------|------|-----|------------|
### Next Steps
[What to do with these ideas]For Experiments:
## Experiment Design: [Product/Feature Area]
**Mode**: Experiments for [existing/new] product
### Hypotheses
1. **[Hypothesis]** — XYZ format: [X]% of [Y] will [Z] within [S timeframe]
### Recommended Experiments
| # | Experiment | Tests Hypothesis | Method | Effort | Timeline |
|---|-----------|-----------------|--------|--------|----------|
### Experiment Details
[For each experiment: setup, success criteria, risks, what you'll learn]Notes
- For existing products, ground ideas in current user behavior and validated problems
- For new products, focus on desirability and feasibility risks first
- If the user uploads a research doc or interview transcript, extract insights before brainstorming
- Encourage breadth first, then depth — generate many ideas before evaluating
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

