phuryn/brainstorm-ideas-existing
pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills brainstorm-ideas-existingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 2:04 PM31.0s1 file scanned
SKILL.md
- name:
- brainstorm-ideas-existing
- description:
- Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm Product Ideas (Existing Product)
Multi-perspective ideation for continuous product discovery. Generates ideas from PM, Designer, and Engineer viewpoints, then prioritizes the best five.
Context
You are supporting a product trio performing continuous product discovery for $ARGUMENTS.
If the user provides files (research data, opportunity trees, personas), read them first. If they mention a product URL, use web search to understand the product.
Domain Context
Product Trio (Teresa Torres, Continuous Discovery Habits): PM + Designer + Engineer collaborate on discovery together. "Best ideas often come from engineers." Discovery is not linear — loop back if experiments fail. Use the Opportunity Solution Tree (Teresa Torres) to map opportunities → solutions → experiments.
Instructions
The user will describe their objective, target segment, and desired outcomes. Work through these steps:
-
Understand the opportunity: Confirm the product, objective, market segment, and desired outcomes. Ask for clarification if anything is ambiguous.
-
Ideate from three perspectives — generate 5 ideas each from:
- Product Manager: Focus on business value, strategic alignment, and customer impact
- Product Designer: Focus on user experience, usability, and delight
- Software Engineer: Focus on technical possibilities, data leverage, and scalable solutions
-
Prioritize the top 5 ideas across all perspectives based on:
- Strategic alignment with the stated objective
- Potential impact on desired outcomes
- Feasibility and effort required
- Differentiation from existing solutions
-
For each prioritized idea, provide:
- A clear name and one-sentence description
- Why it was selected (reasoning)
- Key assumptions to validate
Think step by step. Present ideas in a clear, structured format.
If the output is substantial, save it as a markdown document in the user's workspace.
Further Reading
- What Is Product Discovery? The Ultimate Guide Step-by-Step
- Product Trio: Beyond the Obvious
- The Extended Opportunity Solution Tree
- Product Model First Principles: Product Discovery, Product Delivery, and Product Culture In Depth
- Continuous Product Discovery Masterclass (CPDM) (video course)
Related Skills
phuryn/strategy-red-team
testing
VerifiedTrustedCommunity
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.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/shipping-artifacts
tools
VerifiedTrustedCommunity
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/intended-vs-implemented
development
VerifiedTrustedCommunity
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/review-resume
testing
VerifiedTrustedCommunity
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
7,806SKILL.mdUpdated Mar 20, 2026