skills.rest
junchenghuo
junchenghuoCOMMUNITY
Explore all skills by this author →
GitHub

product-prd-doc

Generate and revise Product Requirement Documents in Markdown with optional .docx export.

3|Updated Mar 11, 2026
Search Tags:#project management#documentation#acceptance criteria#user stories#prd#product requirements
One-click install
npx skills add https://github.com/junchenghuo/openclaw-biz-agent --skill product-prd-doc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-prd-doc
Source: https://github.com/junchenghuo/openclaw-biz-agent/tree/main/leader/.agents/skills/product-prd-doc
Command: npx skills add https://github.com/junchenghuo/openclaw-biz-agent --skill product-prd-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and revision of Product Requirement Documents (PRDs), ensuring clarity and completeness for internal projects.

Core Features & Use Cases

  • PRD Generation: Write comprehensive PRDs covering goals, user stories, scope, flows, requirements, and acceptance criteria.
  • Format Flexibility: Outputs PRDs in Markdown, with support for .docx export via Pandoc if available.
  • Use Case: When launching a new feature, use this Skill to generate a detailed PRD that outlines the business objectives, user interactions, and technical specifications, ensuring all stakeholders are aligned.

Quick Start

Use the product-prd-doc skill to write a PRD for a new user authentication system.

Frequently Asked Questions about product-prd-doc

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

FAQPage Schema
How do I write a PRD for a new software feature?▼

Generate a Product Requirements Document by specifying business objectives, mapping user stories, defining UX flows, and formulating acceptance criteria to align stakeholders on internal software projects.

What should be included in product requirements documentation for internal projects?▼

Comprehensive PRDs must include project goals, user story mappings, scope definitions, UX flows, edge case analysis, and acceptance criteria formulation to ensure stakeholder alignment.

Can I export a Markdown PRD to a Word document?▼

Yes, you can export Markdown PRDs to .docx format. If Pandoc is installed in your environment, the generated Markdown documentation can be converted directly into a Word document file.

How do I define edge cases and acceptance criteria in a PRD?▼

Define edge cases and acceptance criteria by analyzing potential user flow deviations and formulating exact validation conditions, ensuring comprehensive requirement specification for internal software projects.

Does this PRD generation method support user story mapping?▼

Yes, PRD generation supports user story mapping by structuring user interactions and defining UX flows, translating high-level business objectives into actionable development tasks for internal projects.

Related Skills

Explore More Product & Management Skills→
rhinklerhinkle

prd-local

Generate a structured Product Requirements Document from a feature prompt.

Community
Intermediate
jackspacejackspace
16

markitdown

Convert PDFs, DOCX, PPTX, XLSX, HTML, EPUB, CSV, JSON, and images into Markdown.

Community
Intermediate
bearbinarybearbinary

prd-to-json

Converts Markdown PRDs into structured JSON task files with progress tracking.

Official
Intermediate
MarcoAntoliniMarcoAntolini
1

to-prd

Convert conversation context into a Product Requirements Document and integrate it into an issue tracker.

Community
Advanced