Product prd
Skill jpoindexter/product-management-skills/skills/product-prd
Operational product-management skills and a /pm router for Codex and Claude.
npx -y skills add jpoindexter/product-management-skills --skill product-prdAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Write or critique a lean product brief, PRD, or PR/FAQ that frames the customer, outcome, evidence, risks, constraints, measures, and open decisions before implementation detail. Use when requirements are solution-heavy, scope is unclear, or a team needs an executable product definition.
SKILL.md
2.7 KB, as published. Nobody here has run it
Product PRD
Create the smallest product definition that aligns a cross-functional team and exposes unresolved decisions. Do not use document length as a proxy for rigor.
Choose the artifact
- Use a one-page product brief for early discovery or a reversible bet.
- Use a PR/FAQ when customer value and narrative clarity are the main uncertainty.
- Use a lean PRD when engineering, design, analytics, operations, or policy need durable shared constraints and acceptance signals.
Workflow
- Name the decision owner, target customer, triggering situation, and desired outcome.
- Summarize problem evidence and current alternatives.
- Explain the value mechanism and strategic fit.
- State assumptions and assess value, usability, feasibility, and viability risks.
- Define in-scope behavior, constraints, and explicit non-goals without prematurely specifying every interaction.
- Describe the end-to-end customer journey, including failure, recovery, support, and exit paths.
- Define success, guardrail, instrumentation, rollout, and decision thresholds.
- Capture dependencies, unresolved questions, and owner for each.
- Add a decision log and change policy so later learning is traceable.
Output contract
Return:
- Summary and decision
- Customer, situation, problem, and evidence
- Outcome and strategic rationale
- Proposed approach and alternatives
- Scope, non-goals, and constraints
- Four-risk assessment
- Journey and failure handling
- Metrics, instrumentation, rollout, dependencies, and open decisions
Quality gate
- Evidence and assumptions are visibly different.
- The artifact explains why before what.
- Non-goals constrain scope.
- Acceptance is behavioral and measurable where possible.
- Failure and operational paths are included.
- Unknowns have owners and resolution dates.
Avoid
- A giant feature specification before discovery
- Requirements without a target outcome
- “User-friendly,” “fast,” or “accurate” without thresholds
- Hiding disagreements in vague prose
- Treating document approval as product validation
Source grounding
Operational synthesis informed by product discovery, four-risk, and prototype principles in Inspired, outcome orientation in Escaping the Build Trap, and strategy coherence in Good Strategy/Bad Strategy. PR/FAQ use is framework-informed rather than a faithful distillation of Working Backwards.