Asset Accumulation

Objective

Core Principles

• 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)

Must-complete Items for This Step

1. Identify precipitable achievements
2. Clarify asset categories
3. Clarify priority precipitation directions
4. Form the current asset precipitation scheme

Priority Confirmation Order

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 priority asset precipitation schemes have been formed
• The user has confirmed the current priority precipitation direction

What to Explain in This Step

• 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

• "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"

Input

• 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 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. 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. 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)

• 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)

• 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)

"✅ 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

)."

When to Call Other Skills

• 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