菜单
Write PRD — Product Requirements Documents with structured 8-section templates, user stories, acceptance criteria, and value proposition validation. Use when writing PRDs, defining product requirements, creating user stories with INVEST criteria, or building go/no-go decision frameworks.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/yonatangross/orchestkit --skill write-prd命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Chain patterns for multi-phase pipelines: MCP detection, handoff files, checkpoint-resume, worktree agents, CronCreate monitoring. Use when building or debugging a pipeline skill.
OrchestKit doctor for health diagnostics across manifest integrity, hook configuration, skill validation, agent frontmatter, MCP server connectivity, CC version compatibility, and permission rules. Reports issues with severity levels and auto-remediation suggestions. Validates component counts, detects orphaned entries, and checks CC version matrix compliance. Use when diagnosing plugin health, troubleshooting configuration issues, or running pre-release checks.
Inspects the OrchestKit telemetry pipeline for the current project — lists all known telemetry files with write counts, sizes, schema status, growth trend, and orphan detection. Use when verifying the observability pipeline is healthy, debugging a missing writer, or auditing which files have schema locks vs. which are drift-vulnerable. Read-only — never modifies telemetry files.
正在显示 SKILL.md
| name | write-prd |
| license | MIT |
| compatibility | Claude Code 2.1.220+. |
| description | Write PRD — Product Requirements Documents with structured 8-section templates, user stories, acceptance criteria, and value proposition validation. Use when writing PRDs, defining product requirements, creating user stories with INVEST criteria, or building go/no-go decision frameworks. |
| tags | ["prd","requirements","user-story","acceptance-criteria","invest","value-proposition","go-no-go"] |
| context | fork |
| background | false |
| agent | product-strategist |
| version | 2.0.1 |
| author | OrchestKit |
| user-invocable | true |
| argument-hint | product name or feature |
| disable-model-invocation | false |
| complexity | medium |
| persuasion-type | collaborative |
| metadata | {"category":"document-asset-creation"} |
| allowed-tools | ["Read","Write","Edit","Glob","Grep","Bash","WebFetch","WebSearch","AskUserQuestion","TaskCreate","TaskUpdate","Agent","mcp__memory__search_nodes","mcp__memory__create_entities","mcp__memory__add_observations","mcp__memory__create_relations"] |
| triggers | {"keywords":["prd","product requirements","requirements document","requirements for","define the requirements","user stories","acceptance criteria","product spec","formal spec"],"examples":["write a PRD for the SSO invite flow","create a product requirements document for billing","i need user stories and acceptance criteria for the dashboard"],"anti-triggers":["implement","build","brainstorm","explore","review"]} |
Translate product vision and research into clear, actionable engineering specifications. Produces PRD-[product-name].md output files following an 8-section structure.
Output file naming: PRD-[product-name].md (e.g., PRD-sso-invite-flow.md)
PRODUCT = "$ARGUMENTS" # Product name or feature, e.g., "SSO invite flow"
AskUserQuestion(
questions=[{
"question": "What type of PRD?",
"header": "PRD Scope",
"options": [
{"label": "Full PRD (Recommended)", "description": "All 8 sections with research, stories, and release plan"},
{"label": "Lightweight spec", "description": "Summary, objectives, user stories only"},
{"label": "User stories only", "description": "INVEST stories with acceptance criteria"},
{"label": "Update existing PRD", "description": "I have a PRD file to iterate on"}
],
"multiSelect": false
}]
)
# 1. Create main task IMMEDIATELY
TaskCreate(subject="Write PRD: {PRODUCT}", description="8-section PRD with user stories and acceptance criteria", activeForm="Writing PRD for {PRODUCT}")
# 2. Create subtasks for each phase
TaskCreate(subject="Scope clarification", activeForm="Clarifying PRD scope") # id=2
TaskCreate(subject=, activeForm=)
TaskCreate(subject=, activeForm=)
TaskCreate(subject=, activeForm=)
TaskCreate(subject=, activeForm=)
TaskUpdate(taskId=, addBlockedBy=[])
TaskUpdate(taskId=, addBlockedBy=[])
TaskUpdate(taskId=, addBlockedBy=[])
TaskUpdate(taskId=, addBlockedBy=[])
TaskUpdate(taskId=, status=)
TaskUpdate(taskId=, status=)
# Search for prior PRDs and product decisions
mcp__memory__search_nodes(query="{PRODUCT} PRD requirements")
# After PRD is written, store key decisions
mcp__memory__create_entities(entities=[{
"name": "PRD-{product-slug}",
"entityType": "document",
"observations": ["PRD written for {PRODUCT}", "Key objectives: ..."]
}])
Load Read("${CLAUDE_PLUGIN_ROOT}/skills/write-prd/references/prd-template.md") for the full template with all 8 sections (Summary, Contacts, Background, Objective, Market Segments, Value Propositions, Solution, Release), priority levels, and NFR categories.
Load Read("${CLAUDE_PLUGIN_ROOT}/skills/write-prd/references/user-stories-guide.md") for INVEST criteria, story format, Gherkin acceptance criteria, and Definition of Ready/Done.
Load Read("${CLAUDE_PLUGIN_ROOT}/skills/write-prd/references/value-prop-canvas-guide.md") for the canvas template and fit check process. Every Value Map item must correspond to a Job, Pain, or Gain.
Load from rules: Read("${CLAUDE_PLUGIN_ROOT}/skills/write-prd/rules/strategy-go-no-go.md") for stage gate criteria and scoring thresholds (Go >= 7.0 | Conditional 5.0-6.9 | No-Go < 5.0).
After generating the PRD, write it to disk:
Write(f"PRD-{product_slug}.md", prd_content)
TaskUpdate(status="completed")
Plan-mode filenames (CC 2.1.111+): If this skill enters plan mode (via
EnterPlanMode) before writing the PRD, CC 2.1.111 names the resulting plan file after the prompt stem rather than random words. To get a clean filename, include the product slug in the plan-mode prompt (e.g.EnterPlanMode("PRD: authentication-rework")→plans/prd-authentication-rework.md). Before 2.1.111, plan filenames wereplans/swift-cobra.mdetc. — review and rename as needed.
After PRD is approved, decompose its acceptance criteria into a runnable goal, then implement:
/ork:prd-to-goal PRD-{product-slug}.md # → one copy-pasteable `/goal until …, or stop after N turns` line
/ork:implement PRD-{product-slug}.md
/ork:prd-to-goal reduces the Go/No-Go gate + acceptance criteria below into a single AND-joined boolean assertion, so the PRD drives an autonomous /goal run rather than a manual read-through.
ork:user-research — Build user understanding (personas, journey maps, interviews) before writing the PRDork:prd-to-goal — Reduce this PRD's acceptance criteria to a single /goal until …, or stop after N turns lineork:implement — Execute the implementation plan from the PRDork:brainstorm — Explore solution alternatives before committing to PRD scopeork:assess — Rate PRD quality and completenessVersion: 2.0.0