prd-writer
Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation.
Works with
--- name: prd-writer description: Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation. license: MIT --- ## 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)
More Writing & Documentation skills
paper-context-resolver
lllllllama/rigorpilot-skills
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.
repo-intake-and-plan
lllllllama/rigorpilot-skills
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

