prd-creator-skill — Summary

prd-creator-skill is a single SKILL.md file (v2.0.0) that implements a 6-phase AI-driven SOP for creating hierarchically structured Product Requirement Documents in Chinese-language enterprise workflows. Phases run from 需求孵化 (Requirement Incubation — multi-round Q&A to clarify vague ideas) through 方案预研 (Solution Research — AI web search for best practices), 项目构建 (Project Construction — directory + README), 模块构建 (Module Construction — module-level PRD), 功能细化 (Feature Refinement — function-level PRD), to 多角色评审 (Multi-Role Review — simulated test/dev/product persona review). The key structural innovation is a three-tier document hierarchy: Project (P001-xxx/) → Module (M001-xxx.md) → Function (F001-xxx.md), with each level carrying its own Mermaid architecture diagrams rendered via the beautiful-mermaid library. At 17 stars, it is a community skill targeting Chinese-speaking product managers and developers who want LLM-assisted PRD authoring within their IDE. Compared to seeds, it most resembles the spec-kit approach of funneling a natural language idea through a structured clarification sequence into a spec artifact, but goes deeper on the document hierarchy and adds a multi-role review simulation absent from any seed.

prd-creator-skill — Overview

Origin

Created by huchi996. Published on GitHub as huchi996/prd-creator-skill. Version 2.0.0, pushed 2026-02-17. MIT license. The skill follows agentskills.io format (SKILL.md frontmatter with name, version, description). The v2.0.0 release notes are in RELEASE-v2.0.0.md.

Philosophy

The skill targets the common enterprise PM workflow where product requirements start as vague verbal descriptions ("我想做一个用户中心平台") and must be refined into structured multi-level specifications before development can begin. The 6-phase SOP is modeled on standard Chinese enterprise SDLC methodology (需求孵化 → 开发). Every phase produces a tangible artifact in a structured file tree rather than a single monolithic document.

Key design decisions:

1. Three-tier hierarchy — P (project) → M (module) → F (function) — matches enterprise-scale product breakdown
2. Multi-role review simulation — Phase 6 simulates test engineer, developer, and product manager review personas, catching specification gaps before development
3. Mermaid diagrams as first-class artifacts — every PRD level includes architecture diagrams rendered by beautiful-mermaid
4. AI web search in Phase 2 — uses SearchWeb to gather competitive analysis and technical best practices before writing specs

Manifesto-style quotes

From SKILL.md description field:

"Create comprehensive Product Requirement Documents (PRD) using an AI-driven 6-phase SOP workflow (需求孵化 -> 方案预研 -> 项目构建 -> 模块构建 -> 功能细化 -> 多角色评审) with multi-role review (测试、研发、产品等角色评审)."

Phase 6 rationale from SKILL.md:

"Based on review findings, update the module and function specs. Fix specification ambiguities. Resolve technical feasibility concerns. Address test coverage gaps."

Target audience

Chinese-speaking product managers, architects, and developers working in enterprise software shops who want a structured, AI-assisted PRD authoring workflow without learning a complex framework.

prd-creator-skill — Architecture

Distribution

Single SKILL.md file + assets/examples/references directories. No CLI, no npm package.

Install

Copy SKILL.md into the AI tool's skills directory (e.g., ~/.claude/skills/prd-creator/SKILL.md).

Required runtime

None (just the AI host tool)

Directory tree (as installed)

prd-creator-skill/
├── SKILL.md             # The skill itself (6-phase SOP)
├── README.md
├── CHANGELOG.md
├── RELEASE-v2.0.0.md
├── assets/              # Mermaid diagram assets
├── examples/            # Example PRD outputs
└── references/          # Reference materials

Output directory tree (produced by skill)

prd/
├── P001-用户中心平台/           # Project directory
│   ├── README.md               # Project overview (scope, goals, roadmap)
│   ├── M001-用户认证.md        # Module document with Mermaid architecture
│   ├── M001/                   # Function subdirectory
│   │   ├── F001-注册登录.md
│   │   ├── F002-密码找回.md
│   │   └── F003-第三方登录.md
│   ├── M002-账户管理.md
│   └── M002/
│       ├── F001-资料修改.md
│       └── F002-账号注销.md
├── P002-xxx/
└── ...

Naming convention

• Project: P{三位编号}-{项目名}/ — e.g., P001-用户中心平台/
• Module: P{编号}/M{三位编号}-{模块名}.md — e.g., M001-用户认证.md
• Function: P{编号}/M{编号}/F{三位编号}-{功能名}.md — e.g., F001-注册登录.md

Target AI tools

Any agentskills.io-compatible tool with web search capability (Phase 2 uses SearchWeb). Claude Code is the primary target.

External dependencies

• beautiful-mermaid library for Mermaid SVG rendering (referenced but not bundled)
• SearchWeb capability in the AI host (for Phase 2 competitive research)

prd-creator-skill — Components

Single Skill

6 Phases within the Skill

Templates

Role Simulations (Phase 6)

The skill instructs the AI to simulate:

• 测试工程师 (Test Engineer): Checks testability, edge cases, coverage gaps
• 研发工程师 (Development Engineer): Checks technical feasibility, API completeness, performance concerns
• 产品经理 (Product Manager): Checks business alignment, user experience, priority clarity

External Tool Call

Phase 2 explicitly calls SearchWeb to gather competitive analysis and technical best practices — the only skill in this batch that makes web search a first-class phase.

prd-creator-skill — Uniqueness

Differs from Seeds

Closest seed is spec-kit — both convert a natural language idea into a structured spec through a clarification loop. prd-creator diverges in three ways: (1) it adds a three-tier document hierarchy (Project → Module → Function) whereas spec-kit produces a single flat spec file; (2) it includes a Phase 2 competitive research step using SearchWeb before writing any spec, which no seed framework does; (3) it simulates multi-role review in Phase 6 (test/dev/product personas) as a specification quality gate, not a code review gate. Compared to openspec (which also targets full SDLC), prd-creator is narrower — it covers only the requirements authoring phase, not implementation or task management. It is the only Chinese-language skill in this batch and appears to target enterprise PM workflows in the Chinese tech industry.

Positioning

Occupies the "idea-to-structured-PRD" slot with unusual depth: most PRD tools stop at a single document, whereas prd-creator enforces hierarchical decomposition all the way to individual function files. The multi-role review simulation is the most distinctive feature — it operationalizes structured spec review without requiring separate review agents.

Observable Failure Modes

1. SearchWeb dependency in Phase 2: If the AI host lacks web search capability, Phase 2 silently falls back to training-data knowledge. The spec may miss real competitive context.
2. Persona simulation fidelity: The three-role review in Phase 6 is a single-model role-play, not genuine adversarial agents. A sufficiently aligned LLM may not challenge its own prior work effectively.
3. Context window stress: Phase 6 reads ALL module and function docs simultaneously. On large projects (5+ modules, 10+ functions each), this can exceed practical context limits.
4. Chinese-only terminology: The phase names and many output document titles are in Chinese, creating a language barrier for non-Chinese teams.
5. No enforcement beyond prompting: Nothing prevents skipping Phase 6 review — the skill is guidance only.