Prd Writer
- 852 installs
- 43 repo stars
- Updated March 7, 2026
- pmprompt/claude-plugin-product-management
prd-writer is a Claude Code skill that generates a complete structured Product Requirements Document for developers and PMs who are kicking off a new feature or product initiative and need formal scope documentation.
About
prd-writer is a skill from pmprompt/claude-plugin-product-management that generates comprehensive product requirements documents using a proven product management framework combining industry best practices for day-to-day PM work. The skill accepts a feature name argument and works best with product context, relevant data or research, constraints, and a clear statement of goals. Developers and product managers reach for prd-writer when starting a new feature or product initiative and need structured documentation before engineering breakdown. Output covers the standard PRD sections expected in professional product workflows, turning informal feature ideas into scoping artifacts that downstream skills like analyze-issue can later decompose into technical specifications.
- Generates 5-section PRDs covering problem statement, proposed solution, requirements, implementation, and risks
- Follows a proven product management framework drawn from industry best practices
- Accepts optional research, constraints, and context to produce tailored documentation
- Creates alignment artifacts ready for engineering, design, and stakeholder handoff
- Hard-gate: run before design or development work begins
Prd Writer by the numbers
- 852 all-time installs (skills.sh)
- +29 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #560 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pmprompt/claude-plugin-product-management --skill prd-writerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 852 |
|---|---|
| repo stars | ★ 43 |
| Security audit | 3 / 3 scanners passed |
| Last updated | March 7, 2026 |
| Repository | pmprompt/claude-plugin-product-management ↗ |
How do you write a PRD for a new feature?
Instantly generate a complete, structured Product Requirements Document when kicking off a new feature or product.
Who is it for?
Product managers and tech leads kicking off a new feature who need a complete PRD from informal context and research inputs.
Skip if: Developers who already have a GitHub issue ready for technical decomposition or teams past scoping who need implementation specs only.
When should I use this skill?
A developer or PM starts a new feature or product initiative and asks for a product requirements document.
What you get
Structured Product Requirements Document with scope, requirements, constraints, and goals for the named feature.
- Product Requirements Document
- Feature scope and constraints documentation
Files
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
PRD Writer
When to Use
- Starting a new feature or product initiative
- Need to document requirements for the engineering team
- Stakeholders need a detailed project overview
- Before beginning design or development work
- To align cross-functional teams on scope and goals
What This Skill Does
Creates structured, comprehensive PRDs covering problem statement, proposed solution, requirements, success metrics, and implementation details.
Instructions
Help me write a comprehensive PRD for [feature name]. Include:
1. Problem Statement
- Current situation
- User pain points
- Business impact
2. Proposed Solution
- Overview of the approach
- User stories
- Success metrics
3. Requirements
- Functional requirements
- Technical requirements
- Design requirements
4. Implementation
- Dependencies
- Timeline estimate
- Resources needed
5. Risks and Mitigations
Your context: [Add product context, feature details, and constraints here]
Best Practices
- Be specific about the problem and user pain points
- Include quantitative success metrics
- Define scope clearly (what's in scope and out of scope)
- Consider technical constraints upfront
- Add detailed user stories for key flows
- Include acceptance criteria
Example
Input: Building a notification center for SaaS app, target users are power users who miss important updates Output: Full PRD with problem statement, user stories, functional/technical requirements, success metrics (reduce missed notifications by 40%), timeline, and risk assessment
Further Reading
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Choose prd-writer for new feature scoping documents; use analyze-issue when a GitHub ticket already exists and needs a technical spec.
FAQ
What inputs does prd-writer need?
prd-writer accepts a feature name plus product context, relevant data or research, constraints, and a clear goal statement. Research and constraints are recommended but optional for generating the PRD.
When should developers use prd-writer?
Developers and PMs should use prd-writer when starting a new feature or product initiative and needing structured requirements documentation. prd-writer applies a proven PM framework before engineering breakdown begins.
Is Prd Writer safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.