From flywheel-pm
Apply 20 systematic creativity techniques to generate solution candidates for product opportunities. Use when brainstorming solutions or feeling stuck on approaches.
npx claudepluginhub abhitsian/compound-pm-marketplace --plugin flywheel-pmThis skill uses the workspace's default tool permissions.
Provide systematic creativity techniques for generating product solutions. These 20 techniques ensure you explore the full solution space instead of jumping to the first idea.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Provide systematic creativity techniques for generating product solutions. These 20 techniques ensure you explore the full solution space instead of jumping to the first idea.
| # | Technique | How to Apply |
|---|---|---|
| 1 | Add constraints | What if you could only use one screen? One click? No text? |
| 2 | Remove constraints | What if there were no technical limitations? No budget limits? |
| 3 | Make it much bigger | What if this served 100x the users? What changes? |
| 4 | Make it much smaller | What's the absolute minimum that delivers value? |
| # | Technique | How to Apply |
|---|---|---|
| 5 | Bundle | What separate things should be combined into one? |
| 6 | Unbundle | What combined thing should be broken apart? |
| 7 | Make it the only thing | What if the entire product was just this feature? |
| 8 | Make it unnecessary | Can you eliminate the need entirely? |
| # | Technique | How to Apply |
|---|---|---|
| 9 | Remove friction | What steps can be eliminated or automated? |
| 10 | Add friction | Where would intentional friction improve outcomes? |
| 11 | Reduce anxiety | What worries users? How do you address that fear? |
| 12 | Solve an unexpressed need | What do users need but haven't articulated? |
| # | Technique | How to Apply |
|---|---|---|
| 13 | Do the opposite | What if you reversed every assumption? |
| 14 | Reframe | What if the problem is actually something different? |
| 15 | Combine unrelated things | What unexpected combination creates value? |
| 16 | Solve multiple problems | Can one solution address 2-3 pain points? |
| # | Technique | How to Apply |
|---|---|---|
| 17 | Surprise | What would unexpectedly delight users? |
| 18 | Make them feel smarter | How can the product make users look good? |
| 19 | Build distribution in | How can the product spread itself through use? |
| 20 | Make it skeuomorphic | What real-world metaphor fits perfectly? |
Pick 3-4 techniques most relevant to the problem. Generate one idea per technique.
Run all 20 techniques. Generate 1-2 ideas per technique. Then cluster and evaluate.
Run all 20 techniques in groups. For each group, discuss the best idea. Then combine ideas across groups.
After generating candidates, evaluate each on four dimensions:
| Dimension | Question | Validation Method |
|---|---|---|
| Valuable | Will customers find this valuable? | Painted doors, interviews |
| Usable | Can customers use this easily? | Prototype testing |
| Feasible | Can we build this? | Engineering spikes |
| Viable | Will this achieve the business outcome? | GTM validation |
After evaluation, classify each solution:
Then plot on the Risk vs Impact 2x2: