pm-prd

Generate dual-format PRDs from PMContext with strict traceability.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-prd-wcof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-prd
Source: https://github.com/Wcof/PMSkill/tree/main/skills/delivery/pm-prd
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-prd-wcof

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams turn a structured PMContext into two aligned PRD outputs: one optimized for AI execution and one optimized for human review. It prevents teams from drafting requirement documents directly from vague chat context, which often leads to lost assumptions, untraceable decisions, and inconsistent delivery artifacts.

Core Features & Use Cases

  • Dual-form PRD generation: Produces both ai-prd.md and human-prd.md from the same PMContext source so execution rules and review narrative stay aligned.
  • Strict traceability: Ensures every rule, acceptance criterion, and boundary maps back to facts, assumptions, conflicts, or decisions already captured in PMContext.
  • Workflow orchestration: Coordinates downstream PRD generation steps, supports auto mode, and handles missing PMContext by routing through the upstream requirement flow when arguments are provided.
  • Risk-aware output: Preserves [待确认] and [冲突] signals instead of upgrading them into facts, and limits output when uncertainty is too high.
  • Use case: A product manager has already captured user needs, constraints, and open questions in PMContext and now needs both an AI-executable product spec for implementation support and a human-readable PRD for stakeholder review.

Quick Start

Ask the agent to run pm-prd on your existing PMContext to generate both the AI PRD and the human PRD, or provide a requirement description with auto mode to create the context and PRDs in one flow.

Frequently Asked Questions about pm-prd

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

FAQPage Schema
How do I generate AI-executable and human-readable PRDs from existing requirements?

Generating dual-format product requirement documents requires orchestrating PMContext into aligned AI-executable and human-readable files. This process maps rules and acceptance criteria directly to source facts, ensuring both execution specs and stakeholder narratives stay consistent.

What is PMContext traceability in product specifications?

PMContext traceability ensures every rule, acceptance criterion, and boundary in a product specification maps back to captured facts, assumptions, conflicts, or decisions. This prevents lost context and untraceable decisions when converting discovered requirements into delivery artifacts.

Can I generate product requirement documents automatically if PMContext is missing?

Yes, auto mode supports generating product requirement documents when PMContext is missing by routing through the upstream requirement flow using provided arguments. This creates the context and outputs both AI and human PRDs in one continuous workflow.

How are unresolved conflicts and assumptions handled during PRD generation?

Unresolved conflicts and assumptions are preserved as [待确认] and [冲突] markers during PRD generation rather than being upgraded into facts. Output is limited when uncertainty is too high to ensure risk-aware and traceable product specifications.

Do I need a structured PMContext to create review-ready PRDs?

Yes, creating review-ready PRDs requires reading a configured PMContext path to ensure strict traceability to source facts. Without it, you must use auto mode and provide requirement descriptions to trigger the upstream context creation flow.