agentleFS
Dimon94Dimon94/restart-life/.agents/skills/life-roadmap/SKILL.md

life-roadmap

Skill1 starsChanged 7 months agoMITView on GitHub

私有人生路线图层。Use when the user asks for the next months/stages, after integration changes direction, or when ROADMAP/BACKLOG need evidence-backed refresh.

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
  1. Very specific:

    Read references/guide.md for 思想来源/source lineage, private roadmap/backlog chain, and scope boundaries.

    line 129
  2. Very specific:

    Use assets/roadmap-stage.template.md as the roadmap stage and backlog item template material.

    line 130
  3. Very specific:

    Run node scripts/check-handoff.mjs --runtime ~/.restart-life before private roadmap refresh.

    line 131

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

life-roadmap

你负责维护用户私有的 ~/.restart-life/ROADMAP.md 和 BACKLOG.md,不是仓库里的 devflow/ROADMAP.md。路线图必须来自 profile、proof、principles 和 constraints,而不是一时兴奋。

铁律

  • Roadmap 是证据和阶段选择,不是愿望清单。
  • repo roadmap 记录产品开发;private roadmap 记录用户人生行动,二者不能混写。
  • 没有 profile 或 proof 支撑时,只能提出 discovery/experiment 下一步,不能刷新长期路线。

入口检查

  1. 读取 profile.json、COMPASS.md、PRINCIPLES.md。
  2. 读取 ROADMAP.md 和 BACKLOG.md 当前版本。
  3. 若来自 cycle closeout,读取 integration.md 和 proof-card.json。
  4. 如果没有 usable profile,reroute 到 life-discover。

Roadmap Stage

每个阶段必须包含:

  • goal
  • why now
  • evidence
  • dependencies
  • exit signal
  • kill signal
  • non-goals
  • likely next cycle

Backlog Item

每个 backlog item 必须包含:

  • item
  • source evidence
  • priority
  • depends on
  • next action
  • stop condition

输出格式

无论是 proof-backed refresh、轻量草案还是证据不足的拒绝写入,都使用同一个输出骨架,避免为不同情况增加分支:

# Private Roadmap Update

## Read Gate
- profile: found|missing|not-usable
- proof: found|missing|not-required
- source: integration|lightweight-draft|blocked

## Roadmap Stages
| Stage | Goal | Evidence | Exit Signal | Kill Signal | Next Cycle |
| --- | --- | --- | --- | --- | --- |

## Backlog
| Item | Source Evidence | Priority | Depends On | Next Action | Stop Condition |
| --- | --- | --- | --- | --- | --- |

## Decision
- action: write-private-roadmap|draft-only|reroute
- next_route: life-discover|life-choose|life-act|life-investigate|memory-write-gate|stop
- reason: ...

执行流程

  1. 判断当前是否是 roadmap refresh,还是只需要选择下一 cycle。
  2. 对照 profile/compass/principles,保留 1-3 个阶段;超过 3 个就是失焦。
  3. 把 backlog 压到可执行粒度,优先下一个 RL cycle。
  4. 写 exit signal 和 kill signal,防止路线图变成长期拖延。
  5. 输出下一入口:life-discover、life-choose、life-act、life-investigate 或 stop。

质量门

私有 ROADMAP.md 和 BACKLOG.md 刷新前运行:

npm run validate:life-cycle -- --runtime ~/.restart-life --cycle <cycle> --mode <mode>

如果不是来自具体 cycle,而是用户要求轻量规划,只能输出草案和证据缺口,不能写 durable roadmap。

禁止事项

  • 不把 repo devflow/ROADMAP.md 当成用户人生路线图。
  • 不创建十几个并行人生阶段。
  • 不把没有 proof 的想法提升为 roadmap stage。
  • 不删除旧阶段,除非 integration 明确说明 evidence 已反驳或替换。

Bundled Resources

  • Read references/guide.md for 思想来源/source lineage, private roadmap/backlog chain, and scope boundaries.
  • Use assets/roadmap-stage.template.md as the roadmap stage and backlog item template material.
  • Run node scripts/check-handoff.mjs --runtime ~/.restart-life before private roadmap refresh.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.