# Prd Writer

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

- Skill: `om-scogo/prd-writer` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds add om-scogo/prd-writer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/om-scogo/prd-writer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: om-scogo (https://skillmd.com/u/om-scogo)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/om-scogo/prd-writer

---


## 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

- [Prd Templates](https://pmprompt.com/blog/prd-templates)
- [How To Write Prd Using Ai](https://pmprompt.com/blog/how-to-write-prd-using-ai)
- [Prd Examples](https://pmprompt.com/blog/prd-examples)