Agent skill · Documentation

prd-template

Create 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.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill prd-template --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/prd-template/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PRD Template Skill This skill helps create professional Product Requirements Documents following industry best practices. ## Required Inputs Ask the user for these if not provided: - **Feature or product name** - **Problem being solved** (from the user's perspective) - **Target user** (role, context, what they're trying to accomplish) - **Success metrics** (how will you know it worked?) - **Scope** (MVP vs full vision — what's in and out of scope) - **Key stakeholders** (who needs to review and approve) ## Reads from / Writes to the Brain If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, use it instead of asking for context you already have: - **Read first:** `context.md` (product, metrics definitions, voice), `knowledge/strategy.md` (where the product is going), any related `hypotheses/` and the matching `entities/` feature file. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<feature>"` to pull grounded facts, and carry their provenance tags into the PRD (don't present a `[hunch]` as a settled requirement). - **Write after:** save the feature as/into `entities/<feature>.md`, log any scoping decision to `decisions/`, and add new a

What's inside
Steps it walks through
  1. Required Inputs
  2. Reads from / Writes to the Brain
  3. Deeper Materials
  4. Template Structure
  5. 1. Overview
  6. 2. Context & Background
  7. 3. User Stories & Use Cases
  8. 4. Requirements
  9. 5. Design & User Experience
  10. 6. Technical Considerations
  11. 7. Implementation Plan
  12. 8. Open Questions
  13. 9. Appendix
  14. Writing Guidelines
Ships with 3 files
  • references/success-metrics-guide.md
  • references/worked-example.md
  • templates/prd-skeleton.md
More from pm-claude-skills
All skills →
About this skill
What does the prd-template skill do?

Create 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.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill prd-template --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going