메뉴
Use when diagnosing business metric changes or anomalies such as GMV decline, conversion drop, retention loss, churn increase, revenue change, lead decline, or active user fluctuation with a structured root cause analysis plan.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when writing a concise daily report, daily worklog, standup update, shift handoff, or end-of-day summary for data analysis, data development, BI, governance, or operations work.
Use when writing or improving data documentation for warehouse tables, metrics, dashboards, SQL jobs, data products, or handover materials so other people and agents can understand data purpose, grain, fields, logic, ownership, and usage constraints.
Use when analyzing upstream and downstream impact for table changes, metric changes, field deprecation, pipeline migration, dashboard breakage, data governance review, or data asset dependency communication.
Use when planning integration with databases, BI tools, data platforms, APIs, workflow systems, storage services, or third-party tools, including connection requirements, API availability, auth strategy, configuration questions, and validation steps.
Use when planning or writing market research for a specific industry, product category, competitor set, business opportunity, user segment, or go-to-market question with structured evidence and clear assumptions.
Use when reviewing whether a BI dashboard, management dashboard, metric board, or data product page can support business decisions with clear metrics, trustworthy definitions, and actionable drill-down paths.
| name | business-root-cause-analysis |
| description | Use when diagnosing business metric changes or anomalies such as GMV decline, conversion drop, retention loss, churn increase, revenue change, lead decline, or active user fluctuation with a structured root cause analysis plan. |
把“某个业务指标变差了”拆成可验证的归因假设、数据检查路径和行动建议。
这个 Skill 不负责凭空给出唯一原因，而是帮助用户建立一套可执行的排查框架。
使用这个 Skill，当用户需要：
不要使用这个 Skill 处理：
funnel-analysisretention-cohort-analysisdata-analysis-report-writersql-reviewer最少输入：
推荐输入：
优先使用这些模板准备上下文：
如果问题明显属于某个行业，建议补充行业上下文：
上下文不足时，先输出假设树和验证数据需求，不要直接断言原因。
## 归因分析结论
## 异常确认
## 指标拆解
核心指标 = 驱动因子 A * 驱动因子 B * 驱动因子 C
## 假设树
| 假设 | 可能机制 | 需要验证的数据 | 优先级 |
| --- | --- | --- | --- |
## 已知证据
## 下一步验证计划
| 步骤 | 要查什么 | 维度/口径 | 预期判断 |
| --- | --- | --- | --- |
## 可行动建议
## 待确认问题
输出必须：
请用 business-root-cause-analysis 分析这个问题。
背景：SaaS 产品 5 月第 3 周新用户激活率从 42% 降到 31%。
激活口径：注册后 7 天内完成创建工作区、邀请成员、完成一次核心任务中的任意 2 个。
对比基准：过去 4 周均值。
已知变化：
- 5 月 15 日上线了新版引导页
- 付费投放渠道 B 的注册占比从 20% 提升到 38%
- 产品团队反馈没有大面积故障
可用维度：渠道、设备、地区、注册类型、是否进入引导页。
请输出归因假设树、验证路径和下一步建议。