create-prd

Generate a 14-chapter B-end PRD with Mermaid diagrams and TODO gaps.

284|32|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/pmYangKun/create-prd-skill --skill create-prd-pmyangkun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-prd
Source: https://github.com/pmYangKun/create-prd-skill/tree/main
Command: npx skills add https://github.com/pmYangKun/create-prd-skill --skill create-prd-pmyangkun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

create-prd removes the biggest time sink in PRD work: designing a complete 14-chapter structure from scratch. It converts your business description or meeting notes into a usable, structured first draft with real content and clearly marked gaps when information is missing.

Core Features & Use Cases

  • 14-chapter structured B端 PRD generation: Automatically drafts background, business analysis, goals, scope, risks, functionality, tracking, permissions, operations, and open items.
  • Product-type aware tailoring: Adjusts chapter emphasis based on inferred product attributes (commercial product vs enterprise internal system) and feature type.
  • Deterministic, step-by-step workflow: Performs phased generation with mandatory product-type confirmation, then generates chapters sequentially and finishes with a self-check + TODO gap list.
  • Mermaid-first diagrams: Produces architecture, ER model, flowcharts, and state machines using Mermaid code blocks for easy rendering.

Quick Start

Call the skill with your input by writing: “/create-prd 根据下面的业务描述生成一份14章结构化的B端PRD:{粘贴你的业务描述或会议纪要},请先让我确认产品定型结果后再继续。”

Frequently Asked Questions about create-prd

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

FAQPage Schema
How do I generate a structured B端 PRD from business context or meeting notes?

To generate a structured B端 PRD, provide your business context or meeting notes and the system drafts a 14-chapter document. It infers the product type, requests confirmation, then sequentially generates chapters with Mermaid diagrams and a self-check list.

What is the best way to draft a 14-chapter product requirements document for a B端 system?

The best way to draft a 14-chapter B端 PRD is using a deterministic, step-by-step workflow that sequentially builds background, scope, risks, and functionality. This approach ensures chapter emphasis is tailored to the inferred product attributes.

Can I automatically create Mermaid diagrams for architecture and flowcharts in a PRD?

Yes, you can automatically create Mermaid diagrams for architecture, ER models, flowcharts, and state machines directly within the PRD generation process. The system produces Mermaid code blocks during chapter 10 for easy rendering.

Does this PRD generation approach handle missing information in business descriptions?

This PRD generation approach handles missing information by producing clearly marked TODO gaps throughout the document. It completes a final self-check checklist to highlight any missing data tracking or permissions details for later review.

How do I structure data tracking and permissions requirements for an enterprise internal system?

To structure data tracking and permissions for an enterprise internal system, the PRD workflow includes dedicated chapters for these elements. It adjusts the chapter emphasis based on whether the product is a commercial product or an internal enterprise system.

What are the limitations of using automated PRD skeleton generation for new product proposals?

The limitation of automated PRD skeleton generation is that it produces an initial draft with real content but cannot fill gaps where business context is absent, marking these as TODOs instead of making assumptions.