P

prd-writer

by @pmpromptv1.0.0
0.0(0)

Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation.

Product ManagementPRDRequirements GatheringTechnical WritingProduct DocumentationGitHub
安装方式
npx skills add pmprompt/claude-plugin-product-management --skill prd-writer
compare_arrows

Before / After 效果对比

0

description 文档


name: prd-writer description: Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation. argument-hint: [feature name]

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
  1. Proposed Solution
  • Overview of the approach
  • User stories
  • Success metrics
  1. Requirements
  • Functional requirements
  • Technical requirements
  • Design requirements
  1. Implementation
  • Dependencies
  • Timeline estimate
  • Resources needed
  1. 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

forum用户评价 (0)

发表评价

效果
易用性
文档
兼容性

暂无评价,来写第一条吧

统计数据

安装量0
评分0.0 / 5.0
版本1.0.0
更新日期2026年3月17日
对比案例0 组

用户评分

0.0(0)
5
0%
4
0%
3
0%
2
0%
1
0%

为此 Skill 评分

0.0

兼容平台

🔧Claude Code

时间线

创建2026年3月17日
最后更新2026年3月17日