- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add product-on-purpose/pm-skills --skill deliver-prd -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add product-on-purpose/pm-skills --skill deliver-prd -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add product-on-purpose/pm-skills --skill deliver-prd -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add product-on-purpose/pm-skills --skill deliver-prd -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/product-on-purpose/pm-skills/tree/HEAD/skills/deliver-prd来自发布者
A Product Requirements Document is the primary specification artifact that communicates what to build and why. It bridges the gap between problem understanding and engineering implementation by providing clear requirements, success criteria, and scope boundaries. A good PRD enables engineering to build the right thing while maintaining flexibility on implementation details.
define-problem-statement first; a PRD assumes an agreed problemdevelop-solution-brief; the PRD comes after that alignmentdeliver-user-storiesdevelop-adrWhen asked to create a PRD, follow these steps:
Summarize the Problem Start with a brief recap of the problem being solved. Link to the problem statement if available. Ensure readers understand why this work matters before diving into what to build.
Define Goals and Success Metrics Articulate what success looks like. Include specific, measurable metrics with baselines and targets. These metrics should connect directly to the problem being solved.
Outline the Solution Describe the proposed solution at a high level. Focus on user-facing functionality and key capabilities. Include enough detail for stakeholders to evaluate the approach without over-specifying implementation.
Detail Functional Requirements Break down what the system must do. Use user stories or requirement statements. Each requirement should be testable - someone should be able to verify if it's met.
Link AI Behavior to Evidence (only when the feature's output comes from a model) Skip this step entirely for deterministic features. A property that a deterministic check can decide, such as a required field being present or a count matching, does not bring a feature under this step just because a model produced the output; specify it as an ordinary requirement in step 4. When a model produces the output, the behavior varies run to run, so "it works" is a claim that needs evidence attached. Name the behaviors that are requirements of this release and, for each one, how it will be shown to hold and the rule a case must meet to pass, fixed before the run. Refusal and abstention get their own rows: a model has no dependable default for either, so what the feature does when it should not answer is a requirement, not an implementation detail. Score each component of a multi-step feature separately, because an end-to-end pass rate hides which step failed. State how the case set was sized as a method, never as a borrowed number.
Because the same case can pass on one run and fail on the next, the template recommends stating how many times each case runs at production settings and when a case counts as passed. It also recommends two rows that are easy to leave out. When the model reads content that neither the product's instructions nor the user told it to obey, that content is data and never instructions. When the output is shown to people other than the one whose access produced it, it must not reach anyone with less access than its source. A rate, such as "90% of answers are faithful to their sources", can be verified only by a designed sample; until one exists, keep the rate and mark its verification unresolved, with pass rules per case as additional evidence.
Define Scope Boundaries Explicitly state what's in scope, out of scope, and deferred to future iterations. Clear scope prevents scope creep and sets realistic expectations.
Address Technical Considerations Note any technical constraints, architectural decisions, or integration requirements. Don't design the system, but surface considerations engineering needs to know.
Write the Agent Execution Contract (only when an executor will implement this without the authoring context) Skip this step entirely when the implementers were in the room. A coding agent, an outside contractor, or a team picking this up cold cannot infer what you already know, so declare it: which sources are authoritative and which wins when two disagree, what must not be touched and why, how each FR-n is verified and by whom, and the conditions where the executor must stop and escalate rather than decide. Name an owner for every escalation; an escalation with no addressee becomes a guess. A requirement with no verification is not ready to hand off, because nothing distinguishes "done" from "the executor believes it is done".
Identify Dependencies and Risks List external dependencies, assumptions, and risks that could impact delivery. Include mitigation strategies where applicable.
Propose Timeline and Milestones Outline key phases and checkpoints. This helps stakeholders understand the delivery plan without committing to specific dates prematurely.
Active only when .claude/pm-skills.local.md exists. With no file, ignore this section entirely
and behave exactly as described above.
active_initiative, and any interpretation artifacts recording personas or research findings. Use them instead of asking for context that has already been produced. If none exist, ask as normal and never invent a persona to fill the gap.decision artifact, and its committed scope boundaries and success metrics to the ## Decisions section.memory_auto_append: true is set, in which case append and echo what was written.This is the reader half of the demonstration loop: when discover-interview-synthesis has already recorded personas, do not ask the user to supply them again.
Use the template in references/TEMPLATE.md to structure the output. A complete PRD fills every template section: Overview; Goals & Success Metrics; User Stories; Scope; Solution Design; Technical Considerations; Dependencies & Risks; Timeline & Milestones; Open Questions; the Appendix when supporting material exists; AI Behavior and Evaluation when the feature's output comes from a model; and the Agent Execution Contract when an executor will implement it without the authoring context.
The last three are conditional by design. A PRD that omits a section its feature does not need is complete; a PRD that includes an empty one is not.
Before finalizing, verify:
See references/EXAMPLE.md for a completed example.
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for
---name: deliver-prddescription: Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how…---# skills/deliver-prd/SKILL.md概览
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
常见问题
从发布者处下载 skills/deliver-prd/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/product-on-purpose/pm-skills。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。