deanpeters/prd-development
Structured PRD process: problem → personas → solution → metrics → stories
by deanpetersFree
Description
prd-development is a workflow skill for writing a structured product requirements document (PRD). It orchestrates problem framing, user research synthesis, solution definition and success criteria into one cohesive document. The aim is to move from scattered notes and chat threads to a clear, complete PRD that aligns stakeholders, gives engineers the context they need, and serves as the source of truth. The skill is built to avoid ambiguity, scope creep and what it calls the build what is in my head trap. It fits three situations: writing a complete PRD from scratch, structuring requirements for an engineering handoff, and documenting a major new feature before development starts. Example requests include a PRD for an AI-powered recommendation feature in an e-commerce platform, and a PRD built from the findings of a finished discovery sprint. You pass the feature or initiative as the argument. The estimated time is 60 to 120 minutes, and the skill belongs to the PM artifacts theme of the product-manager-skills repository on GitHub.…
Highlights
- Problem, users, solution and success criteria
- Orchestrates framing and research synthesis
- Engineering handoff context
- Avoids scope creep and ambiguity
- Estimated 60 to 120 minutes
Ratings & Reviews
No ratings yet
Be the first to rate deanpeters/prd-development.
People also visit
coreyhaines31/copywriting
Write and rewrite marketing copy for landing pages, homepages, and ads
coreyhaines31/ab-testing
Plan and implement A/B tests or experiments for any digital experience
coreyhaines31/ad-creative
Generate and iterate ad creative including headlines, descriptions
coreyhaines31/ads
Create and optimize paid campaigns on Google, Meta, LinkedIn, and more
coreyhaines31/ai-seo
Optimize content to appear in AI-generated answers and LLM search results
deanpeters/prd-development FAQ
What does the skill produce?
A structured PRD that connects the problem, the users, the solution and the success criteria.
When should I use it?
When turning discovery notes into an engineering-ready document for a major initiative.
What input does it need?
The feature or initiative, as the argument.
Does it replace discovery?
No. The skill is meant to use the findings of problem framing and research synthesis.
How long does it take?
The skill estimates 60 to 120 minutes.
What are the best deanpeters/prd-development alternatives?
Popular alternatives to deanpeters/prd-development include coreyhaines31/seo-audit, coreyhaines31/copywriting and coreyhaines31/ab-testing. See all deanpeters/prd-development alternatives