opc-resource-audit

Resource inventory

Objective

Confirm all resources the founder currently possesses, category by category, and clarify the details of each to form a resource list with substance and depth.

The only output of this step is: the resource list.

Do not analyze direction, do not judge what it suits, do not assess preferences or risk tolerance—those are the work of subsequent skills.

Core principles

By default, read and write the opc-doc/
Ask only one question at a time; if several questions are all light and closely related, 2 to 3 may be combined
Each round, give immediate feedback first, then move to the next question
Write formal results only after user confirmation
Do not analyze direction, do not evaluate which resource has more potential, do not discuss preferences or risk—only probe resources

Boundaries of this stage

Only do these

By the 8 resource categories, confirm one by one which resources the user has
For each confirmed resource, dig deep into the specifics (distribution, available methods, costs)
Output a complete resource list confirmed by the user

Do not do these (they belong to subsequent skills)

❌ Do not judge "which resource is most valuable" (belongs to opc-niche-positioning)
❌ Do not assess preferences or risk tolerance (belongs to the subsequent decision stage)
❌ Do not give business advice or product direction

Boundary-crossing detection: if analytical topics such as "you are suited to do" "this direction is better" "you should do this first" appear in the conversation, record them first, then say:

"This judgment is valuable, but it belongs to the work of a subsequent stage. Let's first get the resource baseline clear, so the later analysis has a basis."

Resource categories

8 categories in total, see references/resource-categories.md：

Experience resources: industry experience, professional experience, things done and proven to work
People resources: which type of people you understand best, whom you have dealt with long-term
Capability resources: professional capability, expression, aesthetics, judgment, learning ability
Relationship resources: customer relationships, partners, acquaintance trust networks
Channel resources: social accounts, communities, private domain, distribution entry points
Asset resources: cases, materials, templates, toolchains, portfolios
Constraint resources: time limits, energy limits, cash flow pressure, family constraints
Hard boundaries: things that absolutely must not be touched, situations that must be stopped (record facts, do not analyze reasons)

Opening statement rules

The user's opening self-introduction does not mean the resource inventory is complete.

No matter how much background information the opening statement provides, it is only context and cannot replace formal confirmation of each category. The opening statement usually covers only experience resources and part of capability resources; the remaining 6 categories are almost certainly blank.

Identify the information already present in the opening statement, do a brief confirmation, then continue advancing through the categories not yet covered.

Execution process (two stages)

Stage one: rough scan—confirm which resources exist

Objective: quickly go through the 8 categories and confirm what the user has in each category.

Rules：

Use 1 to 2 questions per category, and immediately move to the next after getting a basic answer
Don't linger, don't dig deep, don't evaluate, just record
If the user proactively expands on a certain item, briefly note it down and politely pull them back: "Okay, noted. Let's go through the other sections first."

Advancement order(prioritize those not covered in the opening):

Channel resources: Do you have any social accounts or private domains? Roughly how many followers / friends?
Relationship resources: Among the people you can directly contact right now, which type is most likely to support you?
Asset resources: Do you have anything ready to use on hand—case images, templates, materials, tools?
Constraint resources: What is the hardest constraint right now—time, cash flow, or something else?
Hard boundaries: Is there anything you absolutely cannot touch? (If yes, note it; if no, skip)
People resources: Among the people you've dealt with, which type do you understand best?
Ability resources: Which of your professional abilities do you consider yourself good at?
Experience resources: Is there any experience that others would find hard to replicate?

After the rough scan is complete, move to the second stage.

Second stage: Deep dive—get clear on the details of each resource

Goal: For each resource confirmed in the first stage, dig into the specific situation one by one.

For each resource, clarify the following dimensions(choose flexibly based on resource type):

What exactly it is: scale, quantity, quality, current status
Where it is distributed: field, group, platform, occasion
What can be used: the parts that can be directly used now
How to use it: in what way it can be mobilized or converted
What the cost is: what must be paid to use this resource (time, relationship wear, money, reciprocity, etc.)

Example：

User says they have connection resources →

Which industries or circles are these connections mainly in?

Among them, which type is closest to you and most likely to help you?

If you ask them for help, in what way is it usually—introducing clients, forwarding, endorsing, or something else?

What do you think the cost is of using these relationships?

You don't need to ask all dimensions for every resource; supplement flexibly based on the information already in the conversation. The key is: when each resource is finished, there is enough detail to write into the list.

After the deep dive is complete, move to list confirmation.

List confirmation

Organize all information into a complete resource list and present it to the user for confirmation:

这是我目前整理的资源情况，请逐项看一下，有没有遗漏或需要修正？

---
资源清单 · 初稿

1. 经验资源
   - [从对话中提取的具体内容]

2. 人群资源
   - [从对话中提取的具体内容]

3. 能力资源
   - [从对话中提取的具体内容]

4. 关系资源
   - [规模 / 分布 / 可用方式 / 代价]

5. 渠道资源
   - [平台 / 规模 / 活跃度]

6. 资产资源
   - [具体内容及可用程度]

7. 约束资源
   - [时间、现金流、家庭等具体情况]

8. 硬性边界
   - [记录，不分析]
---

有没有哪个类别还有重要内容没提到？或者有哪条需要修正？

User confirms (or confirms after supplementing/correcting) → save to file.

Completion standard

All 8 resource categories have been covered
Each confirmed resource has enough detail (not just a label, but a description with content)
The user confirms the list has no omissions

Stop once complete: After the list is confirmed, this skill task ends. Do not extend into direction analysis or suggestions.

Save checkpoint (the stage must be completed, cannot be skipped)

After the user confirms the list,immediatelyuse the Write tool to create the following file:

Write to file:

opc-doc/outputs/01-resource-audit/inventory.md(the complete resource list confirmed by the user, 8 categories, including details)
opc-doc/outputs/01-resource-audit/scorecard.json(Structured resource entry, for subsequent skills to read)

Update status file:

opc-doc/state/current-stage.json(Write to:{"stage": "01-resource-audit", "status": "completed", "next_stage": "02-niche-positioning", "summary": "一句话描述最关键的资源特征"}）

After the write to disk is complete, inform the user in the conversation:

"✅ The resource list has been saved to opc-doc/. The next conversation can continue from niche positioning."

Only after the write to disk is complete may you prompt to proceed to opc-niche-positioning。

When to call other skills

Only after the write to disk is complete may you prompt to proceed to opc-niche-positioning。

Input

Read first:

opc-doc/inputs/founder-profile.md
opc-doc/inputs/raw-ideas.md

If opc-doc/ does not exist, start directly based on the conversation, and create directories as needed when writing to disk.

Exception handling

If the user has no resources at all in a certain category, truthfully record "none available" and continue advancing without pausing
If the user's answer is too broad, ask one specific question rather than asking a series of questions in succession
If the user explicitly requests an extension after round 9, you may continue, but state that this is an extension at the user's request