Product Requirements Document writer
Draft a complete 8-section PRD — summary, contacts, background, objectives, segments, value propositions, solution, release plan — from a product idea
- What
- Draft a complete 8-section PRD — summary, contacts, background, objectives, segments, value propositions, solution, release plan — from a product idea
- Cost
- Free
- Needs
- a product or feature idea to spec (files, research, URLs or customer data help — you can also search the web); nothing else — no accounts or keys required.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @phuryn's Product Requirements Document workflow: gather inputs first (user files, research, URLs, customer data — the agent may search the web for context and market insights), think step by step (problem, audience, success metrics, constraints, assumptions), then apply a proven 8-section template: Summary, Contacts, Background (context, why now, what became possible), Objective (why it matters, company/customer benefit, strategy alignment, SMART OKR key results), Market Segments (defined by people's problems, not demographics), Value Propositions (customer jobs, gains, pains avoided, competitive edge, Value Curve), Solution (UX/prototypes, key features, technology, assumptions), and Release (relative timeframes for v1 vs later, never exact dates). Written in accessible language — primary-school reading level, short sentences, no jargon — with assumptions flagged clearly for the team to validate, and substantial output saved as `PRD-[product-name].md`. By @phuryn, listed here with credit to its creator. Honest caveats: guidance workflow, no tooling — the agent writes the document; assumes the agent can do web research for market context. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Product Requirements Document writer is a free Muse skill for drafting a complete eight-section PRD from a product idea. It covers summary, contacts, background, objectives, segments, value propositions, solution and release plan. A complete PRD like this aligns teams early and prevents costly misunderstandings during building.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit c68487dBefore you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: a product or feature idea to spec (files, research, URLs or customer data help — you can also search the web); nothing else — no accounts or keys required. Install "Product Requirements Document writer" for me. It teaches you @phuryn's PRD workflow, rewritten upstream as a lean, decision-ready format: the PRD is short by default (one to two pages, roughly 600-1,000 words), with a fuller spec only on request. Start from what I give you; if the problem, the target users or how success will be measured is missing, ask me up to three short questions first and write only after my answers. You may research the web (market, competitors, regulations) and cite your sources, putting a finding in the document only if it changes a decision. Then write the 8-section template — Summary, Contacts (optional in the lean version), Background, Objective with SMART OKR key results, Market Segments (always included, defined by people's problems or jobs, not demographics), Value Propositions (always included: a 6-part JTBD template per segment — Who, Why, What before, How, What after, Alternatives — ending in a value proposition statement of one or two sentences), Solution (UX/prototypes, must-have features for the first version, optional technology, assumptions and open questions), Release (first version vs later vs explicitly not doing, relative timeframes) — in accessible language (short sentences, no jargon), never padding a section with "TBD" and putting what you don't know under assumptions and open questions instead of stating it as fact. Save the output as PRD-[product-name].md, and in your reply name what you deliberately left out. The skill can also review an existing PRD against the same standard, returning the gaps first, then the cuts. Source: https://raw.githubusercontent.com/phuryn/pm-skills/c68487d721e419ec87af1ae6412a842978eab785/pm-execution/skills/create-prd/SKILL.md Pinned version: install the code at commit c68487d721e419ec87af1ae6412a842978eab785 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated October 10, 2026: Skill Harbor regenerated this install prompt from the upstream file of the day. What changed for you: the PRD is now lean by default (one to two pages, fuller spec on request), the value proposition follows a fixed 6-part JTBD template, and the agent asks up to three short questions before writing when the problem, the target users or the success measure is missing. The previous prompt described the older, comprehensive format. 1. Download the SKILL.md file into a temporary folder. 2. Compare the file with the fingerprint from Skill Harbor's review of 2026-10-10: - SKILL.md: SHA-256 e3aa10a437ed7f748a957bd5d1eb06d8fa3f56dc728dcb93ce484387ecc3fa13 If it does not match, the file changed since the review: do not install it yet — tell me what you found and let me decide. 3. Read the file and tell me in plain words: what the skill does when used, whether it connects to a service, whether it reads or sends any personal information or keys, and anything that seems unusual. 4. When I say yes, copy SKILL.md and its helper files into my skills folder, in a folder named "create-prd". 5. Check the copy opens correctly (valid frontmatter, files in place) and tell me what was installed, where, and what is left for me to do (for example, give you my product idea plus any files or research to ground the PRD). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. If something seems off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- c68487d · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.