phuryn/pm-skills

brainstorm-ideas-existing

Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints.

View source
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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:

  1. Understand the opportunity: Confirm the product, objective, market segment, and desired outcomes. Ask for clarification if anything is ambiguous.
  1. 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
  1. 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
  1. 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

from this repository

More skills

All skills
phuryn
Community

create-prd

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

installs
1
GitHub stars
26.5K
Updated
Sep 14
phuryn
Community

outcome-roadmap

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

installs
1
GitHub stars
26.5K
Updated
Sep 14
phuryn
Community

strategy-red-team

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.

installs
1
GitHub stars
26.5K
Updated
Sep 14
phuryn
Community

brainstorm-experiments-new

Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.

installs
2
GitHub stars
26.4K
Updated
Sep 14