Claude Skill that writes a product requirements document from rough notes, with open questions kept visible
A Claude Skill for product managers: give Claude notes, a problem statement or a feature request thread, and it produces a PRD in a consistent template with goals, non-goals, user stories, acceptance criteria and an explicit open-questions list instead of invented answers.
Skill in Product by AISkillHub Library
What it does
PRDs vary in quality because each one starts from a blank page, and gaps get papered over with confident-sounding guesses. This Skill gives Claude a fixed PRD structure and rules about what it may and may not fill in, so drafts are consistent and anything uncertain stays visible as an open question.
**What it does**
- Triggers when you ask Claude to write, draft or structure a PRD, product spec or feature brief. - Reads your input: notes, a Slack or email thread, customer feedback, a problem statement. - Asks up to five clarifying questions if critical information is missing (the problem, the user, how success is measured), or proceeds with gaps marked if you say "draft anyway". - Fills the template in `template.md`: summary, problem, users, goals and success metrics, non-goals, user stories, functional requirements with acceptance criteria in Given/When/Then form, non-functional requirements, dependencies, risks, rollout, and open questions. - Tags every requirement with a priority (must, should, could) and an ID so engineering can reference it. - Saves the PRD as a Markdown file.
**When to use it**
- Turning a discovery summary into a spec - Writing up a feature request so engineering and design can estimate - Standardizing PRDs across several PMs
**What it will not do**
- It does not invent metrics targets, user research results, deadlines or technical constraints. These become open questions with an owner. - It does not make prioritization decisions for you. Priorities it proposes are marked "proposed" until you confirm them. - It does not design the UI. It describes required behavior.
**Example acceptance criterion**
`FR-3 (must, proposed)`: Given an admin on the Members page, when they select "Export", then a CSV of all members with name, email, role and last active date downloads within the same session.
Open question raised alongside it: "Should exports include deactivated members? Owner: PM. Needed before build."
How to use it
**Files:** `.claude/skills/prd-writer/SKILL.md` and `template.md` must stay together in a folder named `prd-writer`.
**1. Optional: adapt the template.** Edit `template.md` to match your team's PRD sections. Keep the `{{...}}` markers for sections Claude should fill, or delete sections you never use. Claude follows whatever the template contains.
**2a. Claude Code.** Put the folder at `.claude/skills/prd-writer/` in your repository so the whole team uses the same template, or at `~/.claude/skills/prd-writer/` for personal use. Then ask, for example: `Write a PRD from these notes: ...` or `Draft a PRD for the export feature discussed in docs/discovery/export.md`. The PRD is saved under `docs/prd/` unless you name another path.
**2b. Claude apps (claude.ai, desktop).** Skills require code execution to be enabled in settings, and availability depends on your plan. Zip the `prd-writer` folder so the ZIP contains the folder, upload it in the Skills section of Claude's settings, and enable it. In any chat, paste your notes and ask for a PRD; Claude creates a Markdown file you can download.
**3. Review.** Resolve the Open questions table with the named owners, then change `proposed` priorities to confirmed ones.
**Variables:** none to fill in chat. `{{...}}` markers in `template.md` are filled by Claude.
Files
Save each file at the path shown, relative to your project root.