life-investigate
Skill1 starsChanged 7 months agoMITView on GitHub
困惑和痛苦调查层。Use when the user is stuck, in pain, repeating failure patterns, facing high-stakes conflict, or asking for advice before the real problem is frozen.
In this repository18 other files it gives its agents.
- life-actSkill
- life-chooseSkill
- life-discoverSkill
- life-integrateSkill
- life-principleSkill
- life-proveSkill
- life-roadmapSkill
- life-roundtableSkill
- memory-write-gateSkill
- restart-lifeSkill
- cc-actSkill
- cc-checkSkill
- cc-doSkill
- cc-investigateSkill
- cc-planSkill
- cc-roadmapSkill
- cc-simplifySkill
- cc-spec-initSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 128
Read references/guide.md for 思想来源/source lineage, investigation chain, problem classes, and reroute rules.
- Very specific: line 129
Use assets/investigation.template.md as the investigation template material.
- Very specific: line 130
Run node scripts/check-handoff.mjs --runtime ~/.restart-life --cycle <cycle> before handing off to life-principle.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
life-investigate
你负责在建议出现之前冻结真实问题。痛苦、反复失败、逃避、冲突和高风险决策,先进入 investigation,不直接给答案。
铁律
NO ADVICE BEFORE THE PROBLEM IS FROZEN痛苦不是噪音,是证据入口。但不能把痛苦直接翻译成原则或人生方向。
入口检查
- 读取
profile.json;没有 usable profile 时,只能收集当前痛点并 reroute 到life-discover补 profile。 - 读取
intake.md或用户当前叙述,保留原话。 - 查看
pain-reflection-log.jsonl是否有类似模式。 - 若用户已经有清楚方向选择且没有痛点,reroute 到
life-choose。
问题分类
把当前问题归入一个主类,不要多头并行:
| 类型 | 判断信号 | 下一步 |
| self-understanding gap | 不知道自己重视什么、擅长什么、约束是什么 | life-discover |
| decision conflict | 多个方向都可行但无法选择 | life-choose |
| execution friction | 知道要做但反复不做 | life-act 或 life-principle |
| environment mismatch | 人/组织/节奏持续消耗 | life-principle |
| skill gap | 缺能力、资源、信息 | life-act |
| avoidance pattern | 快选择时退缩、拖延、转移 | life-principle |
Investigation 输出
写入 ~/.restart-life/cycles/<cycle>/investigation.md:
# Investigation
## Symptom
用户看到的表象。
## Trigger
触发时机、场景、人物、压力。
## Pattern
是否重复发生,频率和历史。
## Failed Attempts
已经试过什么,为什么没解决。
## Reality Constraints
钱、时间、关系、健康、身份、机会窗口。
## Problem Class
self-understanding gap / decision conflict / execution friction / environment mismatch / skill gap / avoidance pattern
## Frozen Problem
一句话定义现在真正要解决的问题。
## Reroute
下一 skill 和理由。如果是显著痛苦或失败,同时追加 pain-reflection-log.jsonl 候选记录,但不要直接生成原则。
执行流程
- 复述 symptom,不急着解释。
- 追问触发条件和重复模式;一次只问一个关键问题。
- 分离事实、解释、情绪、假设。
- 写出 frozen problem;如果无法冻结,明确缺哪条证据。
- 根据 problem class reroute。
质量门
交给 life-principle 或 life-act 前运行:
npm run validate:life-cycle -- --runtime ~/.restart-life --cycle <cycle> --mode ICAP禁止事项
- 不在 frozen problem 之前给建议。
- 不把“我懒/我不行”当根因;这通常是未冻结问题的标签。
- 不把痛苦直接升格为人生原则。
- 不替用户做心理诊断或医疗判断;高风险安全问题要求寻求专业帮助。
flows in skill-manifest.json declares this skill's ICAP next routes.
Bundled Resources
- Read
references/guide.mdfor 思想来源/source lineage, investigation chain, problem classes, and reroute rules. - Use
assets/investigation.template.mdas the investigation template material. - Run
node scripts/check-handoff.mjs --runtime ~/.restart-life --cycle <cycle>before handing off tolife-principle.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

