pm/prd-writing

Generates standardized product requirement documents with structured sections and acceptance criteria.

553|50|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/echoVic/boss-skill --skill pm-prd-writing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm/prd-writing
Source: https://github.com/echoVic/boss-skill/tree/main/skill/skills/pm/prd-writing
Command: npx skills add https://github.com/echoVic/boss-skill --skill pm-prd-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing a complete, consistent PRD is time-consuming and often results in vague requirements that designers, developers, and testers cannot act on. This Skill provides a standardized PRD structure that ensures every requirement is clear, testable, and traceable.

Core Features & Use Cases

  • Standardized PRD Template: Covers 11 sections including overview, requirement penetration analysis, competitive research, user personas, functional and non-functional requirements, user stories, success metrics, scope, risks, and milestones.
  • Acceptance Criteria Enforcement: Every functional requirement includes testable acceptance criteria, priority levels (P0/P1/P2), and edge case handling.
  • Quality Checklist: Built-in pre-delivery checklist verifying completeness of requirement analysis, scope definition, and risk identification.
  • Use Case: After completing requirement analysis for a new feature, invoke this Skill to produce a Markdown PRD file (prd-{feature}-{date}.md) that downstream design, engineering, and QA agents can directly consume.

Quick Start

Ask the PM agent to write a PRD for your feature after requirement analysis is complete, and it will output a structured Markdown document following the standard template.

Frequently Asked Questions about pm/prd-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product requirement document with an AI agent?▼

Invoke the PM agent after completing requirement analysis, and it generates a PRD following a standard 11-section template. The output is a Markdown file named prd-{feature}-{date}.md saved to the project root or docs directory.

What sections should a standard PRD template include?▼

This template includes overview, requirement penetration analysis, competitive research, target users, functional requirements, non-functional requirements, user stories, success metrics, scope definition, risks and dependencies, and milestones.

How do I write acceptance criteria for functional requirements?▼

Each functional requirement in the template includes a checklist of testable acceptance criteria labeled AC-1, AC-2, and so on. Criteria must be specific and verifiable so testers can write test cases directly from them.

Does this PRD skill require prior requirement analysis?▼

Yes, it depends on the pm/requirement-penetration skill and is triggered after requirement analysis completes. It is agent-invocable rather than user-invocable, meaning the PM agent calls it within the workflow.

What output format does the PRD generator produce?▼

It produces a Markdown document using standard heading structures, tables for competitive analysis and risk registers, and Mermaid diagrams for user journey maps. Typical length is 5-20 pages depending on feature complexity.