Full-Cycle Product Manager

Steps

1. 1

   Define the Problem

   ID:OZA6

   Frame the customer problem before proposing a feature. Specify the user segment, job or pain, context, existing alternatives, and desired change. Distinguish evidence from belief, and ensure the problem is specific enough to validate or falsify.

   skill: github:phuryn/pm-skills @ analyze-feature-requests
   Expected Outputs
2. 2

   Discovery

   ID:Y52Q

   Explore the opportunity space before narrowing it. Gather or synthesize customer evidence, map opportunities, generate multiple solution directions, and preserve unanswered questions. Do not write a feature specification or commit to a solution at this stage.

   skill: github:phuryn/pm-skills @ brainstorm-ideas-existingskill: github:phuryn/pm-skills @ opportunity-solution-tree
   Expected Outputs
3. 3

   Map Assumptions

   ID:L35O

   List the value, usability, viability, feasibility, and go-to-market assumptions behind the leading options. Rank them by impact and uncertainty so the team knows which belief could most cheaply invalidate the investment.

   skill: github:phuryn/pm-skills @ identify-assumptions-existingskill: github:phuryn/pm-skills @ prioritize-assumptions
   Expected Outputs
4. 4

   Design Experiments

   ID:YJHN

   Design the smallest credible experiment for each critical assumption. Define the audience, method, cost, required evidence, success threshold, failure threshold, and the decision that follows each result. Prefer learning before building.

   skill: github:phuryn/pm-skills @ brainstorm-experiments-existing
   Expected Outputs
5. 5

   Product Strategy

   ID:0FUF

   Turn validated learning into a product bet. Define the target segment, positioning, differentiated value, strategic trade-offs, success measures, and capabilities required to win. State the hypotheses that still need monitoring after launch.

   skill: github:phuryn/pm-skills @ product-strategy
   Expected Outputs
6. 6

   Prioritize

   ID:JH7C

   Compare initiatives using impact, confidence, effort, dependencies, risk, and strategic alignment. Make the opportunity cost visible. Select the initiative to pursue now and explicitly document what is deferred or declined and why.

   skill: github:phuryn/pm-skills @ prioritize-features
   Expected Outputs
7. 7

   Write PRD

   ID:MISN

   Write an implementation-ready PRD: problem, users, objective, scope, requirements, non-goals, acceptance criteria, metrics, edge cases, dependencies, and unresolved assumptions. Ensure each requirement can be tested and that the document does not substitute unvalidated detail for evidence.

   skill: github:phuryn/pm-skills @ create-prd
   Expected Outputs
8. 8

   Launch Plan

   ID:S560

   Plan who receives the release, how it is introduced, what messaging and enablement are required, and which operational risks must be covered. Define rollout stages, decision owners, rollback criteria, and launch-day communication before release.

   skill: github:phuryn/pm-skills @ gtm-strategy
   Expected Outputs
9. 9

   Measure and Learn

   ID:LONA

   Set a baseline, metric tree, North Star metric, guardrails, and review cadence. Define the thresholds for continue, improve, pause, or stop. Review the evidence after launch and make the next product decision rather than treating launch as completion.

   skill: github:phuryn/pm-skills @ metrics-dashboardskill: github:phuryn/pm-skills @ north-star-metric
   Expected Outputs