borghei/Claude-Skills / project-management/discovery/brainstorm-ideas
brainstorm-ideas
VerifiedGenerates product ideas from PM, design and engineering angles, ties each to an opportunity and ranks the top five. Use when brainstorming features for an outcome, exploring a new product, or choosing which ideas to test first.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.5 KB |
| assets/ideation_workshop_template.md | markdown | 2.9 KB |
| assets/sample_ideas.json | config | 1.5 KB |
| assets/sample_opportunity_tree.json | config | 1.4 KB |
| examples/b2b-onboarding-redesign-trio-session.md | markdown | 14.8 KB |
| references/ideation-frameworks.md | markdown | 5.8 KB |
| references/ideation-process.md | markdown | 8.4 KB |
| references/red-flags.md | markdown | 12.9 KB |
| scripts/idea_scorer.py | script | 7.5 KB |
| scripts/opportunity_tree_builder.py | script | 6.6 KB |
| scripts/scamper_generator.py | script | 6.2 KB |
references/ideation-process.md
View on GitHub# Ideation Process — Methodology, Output, Troubleshooting
> Read this when running an ideation session end to end: the five-phase methodology, output formats, supplementary techniques, troubleshooting table, and success criteria. Pair with `ideation-frameworks.md` (technique detail) and `red-flags.md`.
## Methodology
### Phase 1: Frame the Problem Space
Before generating ideas, establish clarity on the context:
1. **Define the Target Outcome** -- What measurable result are we trying to achieve? (e.g., increase activation rate by 15%, reduce churn by 10%)
2. **Identify the Target Segment** -- Who specifically are we solving for? Include behavioral and situational context, not just demographics.
3. **Map Known Constraints** -- Budget, timeline, technical platform, regulatory requirements, team capacity.
### Phase 2: Product Trio Ideation
Generate 5 ideas from each of the three perspectives (15 total):
**Product Manager Perspective (5 ideas)**
Focus: Business value, market positioning, customer pain points, strategic alignment
- What problems do customers report most frequently?
- Where are competitors weak that we could be strong?
- Which segments are underserved by current solutions?
- What would make customers willing to pay more or switch?
- How does this connect to our strategic objectives?
**Designer Perspective (5 ideas)**
Focus: User experience, workflows, accessibility, delight, friction reduction
- Where do users drop off or struggle in current flows?
- What tasks take too many steps or too much cognitive load?
- How could we surprise users with unexpected value?
- What accessibility gaps exist that exclude potential users?
- Where can we reduce time-to-value for new users?
**Engineer Perspective (5 ideas)**
Focus: Technical feasibility, scalability, platform capabilities, integration opportunities
- What new capabilities does our tech stack enable?
- Which features could we build quickly with high impact?
- Where could automation replace manual processes?
- What data do we have that we are not leveraging?
- Which technical debt, if resolved, would unlock new possibilities?
### Phase 3: Approach by Product Type
#### For New Products
Apply these lenses to each idea:
| Lens | Question |
|------|----------|
| **Core Value** | Does this idea deliver a single, clear value proposition? |
| **Speed to Validate** | Can we test the core assumption in under 2 weeks? |
| **Differentiation** | Why would someone choose this over existing alternatives? |
| **Market Timing** | Is the market ready for this? What tailwinds exist? |
| **Scalability** | Can this grow beyond the initial use case? |
#### For Existing Products (Opportunity Solution Tree)
Follow Teresa Torres' Continuous Discovery Habits framework:
```
Desired Outcome
├── Opportunity 1 (unmet need / pain point / desire)
│ ├── Solution A
│ ├── Solution B
│ └── Solution C
├── Opportunity 2
│ ├── Solution D
│ └── Solution E
└── Opportunity 3
├── Solution F
└── Solution G
```
1. **Start with the outcome** -- The metric or business result you want to move.
2. **Map opportunities** -- Interview-driven insights about what customers need, want, or struggle with.
3. **Generate solutions per opportunity** -- Each opportunity gets multiple potential solutions.
4. **Compare and select** -- Evaluate solutions within the same opportunity branch, not across branches.
### Phase 4: Prioritize Top 5
From the 15 generated ideas, select the top 5 using this scoring model:
| Criterion | Weight | Scale |
|-----------|--------|-------|
| Customer Impact | 30% | 1-10 |
| Strategic Alignment | 25% | 1-10 |
| Feasibility | 20% | 1-10 |
| Speed to Validate | 15% | 1-10 |
| Differentiation | 10% | 1-10 |
**Weighted Score** = (Impact x 0.30) + (Strategy x 0.25) + (Feasibility x 0.20) + (Speed x 0.15) + (Differentiation x 0.10)
### Phase 5: Document Each Idea
For each of the top 5 prioritized ideas, produce:
| Field | Description |
|-------|-------------|
| **Name** | Short, memorable name for the idea |
| **Description** | 2-3 sentence summary of what it is |
| **Reasoning** | Why this idea ranks highly -- connect to outcome and evidence |
| **Source Perspective** | PM, Designer, or Engineer |
| **Key Assumptions** | 2-3 assumptions that must be true for this to succeed |
| **Suggested Validation** | How to test the riskiest assumption first |
| **Effort Estimate** | T-shirt size (XS / S / M / L / XL) |
## Output Format
### Prioritized Ideas Table
| Rank | Name | Source | Score | Effort | Top Assumption |
|------|------|--------|-------|--------|----------------|
| 1 | ... | PM | 8.4 | M | ... |
| 2 | ... | Design | 7.9 | S | ... |
| 3 | ... | Eng | 7.6 | L | ... |
| 4 | ... | PM | 7.2 | S | ... |
| 5 | ... | Design | 6.8 | M | ... |
### Detailed Idea Cards
For each idea, fill in the template from `assets/ideation_workshop_template.md`.
## Supplementary Techniques
When the trio needs additional stimulus:
- **SCAMPER** -- Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse. Apply to existing products or competitor features.
- **How Might We (HMW)** -- Reframe problems as opportunity questions. "Users churn after trial" becomes "How might we demonstrate value before the trial ends?"
- **Crazy 8s** -- 8 sketches in 8 minutes per person. Forces breadth over depth.
- **Worst Possible Idea** -- Generate deliberately bad ideas, then invert them to find hidden good ones.
See `references/ideation-frameworks.md` for detailed descriptions of each technique.
## Troubleshooting
| Problem | Likely Cause | Resolution |
|---------|-------------|------------|
| Ideation session produces only incremental ideas, no breakthrough thinking | Anchoring bias -- team defaults to what they know; PM perspective dominates | Explicitly rotate perspectives (Designer first, then Engineer); use "Worst Possible Idea" technique to break anchoring; invite an outsider to challenge assumptions |
| Prioritization scores cluster tightly, making ranking impossible | Scoring criteria are too similar, or the team is avoiding differentiation | Add a forced-rank step after weighted scoring; increase weight spread between criteria; use pairwise comparison for the top 5 |
| Opportunity Solution Tree has too many branches to be actionable | Team brainstormed opportunities without filtering by evidence | Require each opportunity to link to at least 2 user interview quotes or data points; prune branches without evidence |
| Stakeholders reject prioritized ideas because "the real problem is different" | Problem framing was done without stakeholder input; target outcome not validated | Run a problem framing workshop with stakeholders before ideation; validate the target outcome with data before generating solutions |
| Same ideas keep resurfacing across sessions | Previous ideation results not documented or accessible; no "already considered" registry | Maintain an idea backlog with status (explored, parked, rejected with rationale); review it at the start of each session |
| Engineer perspective ideas are too implementation-focused | Engineers default to "how to build" rather than "what to build" | Reframe the prompt: "What new capability would our tech stack enable for users?" rather than "What should we build next?" |
| Validation suggestions are too expensive or slow | Team defaults to full A/B tests when lighter methods exist | Introduce pretotyping and Wizard-of-Oz as first validation options; use the `brainstorm-experiments/` skill for experiment design |
## Success Criteria
- Each ideation session produces at least 15 ideas across all three Product Trio perspectives (minimum 3 per perspective)
- Top 5 prioritized ideas each have a documented riskiest assumption and a validation plan
- At least 60% of prioritized ideas can begin validation within 2 weeks using lightweight methods
- Stakeholders rate the ideation output as "relevant to strategic objectives" at 4+/5
- Ideas that proceed to validation have a clear connection to the target outcome (traceable through the Opportunity Solution Tree)
- Ideation cadence is maintained (at minimum quarterly for existing products, monthly during new product exploration)
- At least 1 idea per quarter advances from ideation through validation to backlog commitment
## Further Reading
- Teresa Torres, *Continuous Discovery Habits* (2021)
- Marty Cagan, *Inspired* (2018)
- Jake Knapp, *Sprint* (2016)
- Michael Michalko, *Thinkertoys* (2006) -- SCAMPER origin
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |