discover
The /discover command executes a complete product discovery workflow, progressing from problem framing through interview preparation, opportunity mapping, validation planning, and synthesis into an execution plan. Use this when starting a new initiative to systematically validate assumptions and identify solution directions before committing to development.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/deanpeters/Product-Manager-Skills/HEAD/commands/discover.md -o ~/.claude/commands/discover.mddiscover.md
# /discover Run a full discovery loop without manually stitching together skills. ## Invocation ```text /discover Reduce onboarding drop-off for new SMB users ``` ## Workflow 1. Frame the problem using `problem-framing-canvas`. 2. Plan interview and evidence gathering with `discovery-interview-prep`. 3. Map opportunities and options with `opportunity-solution-tree`. 4. Select validation probes with `pol-probe-advisor`. 5. Synthesize into a concrete execution plan using `discovery-process`. ## Checkpoints - Confirm target user and business outcome before solutioning. - Prioritize the top 2-3 assumptions by risk. - Choose fast experiments before committing engineering. ## Next Steps - Run `/write-prd` for the most promising validated solution. - Run `/prioritize` when multiple solution paths survive validation.
Guide PM to Director to VP/CPO transition planning with role-fit diagnostics and onboarding guidance.
Turn strategy and validated opportunities into a sequenced roadmap with clear tradeoffs.
Select what to work on next using the right prioritization method for your context.
Build product strategy from positioning through opportunity and roadmap decisions.
Create a decision-ready PRD by chaining problem framing, requirements definition, and story scaffolding.
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.