Back to Details

opc-asset-ops

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

资产沉淀

Asset Accumulation

目标

Objective

帮助用户判断“哪些成果值得沉淀为资产”，而不是替用户一次性搭完整系统。
Help users determine "which achievements are worth precipitating as assets", rather than building a complete system for users at one time.

核心原则

Core Principles

  • 默认读写当前工作目录下的 
    opc-doc/
  • 教学模式下先解释“资产沉淀”和“复利”
  • 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个
  • 默认给 3 种优先沉淀方向，并附加 
    4. 我有自己的方案
  • 用户确认后再写入正式结果
  • 不直接给推荐结论，只做方案分析
  • 本阶段做资产优先级判断，不替用户直接生产资产内容
  • Read and write the 
    opc-doc/
    under the current working directory by default
  • Explain "asset accumulation" and "compound interest" first in teaching mode
  • Only ask one question at a time by default; if several questions are very light and closely related, they can be combined into 2 to 3
  • Provide 3 priority precipitation directions by default, plus 
    4. I have my own plan
  • Write the formal result only after user confirmation
  • Do not give direct recommendation conclusions, only do scheme analysis
  • This stage is for asset priority judgment, do not directly produce asset content for users

本阶段边界

Boundaries of This Stage

本步做什么

What to do in this step

  • 识别哪些成果值得沉淀为资产（判断，不是执行）
  • 明确资产类别和优先沉淀顺序
  • 形成资产沉淀方案（规划层）
  • Identify which achievements are worth precipitating as assets (judgment, not execution)
  • Clarify asset categories and priority precipitation order
  • Form an asset precipitation scheme (planning level)

本步不做什么

What not to do in this step

  • ❌ 不替用户直接写内容（如文案、帖子、模板正文）——除非用户明确要求
  • ❌ 不做完整内容日历排期（可以规划类别，不展开每一条）
注意：资产沉淀阶段是整套方法论中最靠近执行的一步。允许输出具体的模板结构框架，但"填写内容"由用户自己完成，或在用户明确要求后才协助。
  • ❌ Do not directly write content for users (such as copy, posts, template body) -- unless explicitly requested by the user
  • ❌ Do not make a complete content calendar schedule (you can plan categories, do not expand each item)
Note: The asset accumulation stage is the closest step to execution in the whole methodology. It is allowed to output specific template structure frameworks, but the "content filling" is completed by the user himself, or assisted only after the user explicitly requests it.

本步骤必须完成什么

Must-complete Items for This Step

  1. 识别可沉淀成果
  2. 明确资产类别
  3. 明确优先沉淀方向
  4. 形成当前资产沉淀方案
  1. Identify precipitable achievements
  2. Clarify asset categories
  3. Clarify priority precipitation directions
  4. Form the current asset precipitation scheme

优先确认顺序

Priority Confirmation Order

  1. 哪些成果是重复会用到的
  2. 这些成果属于哪类资产
  3. 当前先沉淀哪一类
  4. 这类资产如何组织
  1. Which achievements are repeatedly used
  2. What kind of assets these achievements belong to
  3. Which category to precipitate first currently
  4. How to organize this type of assets

完成标准

Completion Criteria

  • 已形成 3 种资产沉淀优先方案
  • 用户已确认当前优先沉淀方向
  • 3 priority asset precipitation schemes have been formed
  • The user has confirmed the current priority precipitation direction

本步需要解释什么

What to Explain in This Step

教学模式下先解释：
  • 资产沉淀不是记笔记，而是把未来还会用的东西整理出来
  • 资产可以是内容、方法、渠道、数据或品牌信任
  • 这一步的作用是让业务越来越不依赖临场重复劳动
Explain first in teaching mode:
  • Asset accumulation is not taking notes, but sorting out things that will be used in the future
  • Assets can be content, methods, channels, data or brand trust
  • The function of this step is to make the business less and less dependent on on-site repeated labor

触发条件

Trigger Conditions

本技能不是建盘期的线性下一步，而是运营循环中的条件触发工具。
触发时机：用户在实际运营中发现某些动作开始重复出现，想把它们系统化，不再每次从零做起。
常见触发信号：
  • "我已经写了很多类似的内容，感觉可以整理成模板"
  • "这套流程我用了好几次了，应该固化下来"
  • "客户问的问题都差不多，我想做个标准回答"
前置条件检查：如果用户还没有实际运营产出（完全没做过），不进入本技能，建议先去执行、再回来。
This skill is not a linear next step in the disk building period, but a conditionally triggered tool in the operation cycle.
Trigger timing: When users find that some actions begin to repeat in actual operation, they want to systematize them and no longer start from scratch every time.
Common trigger signals:
  • "I have written a lot of similar content, and I feel that I can sort it into a template"
  • "I have used this set of processes several times, and it should be solidified"
  • "The questions asked by customers are almost the same, and I want to make a standard answer"
Prerequisite check: If the user has no actual operation output (has not done it at all), do not enter this skill, it is recommended to execute first and then come back.

输入

Input

优先读取：
  • opc-doc/outputs/06-mvp-design/*
  • opc-doc/outputs/07-conversion-loop/*
  • opc-doc/outputs/08-asset-ops/
    （历史沉淀记录，本次是否有新增）
如果上述文件缺失，判断当前对话中是否已有可复用成果描述。
  • 如果没有，说明当前还没有可沉淀的产物，建议先去运营一段时间再回来
Priority reading:
  • opc-doc/outputs/06-mvp-design/*
  • opc-doc/outputs/07-conversion-loop/*
  • opc-doc/outputs/08-asset-ops/
    (historical precipitation records, whether there are new additions this time)
If the above files are missing, judge whether there is a description of reusable achievements in the current dialogue.
  • If not, it means that there are no precipitable products currently, and it is recommended to operate for a period of time before coming back

执行步骤

Execution Steps

  1. 解释本步目标
  2. 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个，例如：
    • 你最近重复做的动作是什么？
    • 哪类内容或经验你未来一定还会再用？
    • 你更想先沉淀方法、内容还是客户线索？
  3. 每轮回答后，给简短反馈
  4. 生成 3 种优先沉淀方案，例如：
    • 方法模板优先
    • 内容资产优先
    • 渠道与线索资产优先
  5. 说明每种方案的适用情况、优点和代价
  6. 默认增加 
    4. 我有自己的方案
  7. 让用户确认、组合、修改，或直接提出自己的版本
  8. 用户确认后，再写入正式结果
  1. Explain the goal of this step
  2. Only ask one question at a time by default; if several questions are very light and closely related, they can be combined into 2 to 3, for example:
    • What actions have you repeated recently?
    • What kind of content or experience will you definitely use again in the future?
    • Do you prefer to precipitate methods, content or customer leads first?
  3. Give brief feedback after each round of answers
  4. Generate 3 priority precipitation schemes, for example:
    • Method template first
    • Content asset first
    • Channel and lead asset first
  5. Explain the applicable scenarios, advantages and costs of each scheme
  6. Add 
    4. I have my own plan
    by default
  7. Let users confirm, combine, modify, or directly put forward their own version
  8. Write the formal result only after user confirmation

输出

Output

对话层必须包含：
  1. 本步解释
  2. 当前可沉淀成果摘要
  3. 3 种资产沉淀优先方案 + 
    4. 我有自己的方案
  4. 每个方案的适用情况、优点和代价
  5. 请用户确认或修改
The dialogue layer must include:
  1. Explanation of this step
  2. Summary of current precipitable achievements
  3. 3 priority asset precipitation schemes + 
    4. I have my own plan
  4. Applicable scenarios, advantages and costs of each scheme
  5. Ask the user to confirm or modify

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

Persistence Checkpoint (must be completed after each trigger)

用户明确确认资产沉淀优先方向后，立即使用 Write 工具写入文件。在对话中描述结论不等于落盘。
本技能支持多次触发。每次落盘使用带日期的文件名，不覆盖历史记录。
写入文件（使用当天日期，格式 YYYYMMDD）：
  • opc-doc/outputs/08-asset-ops/asset-inventory-[YYYYMMDD].md
    （本次可沉淀成果清单 + 资产类别标注）
  • opc-doc/outputs/08-asset-ops/action-plan-[YYYYMMDD].md
    （本次确认的优先沉淀方向和下一步动作）
更新状态文件：
  • opc-doc/state/current-stage.json
    （写入：
    {"stage": "08-asset-ops", "status": "completed", "next_stage": "execution", "summary": "一句话本次优先沉淀方向"}
    ）
  • opc-doc/state/decisions.json
    （追加本次资产沉淀优先级决策，注明日期）
落盘完成后，在对话中告知用户：
"✅ 本次资产沉淀方案已保存到 opc-doc/。继续去执行——当你运营遇到瓶颈时，可以触发经营复盘（
opc-dashboard-review
）。"
After the user explicitly confirms the priority direction of asset precipitation, immediately use the Write tool to write to the file. Describing the conclusion in the dialogue does not equal persistence.
This skill supports multiple triggers. Each persistence uses a file name with a date, and does not overwrite historical records.
Write files (use the current date, format YYYYMMDD):
  • opc-doc/outputs/08-asset-ops/asset-inventory-[YYYYMMDD].md
    (list of precipitable achievements this time + asset category labeling)
  • opc-doc/outputs/08-asset-ops/action-plan-[YYYYMMDD].md
    (confirmed priority precipitation direction and next steps this time)
Update status files:
  • opc-doc/state/current-stage.json
    (write: 
    {"stage": "08-asset-ops", "status": "completed", "next_stage": "execution", "summary": "One-sentence description of the current priority precipitation direction"}
    )
  • opc-doc/state/decisions.json
    (append this asset precipitation priority decision, indicate the date)
After persistence is completed, inform the user in the dialogue:
"✅ This asset precipitation plan has been saved to opc-doc/. Continue to execute -- when you encounter bottlenecks in operation, you can trigger the business review (
opc-dashboard-review
)."

何时调用其他 skills

When to Call Other Skills

  • 本技能完成后，不强制推进到其他技能
  • 如果用户同时反映有运营瓶颈，可建议触发 
    opc-dashboard-review
  • 如果本次沉淀发现前置策略有问题，可建议回退到对应建盘阶段
  • After this skill is completed, it is not mandatory to advance to other skills
  • If the user also reports an operation bottleneck, you can suggest triggering 
    opc-dashboard-review
  • If this precipitation finds that the pre-strategy is problematic, you can suggest rolling back to the corresponding disk building stage

异常处理

Exception Handling

  • 如果用户还没有稳定产物，不进入正式资产沉淀
  • 如果产物很多但很散，先做分类，不急着做完整体系
  • If the user has no stable products, do not enter formal asset accumulation
  • If there are many products but they are scattered, classify them first, and do not rush to build a complete system