create-prdcommit 6058e29SKILL.md · Requirements
Create a PRD
Writes a lean, decision-ready PRD from an 8-section template with market segments and a 6-part JTBD value proposition, about one to two pages.
npx skills add phuryn/pm-skills --skill create-prdCommand selected. Copy it manually.
- Permissions
- read-repo
- write-files
- shell
- network
- Compatible with
- Claude Code, Codex, Gemini CLI, OpenCode
- GitHub
- 27.6k
- Source
- Community · Pawel Huryn
- Status
- Scan passed
- License
- MIT
- Category
- Requirements
Core rule
Don't invent: what you don't know goes to Assumptions and open questions, clearly marked, not into the body as fact.
Execution Phases
Phase 01Start from the inputs
Read any files provided; if the problem, target users or success metric is missing, ask up to three short questions first and write no PRD in that reply.
Phase 02Research when it helps
Search the web for market, competitors, regulations or recent changes, cite sources next to claims, and include a finding only if it changes a decision.
Phase 03Write the 8 sections
Cover summary, contacts, background, objective, market segments, value propositions, solution and release; segments and value propositions are always included.
Phase 04Save and list omissions
Save it as PRD-[product-name].md and add one line in the reply listing what was deliberately left out.
Permissions (summarised from SKILL.md)
| Capability | Needed | Details |
|---|---|---|
| File writes | Limited | Writes only the Markdown file PRD-[product-name].md. |
| Command execution | Not required | A writing skill; it runs no commands. |
| Network outbound | Required | Searches the web for market, competitor and regulatory context and reads sources the user points to. |
SKILL.md frontmatter (YAML)
---
name: create-prd
description: "Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD."
---