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 — the agent 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:
Install
Prerequisites: a product or feature idea to spec (files, research, URLs or customer data help — the agent can also search the web); nothing else — no accounts or keys required Install "Product Requirements Document writer" for me. It teaches the agent @phuryn's PRD workflow: gather information first, think step by step (problem, who, success metrics, constraints, assumptions), then write the document with the 8-section template — Summary, Contacts, Background, Objective with SMART OKR key results, Market Segments, Value Propositions, Solution (UX, features, technology, assumptions), Release with relative timeframes — in accessible language (short sentences, no jargon), flagging assumptions clearly and saving substantial output as PRD-[product-name].md. Repository: https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/create-prd/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "create-prd". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. give the agent my product idea plus any files/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. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.