<< All versions

Skill v1.0.1

currentAutomated scan100/100
pmprompt/claude-plugin-product-management/prd-writer

~1 modified, -1 removed

──Details
PublishedNovember 6, 2026 at 01:58 AM
Content Hashsha256:633053f09b0739a9...
Git SHA9b9a4929de8c
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 2.4 KB)
SKILL.md2.4 KBactive
SKILL.md · 78 lines · 2.4 KB

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]" metadata: version: "1.0.1"


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

← v1.0.0All versions