[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J040PNVSC4NMEEAF5SP313":3,"skill-same:01M6J040PNVSC4NMEEAF5SP313":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":48,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6J040PNVSC4NMEEAF5SP313","pm-iteration",null,"Use when: 需要规划迭代内容、制定迭代排期、明确迭代优先级、从需求到排期的落地\nDo NOT use when: 迭代已由团队自行规划、无需系统化管理","konglong87\u002FsuperPM","konglong87","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38234954?v=4","01M6HZZN5EA0572RY1RZAFRKHV","to be a better gopher","01M6HZZN9YN157X26KMMAA147E",90,"MIT","https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002F03-growth-iteration\u002Fpm-iteration\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31],"pm","iteration","pm iteration","Bash","read","write","use","do","2026-11-10 10:12:30",false,"---\nname: pm-iteration\ndescription: |\n  Use when: 需要规划迭代内容、制定迭代排期、明确迭代优先级、从需求到排期的落地\n  Do NOT use when: 迭代已由团队自行规划、无需系统化管理\nallowed-tools:\n  - Agent\n  - Read\n  - Write\n  - AskUserQuestion\n  - Bash\n---\n\n## Preamble\n\n```bash\necho \"? 迭代计划工具已启动\"\n\n# 检查前置数据\necho \"? 正在检查前置数据...\"\nif [ -f \"docs\u002F03-增长迭代\u002F数据报告与用户反馈.md\" ]; then\n  echo \"✅ 数据报告 - 已找到\"\nfi\nif [ -f \"docs\u002F03-增长迭代\u002F产品路线图.md\" ]; then\n  echo \"✅ 产品路线图 - 已找到\"\nfi\n```\n\n---\n\n## 写入时边界\n\n只讨论时不写文件，启动检查不创建目录。用户要求保存产物时，先确认当前产品、精确输出路径及已有文件的覆盖\u002F追加选择；确认后**仅在实际 Write 前**创建该输出文件的父目录。完整安装可参见 `skills\u002F_shared\u002Fartifact-policy.md`，单独安装本 skill 也按本段执行。\n\n---\n\n## 跨 Agent 交互规则\n\n当流程要求与用户交互时：\n\n1. 如果当前环境支持 AskUserQuestion，使用 AskUserQuestion（最佳体验）。\n2. 如果当前环境不支持 AskUserQuestion，必须用普通聊天消息提出同样问题。\n3. 一次只问一个问题。\n4. 提问后必须停止当前回合，等待用户回答（STOP and WAIT）。\n5. 不得在用户回答前生成文档、写入 docs。\n6. 已有 docs 文件不能替代本轮用户回答。\n\n---\n\n## 执行流程\n\n\n### 步骤 1: 确定迭代范围\n\n使用 AskUserQuestion 询问：\n\n> ? 迭代规划\n>\n> **迭代编号**：第X次迭代\n> **迭代周期**：建议2周\n>\n> 本次迭代的输入来源：\n>\n> A) 数据分析结果（数据驱动优化）\n> B) 用户反馈（用户需求驱动）\n> C) 竞品分析（市场变化驱动）\n> D) 技术优化（性能\u002F架构提升）\n> E) 业务目标（战略调整）\n> F) 以上多项组合\n> G) 产品路线图拆解（从长期规划中提取）\n>\n> ? 提示：建议每次迭代聚焦1-2个核心目标\n\n记录到变量 `ITERATION_INPUT`\n\n---\n\n### 步骤 2: 设定迭代目标\n\n> ? 设定迭代目标\n>\n> 本次迭代的核心目标是什么？（建议1-2个）\n>\n> **目标示例**：\n> - 提升注册转化率至30%\n> - 完成XX功能开发上线\n> - 修复Top 5用户反馈问题\n>\n> **目标1**：{目标描述}\n> **目标2**：{目标描述}\n>\n> 每个目标需要可衡量，如\"将XX指标从X%提升到Y%\"\n\n---\n\n### 步骤 3: 收集迭代需求\n\n> ? 本次迭代的需求清单：\n>\n> 请列出本次迭代需要完成的需求\u002F任务（每个一行）：\n>\n> 示例：\n> - 优化注册流程（来源：数据驱动 - 注册转化率低）\n> - 新增商品搜索功能（来源：用户反馈）\n> - 修复首页加载慢问题（来源：技术优化）\n>\n> 输入\"完成\"结束录入\n\n收集到列表 `REQUIREMENT_LIST`\n\n---\n\n### 步骤 4: 需求优先级排序\n\n基于价值和成本对需求排序：\n\n> ? 需求优先级排序\n>\n> **P0（必须有）**：影响核心目标或阻塞其他需求\n> **P1（应该有）**：重要但不紧急\n> **P2（可以有）**：锦上添花\n>\n> 对每个需求确认优先级：\n>\n> 需求\"{需求名称}\"的优先级？\n>\n> A) P0 - 必须有\n> B) P1 - 应该有\n> C) P2 - 可以有\n> D) 推迟到下次迭代\n\n---\n\n### 步骤 5: 资源分配与排期\n\n> ? 资源分配：\n>\n> 可用开发资源：\n> - 前端：[X]人\n> - 后端：[X]人\n> - 设计：[X]人\n> - QA：[X]人\n>\n> **工时估算**：\n>\n> | 需求 | 优先级 | 前端工时 | 后端工时 | 总工时 |\n> |------|--------|---------|---------|--------|\n> | {需求1} | P0 | X天 | X天 | X天 |\n> | {需求2} | P0 | X天 | X天 | X天 |\n> | {需求3} | P1 | X天 | X天 | X天 |\n> | **合计** | | **X天** | **X天** | **X天** |\n>\n> **风险评估**：\n> - 总工时是否在迭代容量内？\n> - 是否存在阻塞依赖？\n> - 是否需要调整范围？\n\n---\n\n### 步骤 6: 输出迭代计划\n\n使用 Write 工具创建 `docs\u002F03-增长迭代\u002F迭代计划-v{版本号}.md`：\n\n```markdown\n# 迭代计划 v{版本号}\n\n## 一、迭代概览\n\n- **迭代编号**：第X次迭代\n- **周期**：YYYY-MM-DD 至 YYYY-MM-DD（2周）\n- **核心目标**：\n  1. {目标1}\n  2. {目标2}\n\n## 二、需求清单\n\n| 优先级 | 需求名称 | 来源 | 前端工时 | 后端工时 | 负责人 |\n|--------|---------|------|---------|---------|--------|\n| P0 | {需求1} | {来源} | X天 | X天 | {负责人} |\n| P0 | {需求2} | {来源} | X天 | X天 | {负责人} |\n| P1 | {需求3} | {来源} | X天 | X天 | {负责人} |\n| P2 | {需求4} | {来源} | X天 | X天 | {负责人} |\n\n## 三、排期计划\n\n### 第1周\n- Day 1-2：{任务}\n- Day 3-4：{任务}\n- Day 5：{任务}\n\n### 第2周\n- Day 6-7：{任务}\n- Day 8-9：{任务}\n- Day 10：交付\u002F测试\u002F上线\n\n## 四、风险与预案\n\n| 风险 | 概率 | 影响 | 预案 |\n|------|------|------|------|\n| {风险} | H\u002FM\u002FL | H\u002FM\u002FL | {预案} |\n\n## 五、验收标准\n\n- 所有P0需求完成开发并测试通过\n- {目标1}达成：{衡量标准}\n- {目标2}达成：{衡量标准}\n\n---\n\n**文档状态**: 迭代计划完成\n**生成时间**: {时间戳}\n**生成工具**: super-pm\n```\n\n---\n\n### 步骤 7: 完成提示\n\n> ✅ 迭代计划完成！\n>\n> ? 已生成：`docs\u002F03-增长迭代\u002F迭代计划-v{版本号}.md`\n>\n> ? 建议下一步：\n>\n> A) 执行 \u002Fpm-risk - 风险管控方案\n> B) 执行 \u002Fpm-agile - 敏捷管理方案\n> C) 迭代开始后执行 \u002Fpm-report 跟踪进度\n\n---\n\n## 兜底机制\n\n### 场景: 需求过多\n\n如果需求总工时超过迭代容量：\n\n> ⚠️ 需求总工时{X天}超过迭代容量{标准容量}\n>\n> 建议：\n> A) 将部分P1\u002FP2需求推迟到下个迭代\n> B) 增加开发资源\n> C) 延长迭代周期\n\n---\n\n## V2 并行架构升级\n\n### 架构概览\n\n\n### 并行Subagent分析\n\n在确认需求清单后，并发派发4个Subagent：\n\n**Subagent 1: 需求分析**\n- 负责：评估需求的业务价值、用户影响面、关联度\n\n**Subagent 2: 工时估算**\n- 负责：基于历史数据估算各需求开发工时、测试工时\n\n**Subagent 3: 依赖分析**\n- 负责：识别需求间的技术依赖、团队依赖、外部依赖\n\n**Subagent 4: 风险分析**\n- 负责：识别排期风险、资源瓶颈、技术风险\n\n### V1 vs V2 对比\n\n| 指标 | V1（顺序分析） | V2（并行分析） | 提升 |\n|------|--------------|--------------|------|\n| **分析时间** | ~5分钟 | ~2分钟 | 2.5x |\n| **主Agent上下文** | ~12,000 tokens | ~3,500 tokens | 节省71% |\n| **分析维度** | 手动逐项估算 | 4维度并行评估 | - |\n| **排期准确性** | 依赖经验 | 多维度交叉验证 | 更准确 |\n\n---\n\n## 注意事项\n\n1. 每个迭代聚焦1-2个核心目标，避免目标过多\n2. P0需求不超过迭代容量的60%\n3. 预留20%缓冲时间应对突发问题\n4. 迭代计划在迭代开始前确认并周知团队\n\n---\n\n## 输出质量对比\n\n**✅ Good 示例**：\n```\n- 有数据引用：「根据 Q4 数据，留存率从 35% 降至 28%」\n- 有验证来源：「数据来源：Google Analytics, 2025-12-01」\n- 有明确建议：「建议将新手引导步骤从 5 步减少至 3 步」\n```\n\n**❌ Bad 示例**：\n```\n- 模糊结论：「数据表明留存率有所下降」\n- 无来源：「根据经验，这个功能很重要」\n- 没有行动建议：「留存是个问题」\n```\n\n---\n\n## 常见误区 \u002F Red Flags — STOP\n\n出现以下情况立即停止并回溯：\n\n| 误区 | 正确做法 |\n|------|---------|\n| 使用\"应该\"、\"大概\"、\"看起来\"做结论 | 必须基于实际数据和验证 |\n| 未运行检查就声称已完成 | 先验证，再陈述 |\n| 因时间紧迫跳过关键步骤 | 没有例外，时间紧更要严格 |\n| \"这次应该没问题\"的想法 | 每次都要重新验证 |\n\n---\n\n## 产出质量检查 \u002F Verification Checklist\n\n- [ ] 前置依赖已满足（输入文档\u002F数据已收集）\n- [ ] 核心步骤已全部执行\n- [ ] 输出文档已生成到 `docs\u002F` 目录\n- [ ] 每个判断都有数据\u002F证据支撑\n- [ ] 已推荐 2-3 个后续 skill\n\n> ⚠️ 任何一项未通过 → 补全后再标记完成。\n\n---\n","## Preamble\n\n```bash\necho \"? 迭代计划工具已启动\"\n\n# 检查前置数据\necho \"? 正在检查前置数据...\"\nif [ -f \"docs\u002F03-增长迭代\u002F数据报告与用户反馈.md\" ]; then\n  echo \"✅ 数据报告 - 已找到\"\nfi\nif [ -f \"docs\u002F03-增长迭代\u002F产品路线图.md\" ]; then\n  echo \"✅ 产品路线图 - 已找到\"\nfi\n```\n\n---\n\n## 写入时边界\n\n只讨论时不写文件，启动检查不创建目录。用户要求保存产物时，先确认当前产品、精确输出路径及已有文件的覆盖\u002F追加选择；确认后**仅在实际 Write 前**创建该输出文件的父目录。完整安装可参见 `skills\u002F_shared\u002Fartifact-policy.md`，单独安装本 skill 也按本段执行。\n\n---\n\n## 跨 Agent 交互规则\n\n当流程要求与用户交互时：\n\n1. 如果当前环境支持 AskUserQuestion，使用 AskUserQuestion（最佳体验）。\n2. 如果当前环境不支持 AskUserQuestion，必须用普通聊天消息提出同样问题。\n3. 一次只问一个问题。\n4. 提问后必须停止当前回合，等待用户回答（STOP and WAIT）。\n5. 不得在用户回答前生成文档、写入 docs。\n6. 已有 docs 文件不能替代本轮用户回答。\n\n---\n\n## 执行流程\n\n\n### 步骤 1: 确定迭代范围\n\n使用 AskUserQuestion 询问：\n\n> ? 迭代规划\n>\n> **迭代编号**：第X次迭代\n> **迭代周期**：建议2周\n>\n> 本次迭代的输入来源：\n>\n> A) 数据分析结果（数据驱动优化）\n> B) 用户反馈（用户需求驱动）\n> C) 竞品分析（市场变化驱动）\n> D) 技术优化（性能\u002F架构提升）\n> E) 业务目标（战略调整）\n> F) 以上多项组合\n> G) 产品路线图拆解（从长期规划中提取）\n>\n> ? 提示：建议每次迭代聚焦1-2个核心目标\n\n记录到变量 `ITERATION_INPUT`\n\n---\n\n### 步骤 2: 设定迭代目标\n\n> ? 设定迭代目标\n>\n> 本次迭代的核心目标是什么？（建议1-2个）\n>\n> **目标示例**：\n> - 提升注册转化率至30%\n> - 完成XX功能开发上线\n> - 修复Top 5用户反馈问题\n>\n> **目标1**：{目标描述}\n> **目标2**：{目标描述}\n>\n> 每个目标需要可衡量，如\"将XX指标从X%提升到Y%\"\n\n---\n\n### 步骤 3: 收集迭代需求\n\n> ? 本次迭代的需求清单：\n>\n> 请列出本次迭代需要完成的需求\u002F任务（每个一行）：\n>\n> 示例：\n> - 优化注册流程（来源：数据驱动 - 注册转化率低）\n> - 新增商品搜索功能（来源：用户反馈）\n> - 修复首页加载慢问题（来源：技术优化）\n>\n> 输入\"完成\"结束录入\n\n收集到列表 `REQUIREMENT_LIST`\n\n---\n\n### 步骤 4: 需求优先级排序\n\n基于价值和成本对需求排序：\n\n> ? 需求优先级排序\n>\n> **P0（必须有）**：影响核心目标或阻塞其他需求\n> **P1（应该有）**：重要但不紧急\n> **P2（可以有）**：锦上添花\n>\n> 对每个需求确认优先级：\n>\n> 需求\"{需求名称}\"的优先级？\n>\n> A) P0 - 必须有\n> B) P1 - 应该有\n> C) P2 - 可以有\n> D) 推迟到下次迭代\n\n---\n\n### 步骤 5: 资源分配与排期\n\n> ? 资源分配：\n>\n> 可用开发资源：\n> - 前端：[X]人\n> - 后端：[X]人\n> - 设计：[X]人\n> - QA：[X]人\n>\n> **工时估算**：\n>\n> | 需求 | 优先级 | 前端工时 | 后端工时 | 总工时 |\n> |------|--------|---------|---------|--------|\n> | {需求1} | P0 | X天 | X天 | X天 |\n> | {需求2} | P0 | X天 | X天 | X天 |\n> | {需求3} | P1 | X天 | X天 | X天 |\n> | **合计** | | **X天** | **X天** | **X天** |\n>\n> **风险评估**：\n> - 总工时是否在迭代容量内？\n> - 是否存在阻塞依赖？\n> - 是否需要调整范围？\n\n---\n\n### 步骤 6: 输出迭代计划\n\n使用 Write 工具创建 `docs\u002F03-增长迭代\u002F迭代计划-v{版本号}.md`：\n\n```markdown\n# 迭代计划 v{版本号}\n\n## 一、迭代概览\n\n- **迭代编号**：第X次迭代\n- **周期**：YYYY-MM-DD 至 YYYY-MM-DD（2周）\n- **核心目标**：\n  1. {目标1}\n  2. {目标2}\n\n## 二、需求清单\n\n| 优先级 | 需求名称 | 来源 | 前端工时 | 后端工时 | 负责人 |\n|--------|---------|------|---------|---------|--------|\n| P0 | {需求1} | {来源} | X天 | X天 | {负责人} |\n| P0 | {需求2} | {来源} | X天 | X天 | {负责人} |\n| P1 | {需求3} | {来源} | X天 | X天 | {负责人} |\n| P2 | {需求4} | {来源} | X天 | X天 | {负责人} |\n\n## 三、排期计划\n\n### 第1周\n- Day 1-2：{任务}\n- Day 3-4：{任务}\n- Day 5：{任务}\n\n### 第2周\n- Day 6-7：{任务}\n- Day 8-9：{任务}\n- Day 10：交付\u002F测试\u002F上线\n\n## 四、风险与预案\n\n| 风险 | 概率 | 影响 | 预案 |\n|------|------|------|------|\n| {风险} | H\u002FM\u002FL | H\u002FM\u002FL | {预案} |\n\n## 五、验收标准\n\n- 所有P0需求完成开发并测试通过\n- {目标1}达成：{衡量标准}\n- {目标2}达成：{衡量标准}\n\n---\n\n**文档状态**: 迭代计划完成\n**生成时间**: {时间戳}\n**生成工具**: super-pm\n```\n\n---\n\n### 步骤 7: 完成提示\n\n> ✅ 迭代计划完成！\n>\n> ? 已生成：`docs\u002F03-增长迭代\u002F迭代计划-v{版本号}.md`\n>\n> ? 建议下一步：\n>\n> A) 执行 \u002Fpm-risk - 风险管控方案\n> B) 执行 \u002Fpm-agile - 敏捷管理方案\n> C) 迭代开始后执行 \u002Fpm-report 跟踪进度\n\n---\n\n## 兜底机制\n\n### 场景: 需求过多\n\n如果需求总工时超过迭代容量：\n\n> ⚠️ 需求总工时{X天}超过迭代容量{标准容量}\n>\n> 建议：\n> A) 将部分P1\u002FP2需求推迟到下个迭代\n> B) 增加开发资源\n> C) 延长迭代周期\n\n---\n\n## V2 并行架构升级\n\n### 架构概览\n\n\n### 并行Subagent分析\n\n在确认需求清单后，并发派发4个Subagent：\n\n**Subagent 1: 需求分析**\n- 负责：评估需求的业务价值、用户影响面、关联度\n\n**Subagent 2: 工时估算**\n- 负责：基于历史数据估算各需求开发工时、测试工时\n\n**Subagent 3: 依赖分析**\n- 负责：识别需求间的技术依赖、团队依赖、外部依赖\n\n**Subagent 4: 风险分析**\n- 负责：识别排期风险、资源瓶颈、技术风险\n\n### V1 vs V2 对比\n\n| 指标 | V1（顺序分析） | V2（并行分析） | 提升 |\n|------|--------------|--------------|------|\n| **分析时间** | ~5分钟 | ~2分钟 | 2.5x |\n| **主Agent上下文** | ~12,000 tokens | ~3,500 tokens | 节省71% |\n| **分析维度** | 手动逐项估算 | 4维度并行评估 | - |\n| **排期准确性** | 依赖经验 | 多维度交叉验证 | 更准确 |\n\n---\n\n## 注意事项\n\n1. 每个迭代聚焦1-2个核心目标，避免目标过多\n2. P0需求不超过迭代容量的60%\n3. 预留20%缓冲时间应对突发问题\n4. 迭代计划在迭代开始前确认并周知团队\n\n---\n\n## 输出质量对比\n\n**✅ Good 示例**：\n```\n- 有数据引用：「根据 Q4 数据，留存率从 35% 降至 28%」\n- 有验证来源：「数据来源：Google Analytics, 2025-12-01」\n- 有明确建议：「建议将新手引导步骤从 5 步减少至 3 步」\n```\n\n**❌ Bad 示例**：\n```\n- 模糊结论：「数据表明留存率有所下降」\n- 无来源：「根据经验，这个功能很重要」\n- 没有行动建议：「留存是个问题」\n```\n\n---\n\n## 常见误区 \u002F Red Flags — STOP\n\n出现以下情况立即停止并回溯：\n\n| 误区 | 正确做法 |\n|------|---------|\n| 使用\"应该\"、\"大概\"、\"看起来\"做结论 | 必须基于实际数据和验证 |\n| 未运行检查就声称已完成 | 先验证，再陈述 |\n| 因时间紧迫跳过关键步骤 | 没有例外，时间紧更要严格 |\n| \"这次应该没问题\"的想法 | 每次都要重新验证 |\n\n---\n\n## 产出质量检查 \u002F Verification Checklist\n\n- [ ] 前置依赖已满足（输入文档\u002F数据已收集）\n- [ ] 核心步骤已全部执行\n- [ ] 输出文档已生成到 `docs\u002F` 目录\n- [ ] 每个判断都有数据\u002F证据支撑\n- [ ] 已推荐 2-3 个后续 skill\n\n> ⚠️ 任何一项未通过 → 补全后再标记完成。\n\n---\n",{"name":5,"description":37,"allowed-tools":38},"Use when: 需要规划迭代内容、制定迭代排期、明确迭代优先级、从需求到排期的落地\nDo NOT use when: 迭代已由团队自行规划、无需系统化管理\n",[39,40,41,42,27],"Agent","Read","Write","AskUserQuestion","main","c815a5b055b972b9b56fffce0102dbcf9e8ede7d","skills\u002F03-growth-iteration\u002Fpm-iteration",8,"https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM","https:\u002F\u002Fkonglong87.github.io\u002Fanything-ai\u002F","https:\u002F\u002Fgithub.com\u002Fkonglong87","蓬头稚子学垂纶，侧坐莓苔草映身","2026-10-26 15:12:41",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add konglong87\u002FsuperPM --skill pm-iteration",{"tool":58,"command":59},"bunx","bunx skills add konglong87\u002FsuperPM --skill pm-iteration",{"tool":61,"command":62},"pnpm","pnpm dlx skills add konglong87\u002FsuperPM --skill pm-iteration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002F03-growth-iteration\u002Fpm-iteration\u002FSKILL.md",true,[],[67,96,112,133,146,166],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":79,"publishedAt":32},"01M6J07VBJZGTH83K1ST4AFTSX","write-prd","PRD writing workflow — chain demand validation, clarification, prioritization, MVP scoping, and document generation\nUse when: Writing a PRD, BRD, or MRD, or need to produce product requirement documents","https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fwrite-prd\u002FSKILL.md",[73,74],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[80,29,81,82,83,84,85,86,87,88,27,28,30,89,90,91,92,93,94,95],"prd","write prd","writing","workflow","documents","validation","product","produce","prioritization","prd writing","document","generation","chain","mvp","document generation","websearch",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":103,"publishedAt":32},"01M6J07NR1TC4FGKQN2596F8BH","validate-idea","Idea validation workflow — chain demand validation, market research, prioritization, and MVP scoping\nUse when: Validating a new product idea, testing assumptions, or exploring viability","https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fvalidate-idea\u002FSKILL.md",[102],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[104,105,106,107,108,83,85,86,88,27,109,28,29,110,30,111,92,93,95],"validate","idea","validate idea","testing","research","market research","scoping","Market",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":32},"01M6J07HBCCG59V69N29TPAC12","plan-launch","Launch planning workflow — chain risk assessment, cross-team coordination, agile delivery, and release planning\nUse when: Preparing for a product launch, release, or go-live","https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fplan-launch\u002FSKILL.md",[118],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,83,123,124,125,86,126,127,27,128,28,30,129,130,92,131,95,132],"launch","plan","plan launch","risk assessment","assessment","planning","risk","team","coordination","planning workflow","delivery","team coordination","for",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":32},"01M6J07DYRS1S91SY8JCZZH3CS","discover","Product discovery workflow — chain market analysis, competitor research, demand validation, and prioritization\nUse when: Exploring a new product idea, entering a new market, or validating an opportunity","https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fdiscover\u002FSKILL.md",[139],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[135,108,83,85,86,141,142,88,27,28,29,143,30,111,105,144,145,92,95],"analysis","discovery","product discovery","opportunity","market analysis",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":154,"publishedAt":32},"01M6J079BYTWRDH5N8WBH2NEJJ","define-strategy","Product strategy workflow — chain positioning, business model, OKRs, and roadmap\nUse when: Defining product strategy, setting OKRs, planning roadmap, or making strategic decisions","https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fdefine-strategy\u002FSKILL.md",[152,153],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[155,156,157,83,125,86,27,158,159,28,29,160,30,161,162,92,163,164,165,95],"strategy","define","define strategy","model","decisions","business","roadmap","positioning","product strategy","strategic","business model",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":32},"01M6J0752ZRR0R8FWAQHD4KTJ5","analyze-growth","Growth analysis workflow — chain AARRR analysis, data reporting, growth strategy, and iteration planning\nUse when: Analyzing growth metrics, planning growth initiatives, or optimizing product performance","https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fanalyze-growth\u002FSKILL.md",[172],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,175,176,177,83,125,86,178,179,180,141,27,28,29,155,30,25,92,181,95],"analyze","growth","analyze growth","performance","reporting","analyzing","data","growth strategy"]