phuryn/pm-skills

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.

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.

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.

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.

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.

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.

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.

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.