prd-creator by closedloop-ai/claude-plugins
npx skills add https://github.com/closedloop-ai/claude-plugins --skill prd-creator我们撰写文档是为了达成共识,而非寻求批准。一份 PRD 应回答:
当产品经理(PM)有一个初步想法时,通过对话引导他们:
不要一次性问完所有问题。进行对话。用合理的假设填补空白,并将其标记为待解决问题。
查看 references/examples.md 获取探索对话示例。
当准备撰写时,使用 assets/prd-template.md。该模板包含:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
在导出到 Jira 之前,使用此模式为故事添加验收标准。PM 的工作流程是:
jira-prd-export 创建包含完整验收标准的史诗/故事扩展一个故事:
references/story-patterns.md 获取常见模式查看 references/examples.md 获取故事扩展示例。
将故事组织成史诗时:
查看 references/examples.md 获取史诗格式示例。
当 PM 询问现有功能或可行性时:
| 需求 | 输出 |
|---|---|
| 快速达成共识 | 聊天中的 Markdown,无需文件 |
| 冲刺规划 | PRD 文件 → confluence-prd-export → jira-prd-export |
| Symphony 流水线 | PRD 文件 → prd-analyst → requirements.json |
一致的编号确保在 Symphony 流水线中的可追溯性:
| 类型 | 格式 | 示例 |
|---|---|---|
| 用户故事 | US-### | US-001, US-002 |
| 验收标准 | AC-###.# | AC-001.1, AC-001.2 |
| 待解决问题 | Q-### | Q-001, Q-002 |
使用此技能创建的 PRD 会输入到 Symphony 的规划流水线中:
prd-creator → PRD.md → prd-analyst → requirements.json → plan-writer → implementation-plan.md
prd-analyst 代理提取:
user_stories[]acceptance_criteria[]success_metrics[]open_questions[]constraints[]使用 TodoWrite 来跟踪每个工作流模式的进度。
TodoWrite([
{"content": "理解问题和用户痛点", "status": "pending", "activeForm": "Understanding the problem"},
{"content": "收集证明其重要性的证据", "status": "pending", "activeForm": "Gathering evidence"},
{"content": "识别目标用户画像", "status": "pending", "activeForm": "Identifying personas"},
{"content": "定义成功指标", "status": "pending", "activeForm": "Defining success metrics"},
{"content": "确定第一版切片 / MVP 范围", "status": "pending", "activeForm": "Scoping MVP"},
{"content": "识别风险和合规性问题", "status": "pending", "activeForm": "Identifying risks"}
])
TodoWrite([
{"content": "撰写概述部分", "status": "pending", "activeForm": "Writing Overview"},
{"content": "撰写背景部分", "status": "pending", "activeForm": "Writing Background"},
{"content": "撰写目标与成功指标", "status": "pending", "activeForm": "Writing Goals & Success Metrics"},
{"content": "撰写带有 US-### 编号的用户故事", "status": "pending", "activeForm": "Writing User Stories"},
{"content": "撰写需求(功能性 + 非功能性)", "status": "pending", "activeForm": "Writing Requirements"},
{"content": "撰写用户体验(工作流、边界情况)", "status": "pending", "activeForm": "Writing User Experience"},
{"content": "撰写技术考量", "status": "pending", "activeForm": "Writing Technical Considerations"},
{"content": "撰写验收标准", "status": "pending", "activeForm": "Writing Acceptance Criteria"},
{"content": "记录带有 Q-### 编号的待解决问题", "status": "pending", "activeForm": "Documenting questions"},
{"content": "定义范围外", "status": "pending", "activeForm": "Defining Out of Scope"},
{"content": "撰写风险与缓解措施", "status": "pending", "activeForm": "Writing Risks & Mitigations"}
])
TodoWrite([
{"content": "选择要扩展的用户故事", "status": "pending", "activeForm": "Selecting story"},
{"content": "生成验收标准(假设/当/那么)", "status": "pending", "activeForm": "Generating acceptance criteria"},
{"content": "分配 AC-###.# 编号", "status": "pending", "activeForm": "Assigning AC IDs"},
{"content": "对照 story-patterns.md 进行审查", "status": "pending", "activeForm": "Reviewing patterns"}
])
只有在 PM 确认达成共识后,才将每个任务标记为完成。对于探索模式,随着对话的进行,任务可能会被重新审视。
每周安装数
1
仓库
GitHub 星标数
71
首次出现
今天
安全审计
安装于
windsurf1
amp1
cline1
openclaw1
opencode1
cursor1
We document for alignment , not approval. A PRD answers:
When PM has a rough idea, guide them through conversationally:
Don't ask all at once. Have a conversation. Fill gaps with reasonable assumptions and flag them as open questions.
See references/examples.md for a sample Discovery conversation.
When ready to write, use assets/prd-template.md. The template includes:
Use this mode to add acceptance criteria to stories before exporting to Jira. The PM workflow is:
jira-prd-export to create epics/stories with full ACsTo expand a story:
references/story-patterns.md for common patternsSee references/examples.md for story expansion examples.
When organizing stories into epics:
See references/examples.md for epic format example.
When PM asks about existing features or feasibility:
| Need | Output |
|---|---|
| Quick alignment | Markdown in chat, no file needed |
| Sprint planning | PRD file → confluence-prd-export → jira-prd-export |
| Symphony pipeline | PRD file → prd-analyst → requirements.json |
Consistent IDs enable traceability through the Symphony pipeline:
| Type | Format | Example |
|---|---|---|
| User Story | US-### | US-001, US-002 |
| Acceptance Criteria | AC-###.# | AC-001.1, AC-001.2 |
| Open Question | Q-### | Q-001, Q-002 |
PRDs created with this skill feed into Symphony's planning pipeline:
prd-creator → PRD.md → prd-analyst → requirements.json → plan-writer → implementation-plan.md
The prd-analyst agent extracts:
user_stories[]acceptance_criteria[]success_metrics[]open_questions[]constraints[]Use TodoWrite to track progress through each workflow mode.
TodoWrite([
{"content": "Understand the problem and user pain", "status": "pending", "activeForm": "Understanding the problem"},
{"content": "Gather evidence for why this matters", "status": "pending", "activeForm": "Gathering evidence"},
{"content": "Identify target persona(s)", "status": "pending", "activeForm": "Identifying personas"},
{"content": "Define success metrics", "status": "pending", "activeForm": "Defining success metrics"},
{"content": "Scope the first slice / MVP", "status": "pending", "activeForm": "Scoping MVP"},
{"content": "Identify risks and compliance concerns", "status": "pending", "activeForm": "Identifying risks"}
])
TodoWrite([
{"content": "Write Overview section", "status": "pending", "activeForm": "Writing Overview"},
{"content": "Write Background section", "status": "pending", "activeForm": "Writing Background"},
{"content": "Write Goals & Success Metrics", "status": "pending", "activeForm": "Writing Goals & Success Metrics"},
{"content": "Write User Stories with US-### IDs", "status": "pending", "activeForm": "Writing User Stories"},
{"content": "Write Requirements (Functional + Non-Functional)", "status": "pending", "activeForm": "Writing Requirements"},
{"content": "Write User Experience (Workflows, Edge Cases)", "status": "pending", "activeForm": "Writing User Experience"},
{"content": "Write Technical Considerations", "status": "pending", "activeForm": "Writing Technical Considerations"},
{"content": "Write Acceptance Criteria", "status": "pending", "activeForm": "Writing Acceptance Criteria"},
{"content": "Document Open Questions with Q-### IDs", "status": "pending", "activeForm": "Documenting questions"},
{"content": "Define Out of Scope", "status": "pending", "activeForm": "Defining Out of Scope"},
{"content": "Write Risks & Mitigations", "status": "pending", "activeForm": "Writing Risks & Mitigations"}
])
TodoWrite([
{"content": "Select user story to expand", "status": "pending", "activeForm": "Selecting story"},
{"content": "Generate acceptance criteria (Given/When/Then)", "status": "pending", "activeForm": "Generating acceptance criteria"},
{"content": "Assign AC-###.# IDs", "status": "pending", "activeForm": "Assigning AC IDs"},
{"content": "Review against story-patterns.md", "status": "pending", "activeForm": "Reviewing patterns"}
])
Mark each task completed only after the PM confirms alignment. For Discovery Mode, tasks may be revisited as the conversation evolves.
Weekly Installs
1
Repository
GitHub Stars
71
First Seen
Today
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
windsurf1
amp1
cline1
openclaw1
opencode1
cursor1
超能力技能使用指南:AI助手技能调用优先级与工作流程详解
45,100 周安装