[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J043VECFXETSNEM9SD9KT2":3,"skill-same:01M6J043VECFXETSNEM9SD9KT2":64},{"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":18,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":46,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6J043VECFXETSNEM9SD9KT2","pm-okr",null,"Use when: 需要制定 OKR（目标与关键结果）、拆解公司\u002F产品级目标、做目标对齐与 cascading、设定复盘节奏\nDo NOT use when: 仅需简单待办清单（用 pm-iteration）；目标已由上级完全锁定且无需拆解","konglong87\u002FsuperPM","konglong87","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38234954?v=4","01M6HZZN5EA0572RY1RZAFRKHV","to be a better gopher","01M6HZZN9YN157X26KMMAA147E",91,"MIT","https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002F03-growth-iteration\u002Fpm-okr\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"okr","pm","pm okr","Bash","read","write","use","do","task","iteration","复盘","2026-11-10 10:12:30",false,"---\nname: pm-okr\ndescription: |\n  Use when: 需要制定 OKR（目标与关键结果）、拆解公司\u002F产品级目标、做目标对齐与 cascading、设定复盘节奏\n  Do NOT use when: 仅需简单待办清单（用 pm-iteration）；目标已由上级完全锁定且无需拆解\nallowed-tools:\n  - Task\n  - Read\n  - Write\n  - AskUserQuestion\n  - Bash\n---\n\n## Preamble (run first)\n\n```bash\nif [ -f \"docs\u002F05-产品战略\u002F战略决策建议.md\" ]; then\n  echo \"✅ 战略决策建议 - 已找到（可承接为 O 的来源）\"\nelse\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- 用户说\"定 OKR\"\"目标拆解\"\"关键结果怎么写\"\"目标对齐\"\"季度目标\"\n- 与 `pm-iteration`（迭代待办）区分：OKR 管**方向与可度量结果**，iteration 管**执行排期**。\n\n---\n\n## OKR 基本法（简述）\n\n- **O（Objective）**：方向性、鼓舞人心、定性、不堆指标。\n- **KR（Key Result）**：可度量、有基线值与目标值、可验证、通常 2-4 个\u002F每 O。\n- **对齐（Cascading）**：公司 → 产品\u002F团队 → 个人，下层 KR 支撑上层 O。\n- **信心指数**：制定时标注 50%（有挑战）\u002F 70%（较稳），用于复盘。\n\n---\n\n## 执行流程\n\n### 步骤 1: 明确目标来源（主 agent - 用户交互）\n\n使用 AskUserQuestion 询问：\n\n> ? OKR 范围\n>\n> 这次 OKR 落到哪一层？\n>\n> A) 产品级 OKR（承接公司\u002F战略）\n> B) 团队级 OKR\n> C) 个人\u002F项目级 OKR\n>\n> 目标来源：\n> 1) 沿用战略决策建议\n> 2) 我手动输入业务重点\n> 3) 基于当前增长\u002F数据现状推导\n\n记录 `OKR_LEVEL` 与 `OBJECTIVE_SOURCE`。\n\n---\n\n### 步骤 2: 提炼 Objective（主 agent）\n\n基于来源，提炼 1-3 个 O，要求：\n- 一句话方向、鼓舞人心、不含指标\n- 与战略\u002F业务重点一致\n\n示例：「让产品在目标用户中成为首选」「把增长引擎跑通并可持续」\n\n使用 AskUserQuestion 与用户确认 O 的表述与数量。\n\n---\n\n### 步骤 3: 拆解为 Key Results（主 agent + 可选 subagent）\n\n为每个 O 拆 2-4 个 KR，遵循：**可度量 + 基线 → 目标 + 验证方式**。\n\n可选使用 Agent 工具派发 subagent 对复杂主题生成 KR 草案：\n\n```\nTool: Task\nParameters:\n  subagent_type: \"general-purpose\"\n  description: \"OKR-KR草案\"\n  prompt: |\n    你是目标管理专家。为以下 Objective 拆解 Key Results。\n    O: {O}\n    上下文: {产品现状\u002F数据}\n    要求：每个 O 2-4 个 KR；每个 KR 含 基线值→目标值、度量方式、信心指数(50%\u002F70%)；避免把任务当 KR。\n    输出 Markdown。\n```\n\n主 agent 整合并与用户确认。\n\n---\n\n### 步骤 4: 生成对齐地图与复盘节奏（主 agent）\n\n- **对齐地图**：上层 O 与下层 KR 的支撑关系\n- **复盘节奏**：双周打卡进度、季度复盘评分（0-1.0，0.7 为达标）\n- **风险与依赖**：KR 之间的依赖、资源需求\n\n---\n\n### 步骤 5: 生成 OKR 文档（主 agent）\n\n使用 Write 工具生成 `docs\u002F03-增长迭代\u002FOKR目标管理.md`：\n\n```markdown\n# {产品\u002F团队} OKR（{周期}）\n\n## 一、Objective 与 Key Results\n### O1: {方向性目标}\n- KR1: {基线} → {目标}，度量: {方式}，信心: {50%\u002F70%}\n- KR2: ...\n\n### O2: {方向性目标}\n- KR1: ...\n\n## 二、对齐地图\n| 上层 O | 支撑的下层 KR |\n|-------|--------------|\n| {公司O} | {产品KR1, KR2} |\n\n## 三、度量与基线\n| KR | 当前基线 | 目标 | 数据源 | 负责人 |\n|----|---------|------|-------|-------|\n| {KR} | {值} | {值} | {源} | {人} |\n\n## 四、复盘节奏\n- 双周: 进度打卡\n- 季度: 评分复盘（0-1.0，0.7 达标）\n\n## 五、依赖与风险\n- 依赖: {列表}\n- 风险: {列表}\n\n## 六、下一步建议\n1. \u002Fpm-iteration - 将 KR 转为迭代待办\n2. \u002Fpm-retro - 季度复盘\n3. \u002Fpm-report - 跟踪 KR 进度\n```\n\n---\n\n### 步骤 6: 推荐下一步（主 agent）\n\n> ✅ OKR 已生成：`docs\u002F03-增长迭代\u002FOKR目标管理.md`\n>\n> 建议执行：\n> 1. \u002Fpm-iteration - KR 转迭代待办\n> 2. \u002Fpm-retro - 季度复盘\n> 3. \u002Fpm-report - 进度跟踪\n\n---\n\n## 输出质量对比\n\n**✅ Good 示例**：\n- KR 可度量：「月活 12w → 20w，数据源 GA，信心 50%」\n- O 不含指标：「让新用户首周留存显著提升」\n- 有对齐与复盘\n\n**❌ Bad 示例**：\n- 把任务当 KR：「完成新版上线」\n- O 写成指标堆：「DAU 提升 30%」\n- 无基线与复盘\n\n---\n\n## 常见误区 \u002F Red Flags — STOP\n\n| 误区 | 正确做法 |\n|------|---------|\n| 把任务当 KR | KR 必须可度量、有基线目标 |\n| O 写成指标堆 | O 是方向性定性目标 |\n| KR 无基线 | 必须标注基线→目标 |\n| 不做对齐 | 下层 KR 需支撑上层 O |\n| 无复盘 | 必须定义打分与节奏 |\n\n---\n\n## 产出质量检查 \u002F Verification Checklist\n\n- [ ] 已明确 OKR 层级与目标来源\n- [ ] O 方向性、不含指标、已确认\n- [ ] 每个 O 有 2-4 个可度量 KR（基线→目标）\n- [ ] 已生成对齐地图与复盘节奏\n- [ ] 输出文档已生成到 `docs\u002F03-增长迭代\u002F`\n- [ ] 已推荐 2-3 个后续 skill\n\n> ⚠️ 任何一项未通过 → 补全后再标记完成。\n\n---\n","## Preamble (run first)\n\n```bash\nif [ -f \"docs\u002F05-产品战略\u002F战略决策建议.md\" ]; then\n  echo \"✅ 战略决策建议 - 已找到（可承接为 O 的来源）\"\nelse\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- 用户说\"定 OKR\"\"目标拆解\"\"关键结果怎么写\"\"目标对齐\"\"季度目标\"\n- 与 `pm-iteration`（迭代待办）区分：OKR 管**方向与可度量结果**，iteration 管**执行排期**。\n\n---\n\n## OKR 基本法（简述）\n\n- **O（Objective）**：方向性、鼓舞人心、定性、不堆指标。\n- **KR（Key Result）**：可度量、有基线值与目标值、可验证、通常 2-4 个\u002F每 O。\n- **对齐（Cascading）**：公司 → 产品\u002F团队 → 个人，下层 KR 支撑上层 O。\n- **信心指数**：制定时标注 50%（有挑战）\u002F 70%（较稳），用于复盘。\n\n---\n\n## 执行流程\n\n### 步骤 1: 明确目标来源（主 agent - 用户交互）\n\n使用 AskUserQuestion 询问：\n\n> ? OKR 范围\n>\n> 这次 OKR 落到哪一层？\n>\n> A) 产品级 OKR（承接公司\u002F战略）\n> B) 团队级 OKR\n> C) 个人\u002F项目级 OKR\n>\n> 目标来源：\n> 1) 沿用战略决策建议\n> 2) 我手动输入业务重点\n> 3) 基于当前增长\u002F数据现状推导\n\n记录 `OKR_LEVEL` 与 `OBJECTIVE_SOURCE`。\n\n---\n\n### 步骤 2: 提炼 Objective（主 agent）\n\n基于来源，提炼 1-3 个 O，要求：\n- 一句话方向、鼓舞人心、不含指标\n- 与战略\u002F业务重点一致\n\n示例：「让产品在目标用户中成为首选」「把增长引擎跑通并可持续」\n\n使用 AskUserQuestion 与用户确认 O 的表述与数量。\n\n---\n\n### 步骤 3: 拆解为 Key Results（主 agent + 可选 subagent）\n\n为每个 O 拆 2-4 个 KR，遵循：**可度量 + 基线 → 目标 + 验证方式**。\n\n可选使用 Agent 工具派发 subagent 对复杂主题生成 KR 草案：\n\n```\nTool: Task\nParameters:\n  subagent_type: \"general-purpose\"\n  description: \"OKR-KR草案\"\n  prompt: |\n    你是目标管理专家。为以下 Objective 拆解 Key Results。\n    O: {O}\n    上下文: {产品现状\u002F数据}\n    要求：每个 O 2-4 个 KR；每个 KR 含 基线值→目标值、度量方式、信心指数(50%\u002F70%)；避免把任务当 KR。\n    输出 Markdown。\n```\n\n主 agent 整合并与用户确认。\n\n---\n\n### 步骤 4: 生成对齐地图与复盘节奏（主 agent）\n\n- **对齐地图**：上层 O 与下层 KR 的支撑关系\n- **复盘节奏**：双周打卡进度、季度复盘评分（0-1.0，0.7 为达标）\n- **风险与依赖**：KR 之间的依赖、资源需求\n\n---\n\n### 步骤 5: 生成 OKR 文档（主 agent）\n\n使用 Write 工具生成 `docs\u002F03-增长迭代\u002FOKR目标管理.md`：\n\n```markdown\n# {产品\u002F团队} OKR（{周期}）\n\n## 一、Objective 与 Key Results\n### O1: {方向性目标}\n- KR1: {基线} → {目标}，度量: {方式}，信心: {50%\u002F70%}\n- KR2: ...\n\n### O2: {方向性目标}\n- KR1: ...\n\n## 二、对齐地图\n| 上层 O | 支撑的下层 KR |\n|-------|--------------|\n| {公司O} | {产品KR1, KR2} |\n\n## 三、度量与基线\n| KR | 当前基线 | 目标 | 数据源 | 负责人 |\n|----|---------|------|-------|-------|\n| {KR} | {值} | {值} | {源} | {人} |\n\n## 四、复盘节奏\n- 双周: 进度打卡\n- 季度: 评分复盘（0-1.0，0.7 达标）\n\n## 五、依赖与风险\n- 依赖: {列表}\n- 风险: {列表}\n\n## 六、下一步建议\n1. \u002Fpm-iteration - 将 KR 转为迭代待办\n2. \u002Fpm-retro - 季度复盘\n3. \u002Fpm-report - 跟踪 KR 进度\n```\n\n---\n\n### 步骤 6: 推荐下一步（主 agent）\n\n> ✅ OKR 已生成：`docs\u002F03-增长迭代\u002FOKR目标管理.md`\n>\n> 建议执行：\n> 1. \u002Fpm-iteration - KR 转迭代待办\n> 2. \u002Fpm-retro - 季度复盘\n> 3. \u002Fpm-report - 进度跟踪\n\n---\n\n## 输出质量对比\n\n**✅ Good 示例**：\n- KR 可度量：「月活 12w → 20w，数据源 GA，信心 50%」\n- O 不含指标：「让新用户首周留存显著提升」\n- 有对齐与复盘\n\n**❌ Bad 示例**：\n- 把任务当 KR：「完成新版上线」\n- O 写成指标堆：「DAU 提升 30%」\n- 无基线与复盘\n\n---\n\n## 常见误区 \u002F Red Flags — STOP\n\n| 误区 | 正确做法 |\n|------|---------|\n| 把任务当 KR | KR 必须可度量、有基线目标 |\n| O 写成指标堆 | O 是方向性定性目标 |\n| KR 无基线 | 必须标注基线→目标 |\n| 不做对齐 | 下层 KR 需支撑上层 O |\n| 无复盘 | 必须定义打分与节奏 |\n\n---\n\n## 产出质量检查 \u002F Verification Checklist\n\n- [ ] 已明确 OKR 层级与目标来源\n- [ ] O 方向性、不含指标、已确认\n- [ ] 每个 O 有 2-4 个可度量 KR（基线→目标）\n- [ ] 已生成对齐地图与复盘节奏\n- [ ] 输出文档已生成到 `docs\u002F03-增长迭代\u002F`\n- [ ] 已推荐 2-3 个后续 skill\n\n> ⚠️ 任何一项未通过 → 补全后再标记完成。\n\n---\n",{"name":5,"description":35,"allowed-tools":36},"Use when: 需要制定 OKR（目标与关键结果）、拆解公司\u002F产品级目标、做目标对齐与 cascading、设定复盘节奏\nDo NOT use when: 仅需简单待办清单（用 pm-iteration）；目标已由上级完全锁定且无需拆解\n",[37,38,39,40,22],"Task","Read","Write","AskUserQuestion","main","c815a5b055b972b9b56fffce0102dbcf9e8ede7d","skills\u002F03-growth-iteration\u002Fpm-okr",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add konglong87\u002FsuperPM --skill pm-okr",{"tool":56,"command":57},"bunx","bunx skills add konglong87\u002FsuperPM --skill pm-okr",{"tool":59,"command":60},"pnpm","pnpm dlx skills add konglong87\u002FsuperPM --skill pm-okr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkonglong87\u002FsuperPM\u002Fblob\u002Fmain\u002Fskills\u002F03-growth-iteration\u002Fpm-okr\u002FSKILL.md",true,[],[65,98,114,135,148,168],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":81,"publishedAt":30},"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",[71,76],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[82,24,83,84,85,86,87,88,89,90,22,23,25,91,92,93,94,95,96,97],"prd","write prd","writing","workflow","documents","validation","product","produce","prioritization","prd writing","document","generation","chain","mvp","document generation","websearch",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":30},"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",[104],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[106,107,108,109,110,85,87,88,90,22,111,23,24,112,25,113,94,95,97],"validate","idea","validate idea","testing","research","market research","scoping","Market",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":30},"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",[120],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[122,123,124,85,125,126,127,88,128,129,22,130,23,25,131,132,94,133,97,134],"launch","plan","plan launch","risk assessment","assessment","planning","risk","team","coordination","planning workflow","delivery","team coordination","for",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":30},"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",[141],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[137,110,85,87,88,143,144,90,22,23,24,145,25,113,107,146,147,94,97],"analysis","discovery","product discovery","opportunity","market analysis",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":156,"publishedAt":30},"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",[154,155],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[157,158,159,85,127,88,22,160,161,23,24,162,25,163,164,94,165,166,167,97],"strategy","define","define strategy","model","decisions","business","roadmap","positioning","product strategy","strategic","business model",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":175,"publishedAt":30},"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",[174],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[176,177,178,179,85,127,88,180,181,182,143,22,23,24,157,25,28,94,183,97],"analyze","growth","analyze growth","performance","reporting","analyzing","data","growth strategy"]