pm-humanprd

Generate a human-readable PRD from PMContext with decision rationale and traceability.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams turn a structured PMContext into a human-readable PRD that reviewers can quickly understand and evaluate. It is especially useful when stakeholders need clear business rationale, decision tradeoffs, risks, and traceability instead of implementation-heavy specs.

Core Features & Use Cases

  • Human-readable PRD generation: Produces a review-friendly PRD focused on what to build, why it matters, and how success will be measured.
  • Decision rationale and traceability: Maps each requirement back to PMContext sections, decision points, and risk handling so reviewers can verify the logic behind the document.
  • Uncertainty-aware review drafts: Preserves [待确认], [假设], and [冲突] markers instead of masking ambiguity, making it safer for stakeholder review.
  • Use Case: After a discovery workflow produces PMContext for a feature proposal, use this Skill to generate a stakeholder-facing PRD for product review meetings, leadership alignment, or cross-functional feedback.

Quick Start

Ask the agent to generate a human-readable PRD from the existing PMContext for stakeholder review.

Frequently Asked Questions about pm-humanprd

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

FAQPage Schema
How do I generate a human-readable PRD for stakeholder review from product context?▼

Generate a human-readable PRD by transforming structured product context into a review-friendly document focused on business value, decision rationale, and traceability rather than implementation details.

What is the best way to preserve unresolved items and assumptions in a product requirements document?▼

Preserve unresolved items in a product requirements document by retaining specific markers for assumptions, conflicts, and items pending confirmation instead of masking ambiguity during stakeholder review.

How do I map decision rationale and traceability links back to product context sections?▼

Map decision rationale and traceability by linking each requirement directly back to corresponding product context sections, decision points, and risk handling records within the generated document.

Can I use this PRD generation approach for cross-functional product evaluation and leadership alignment?▼

Yes, this PRD generation approach suits cross-functional product evaluation and leadership alignment by emphasizing tradeoffs, business logic, and review clarity over technical implementation specifications.

Does generating a stakeholder-facing PRD require implementation-oriented specifications as input?▼

No, generating a stakeholder-facing PRD requires structured product context as input rather than implementation-oriented specifications, focusing the output on business value and stakeholder review clarity.

Why does my product requirements document lack clear business rationale and decision tradeoffs for reviewers?▼

A product requirements document lacks clear business rationale when it is implementation-heavy; generating a review-friendly PRD from product context explicitly extracts decision tradeoffs and risk handling for stakeholder evaluation.