From the author
Assemble a full, market-driven Product Requirements Document (PRD) the Pragmatic way — problem-before-solution, evidence-based, persona-first. Use when the PM asks for a PRD, product spec, feature doc, "write the requirements doc", or "put it all together for the team". Pulls in existing personas, positioning, market problems, requirements and use scenarios if present, and gathers anything missing inline. Produces a Product Requirements Document as a Markdown or Word .docx artifact.
Install
npx skills add julianoczkowski/product-manager --skill pm-prd -a claude-code
Installs to .claude/skills/pm-prd/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- pm-requirementsjulianoczkowski/product-managerWrite market-driven, prioritized product requirements (a Market Requirements Document / MRD) the Pragmatic Institute way. Use when the PM asks for "requirements", "an MRD", "what should we build", "prioritize features", "market requirements", or wants development to stop saying "requirements aren't specific enough". Articulates each requirement as a persona's problem, prioritizes with Market Evidence × Impact, and groups them for delivery. Produces a Market Requirements Document as a Markdown or Word .docx artifact.Planning★ 52
- prd-templatemohitagw15856/pm-claude-skillsCreate a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.Planning★ 1.5K
- prdgithub/awesome-copilotGenerate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.Planning★ 40.8K
- prd-generatorrshankras/claude-code-apple-skillsGenerates comprehensive Product Requirements Document from product plan. Creates PRD.md with features, user stories, acceptance criteria, and success metrics. Use when creating product requirements.Planning★ 859
- pm-product-roadmapjulianoczkowski/product-managerBuild a Pragmatic Institute Product Roadmap that communicates vision, direction and priorities over time — a plan, not a commitment. Use when the PM asks for a "roadmap", "product vision", "what's coming", "phases", "themes over time", or wants to align stakeholders on direction (as distinct from a dated release plan). Frames outcomes and market problems over time-frames, not features on dates. Produces a Product Roadmap as a Markdown or Word .docx artifact.Planning★ 52
- prd-developmentdeanpeters/Product-Manager-SkillsBuild a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.Planning★ 7.9K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in