Back to Details

opc-dashboard-review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

经营复盘

Business Review

目标

Objective

帮助用户判断当前最真实的瓶颈是什么，并确认下一周期应该优先解决哪个问题。
Help users identify the most realistic current bottleneck and confirm which problem should be prioritized for resolution in the next cycle.

核心原则

Core Principles

  • 默认读写当前工作目录下的 
    opc-doc/
  • 教学模式下先解释复盘不是流水账，而是找瓶颈
  • 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个
  • 默认给 3 个瓶颈假设或优先重点，并附加 
    4. 我有自己的方案
  • 用户确认后再写入正式结果
  • 不直接给推荐结论，只做方案分析
  • Read and write the 
    opc-doc/
    directory under the current working directory by default
  • In teaching mode, first explain that a review is not a running account, but a process to identify bottlenecks
  • Ask only one question at a time by default; if several questions are very lightweight and closely related to each other, they can be combined into 2 to 3 questions
  • Provide 3 bottleneck hypotheses or priority focuses by default, with an additional option 
    4. I have my own solution
  • Write formal results only after user confirmation
  • Do not give direct recommendation conclusions, only conduct solution analysis

本步骤必须完成什么

Mandatory Completion Items for This Step

  1. 当前经营状态摘要
  2. 主要瓶颈识别
  3. 下周期优先重点确认
  1. Current operating status summary
  2. Major bottleneck identification
  3. Confirmation of priority focuses for the next cycle

优先确认顺序

Priority Confirmation Order

  1. 最近最卡的地方
  2. 最可能的瓶颈类型
  3. 下一周期优先修正哪一点
  1. The most stuck part recently
  2. The most possible bottleneck type
  3. Which point to prioritize for correction in the next cycle

完成标准

Completion Criteria

  • 已形成 3 个瓶颈假设或优先重点
  • 用户已确认当前最真实的瓶颈
  • 3 bottleneck hypotheses or priority focuses have been formed
  • The user has confirmed the most realistic current bottleneck

本步需要解释什么

Content to Explain in This Step

教学模式下先解释：
  • 复盘看的是需求、转化、资产和风险
  • 目标不是证明自己努力了，而是找出最值得修正的一点
  • 这一步会决定下一周期的唯一重点
Explain first in teaching mode:
  • A review focuses on demand, conversion, assets and risks
  • The goal is not to prove you have worked hard, but to find the most worthwhile point to correct
  • This step will determine the sole focus of the next cycle

触发条件

Trigger Conditions

本技能不是建盘期的线性下一步，而是运营循环中的周期性工具。
触发时机（满足其一即可）：
  • 运营一段时间后感到卡顿，不知道问题出在哪
  • 想做一次有结构的回顾，而不是凭感觉继续做
  • 转化、留存或成交出现明显下滑
  • 用户自主选择做一次复盘
前置条件检查：如果用户刚完成建盘期还没开始执行，不进入本技能——复盘需要有实际运营数据，哪怕是轻量的。
This skill is not a linear next step in the foundation building period, but a periodic tool in the operation cycle.
Trigger timing (meet any of the following):
  • You feel stuck after operating for a period of time and don't know where the problem lies
  • You want to conduct a structured review instead of continuing to operate based on intuition
  • There is a significant decline in conversion, retention or transaction volume
  • The user voluntarily chooses to conduct a review
Pre-condition Check: If the user has just completed the foundation building period and has not started execution, do not enter this skill -- a review requires actual operation data, even if it is lightweight.

输入

Input

优先读取：
  • opc-doc/outputs/**
    （所有建盘期产物，用于对照）
  • opc-doc/reviews/dashboard.json
    （历史复盘记录，如果存在）
  • opc-doc/outputs/09-dashboard-review/
    （本周期前几次复盘，如果有）
如果 
opc-doc/
不存在或数据不足，先看当前对话中是否已有足够经营信息。
  • 如果用户完全没有运营过，不做假复盘，提醒先去执行再来复盘
Priority reading:
  • opc-doc/outputs/**
    (all foundation building period products, for comparison)
  • opc-doc/reviews/dashboard.json
    (historical review records, if available)
  • opc-doc/outputs/09-dashboard-review/
    (previous reviews in this cycle, if available)
If 
opc-doc/
does not exist or has insufficient data, first check whether there is enough operation information in the current conversation.
  • If the user has no operation experience at all, do not conduct a fake review, remind the user to execute first before doing a review

执行步骤

Execution Steps

  1. 解释本步目标
  2. 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个，例如：
    • 你最近最卡的一步是什么？
    • 你是没人来、没人买，还是做完不复用？
  3. 每轮回答后，给简短反馈
  4. 生成 3 个瓶颈判断，例如：
    • 需求验证不足
    • 转化路径不顺
    • 资产沉淀太弱
  5. 说明每个判断的适用情况、依据和代价
  6. 默认增加 
    4. 我有自己的方案
  7. 让用户确认、组合、修改，或直接提出自己的版本
  8. 用户确认后，再写入正式复盘结果
  1. Explain the goal of this step
  2. Ask only one question at a time by default; if several questions are very lightweight and closely related to each other, they can be combined into 2 to 3 questions, for example:
    • What is the most stuck step for you recently?
    • Are you facing no traffic, no purchases, or no reuse of completed work?
  3. Give brief feedback after each round of answers
  4. Generate 3 bottleneck judgments, for example:
    • Insufficient demand verification
    • Unsmooth conversion path
    • Too weak asset accumulation
  5. Explain the applicable scenarios, basis and cost of each judgment
  6. Add the option 
    4. I have my own solution
    by default
  7. Let the user confirm, combine, modify, or directly propose their own version
  8. Write the formal review result only after user confirmation

输出

Output

对话层必须包含：
  1. 本步解释
  2. 当前经营状态摘要
  3. 3 个瓶颈判断 + 
    4. 我有自己的方案
  4. 每个判断的适用情况、依据和代价
  5. 请用户确认或修改
The conversation layer must include:
  1. Explanation of this step
  2. Current operating status summary
  3. 3 bottleneck judgments + 
    4. I have my own solution
  4. Applicable scenarios, basis and cost of each judgment
  5. Request for user confirmation or modification

落盘检查点（每次触发后必须完成）

Persistence Checkpoint (must be completed after each trigger)

用户明确确认本周期核心瓶颈和下一重点后，立即使用 Write 工具写入文件。在对话中描述结论不等于落盘。
本技能支持多次触发。每次落盘使用带日期的文件名，不覆盖历史记录。
写入文件（使用当天日期，格式 YYYYMMDD）：
  • opc-doc/outputs/09-dashboard-review/review-[YYYYMMDD].md
    （经营状态摘要 + 瓶颈判断 + 下周期唯一优先重点）
  • opc-doc/reviews/dashboard.json
    （结构化复盘数据，追加写入，保留历史，不覆盖）
更新状态文件：
  • opc-doc/state/current-stage.json
    （写入：
    {"stage": "09-dashboard-review", "status": "completed", "next_stage": "execution-or-回退阶段", "summary": "一句话核心瓶颈和下一重点"}
    ）
  • opc-doc/state/decisions.json
    （追加下周期唯一优先重点，注明日期）
落盘完成后，在对话中告知用户：
"✅ 本次复盘已保存。根据复盘结论：[简短说明下一步是继续执行、回退某阶段，还是触发资产沉淀]"
After the user explicitly confirms the core bottleneck of this cycle and the next focus, use the Write tool to write to the file immediately. Describing the conclusion in the conversation does not equal persistence.
This skill supports multiple triggers. Use a date-stamped file name for each persistence, do not overwrite historical records.
Write to files (use the current date in YYYYMMDD format):
  • opc-doc/outputs/09-dashboard-review/review-[YYYYMMDD].md
    (operating status summary + bottleneck judgment + sole priority focus for the next cycle)
  • opc-doc/reviews/dashboard.json
    (structured review data, append write, retain history, no overwriting)
Update status files:
  • opc-doc/state/current-stage.json
    (write: 
    {"stage": "09-dashboard-review", "status": "completed", "next_stage": "execution-or-回退阶段", "summary": "一句话核心瓶颈和下一重点"}
    )
  • opc-doc/state/decisions.json
    (append the sole priority focus of the next cycle, indicate the date)
After persistence is completed, inform the user in the conversation:
"✅ This review has been saved. According to the review conclusion: [briefly explain whether the next step is to continue execution, roll back to a certain stage, or trigger asset accumulation]"

何时调用其他 skills

When to Call Other Skills

  • 如果复盘发现前置阶段缺口，明确建议回退到对应 skill
  • 不要在没有依据时让用户重复整个流程
  • If the review finds gaps in the pre-stage, clearly recommend rolling back to the corresponding skill
  • Do not ask the user to repeat the entire process without basis

异常处理

Exception Handling

  • 如果数据不完整，只做轻量定性复盘，不装作有完整结论
  • 不要同时给多个下一步重点，保持单一优先级
  • If the data is incomplete, only conduct a lightweight qualitative review, do not pretend to have a complete conclusion
  • Do not give multiple next-step focuses at the same time, maintain a single priority