القائمة
Use when defining, resetting, or narrowing project direction, stage order, or backlog priority before a concrete requirement enters the PDCA loop.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when verified work must be shipped or handed off with a clear landing path: run simplify and required tests, create or update a PR, prepare a local handoff, close out merged work, sync docs, write release notes, and fold follow-ups back into backlog or roadmap.
咨询式证据化自我理解入口。Use when no usable profile exists, the user says they do not know what they want, or values/talents/interests/constraints need to be refreshed before advice.
重启人生 SKILL 的前门顾问与路由器。Use when the user asks for life/career direction, confusion triage, experiment/proof/integration routing, or starts without a usable ~/.restart-life profile.
周期收尾和 durable memory 写入层。Use when proof-card review needs evidence-backed PROFILE, COMPASS, PRINCIPLES, ROADMAP, BACKLOG, versions, and next-cycle handoff updates.
原则提炼层。Use when investigation has frozen a real pain/failure/conflict case and the user needs a reusable personal principle with case evidence, counterexample, review date, and life-act handoff.
私有人生路线图层。Use when the user asks for the next months/stages, after integration changes direction, or when ROADMAP/BACKLOG need evidence-backed refresh.
| name | cc-roadmap |
| version | 4.3.1 |
| description | Use when defining, resetting, or narrowing project direction, stage order, or backlog priority before a concrete requirement enters the PDCA loop. |
| triggers | ["帮我定路线图","下一阶段先做什么","backlog 太乱了","项目方向散了","roadmap this project","what should we build next","reset the roadmap","prioritize the backlog"] |
| reads | ["PLAYBOOK.md","CHANGELOG.md","assets/ROADMAP_TEMPLATE.md","assets/BACKLOG_TEMPLATE.md","assets/TRACKING_TEMPLATE.json","references/roadmap-dialogue.md"] |
| writes | [{"path":"devflow/ROADMAP.md","durability":"durable","required":true},{"path":"devflow/BACKLOG.md","durability":"durable","required":true},{"path":"devflow/roadmap-tracking.json","durability":"durable","required":false,"when":"roadmap/backlog tracking is maintained through bundled helper scripts"}] |
| entry_gate | ["Read current roadmap, backlog, related capability specs, and surrounding repo context before proposing direction.","Confirm this is a project-direction problem, not a single requirement execution problem.","Do not decompose implementation tasks while the roadmap is still being decided."] |
| exit_criteria | ["The next 1-3 stages are frozen with goal, why now, dependencies, exit signal, kill signal, and non-goals.","The first backlog items can naturally enter cc-plan without extra strategic guessing, including explicit capability links and expected spec delta.","The roadmap shows an explicit RM dependency graph so serial blockers and parallel-ready work are obvious.","The user-approved recommendation is explicit and grounded in current evidence."] |
| reroutes | [{"when":"The user is already discussing one concrete requirement, bug, or execution task.","target":"cc-plan"}] |
| recovery_modes | [{"name":"re-scan-context","when":"The current direction no longer matches repo reality, roadmap files, or the latest user constraint.","action":"Reload the roadmap sources, rewrite Context Snapshot, and recompute the recommended route before continuing."}] |
| tool_budget | {"read_files":8,"search_steps":5,"shell_commands":4} |
[PROTOCOL]: 变更时同步更新
version、CHANGELOG.md、相关模板/脚本引用，必要时写 migration note，然后检查CLAUDE.md
cc-roadmap 只负责一件事：决定项目接下来 1-3 个阶段该推进哪几个 capability。
它先尽可能收集真实上下文，再逼出真实用户、真实痛点、真实紧迫性，最后把这些现实压成一条能落地、能进入 cc-plan 的主线。
PLAYBOOK.mdCHANGELOG.mdassets/ROADMAP_TEMPLATE.mdassets/BACKLOG_TEMPLATE.mdreferences/roadmap-dialogue.md如果用户已经在讨论一个明确 requirement、一个 bug 或一组实现任务，停止留在这里，转去 cc-plan。
如果用户只给了一个模糊问题，先把它归到下面 3 类之一，再继续问：
| 用户信号 | 先读成什么问题 | 默认路线形状 |
|---|---|---|
| “不知道下一步做什么” | 主线不清 | wedge-first |
| “后面几阶段都会重复碰同一底座” | 底座风险 | platform-first |
| “增长/交付/信任卡住了” | 当前最大瓶颈 | rescue-first |
先给一个默认推荐，再解释为什么，不要把用户扔进开放式战略讨论。
devflow/ROADMAP.md, devflow/BACKLOG.md, and the optional devflow/roadmap-tracking.json sidecar used by bundled helpers as the shared roadmap/backlog truth source.cc-plan before the roadmap is approved.cc-plan.devflow/ROADMAP.md / devflow/BACKLOG.md 已存在，先读现状再重写。进入对话前，至少主动收这些上下文：
devflow/ROADMAP.md / devflow/BACKLOG.md 的主线、版本、已停放事项。devflow/specs/INDEX.md 与相关 capability specs 的边界、状态、open gaps。CLAUDE.md、README*、TODOS.md、最近相关 docs / specs / plans。先把这些材料压成一个 Context Snapshot，再开始追问用户。
Context Snapshot、证据、约束、非目标，再讨论阶段。RM 之间的硬依赖压成显式 dependency graph，并标出 parallel-ready wave；不要把“最好按这个顺序做”伪装成 blocker。cc-plan 的事项，每项都要带成功信号、下一决策、Primary Capability、Secondary Capabilities、Expected Spec Delta、Depends On 与 Parallel With。cc-plan。给出 2-3 条路线后，必须明确推荐其中一条。推荐格式至少回答这 4 件事：
推荐话术要像这样：
Recommendation:
wedge-first, because the strongest current evidence is demand uncertainty, not platform pain. We should earn the right to build the base layer after Stage 1 proves pull.
不要只写：
至少要逼清这 5 件事：
同时尽量补齐这些落地上下文：
Context Snapshot，不准给路线推荐。Ready For Req-Plan。RM dependency graph 或 parallel-ready wave，不准宣称事项可以并发推进。cc-plan。写完 devflow/ROADMAP.md / devflow/BACKLOG.md 后，至少完成这 6 个检查：
[NEEDS CONTEXT] 之类的逃避词。Depends On 是否只包含硬阻塞，图里有没有环，parallel-ready wave 是否真的共享同一前置。cc-plan 的对象。devflow/ROADMAP.mddevflow/BACKLOG.mddevflow/roadmap-tracking.json when helper automation needs a shared roadmap/backlog truth source一个高质量 roadmap 交付后，用户应该一眼看懂：
cc-planRM 必须串行，哪些已经可以并行开会话cc-roadmap 自身使用 semver：
patch：措辞、模板字段说明、非契约性澄清minor：新增兼容字段、上下文收集规则、评审规则、输出结构增强major：改变 devflow/ROADMAP.md / devflow/BACKLOG.md 的核心契约、阶段模型或 handoff 预期每次修改都必须：
versionCHANGELOG.mddevflow/ROADMAP.md / devflow/BACKLOG.md 使用方式，在 CHANGELOG.md 写清 migration noteCHANGELOG.mdassets/ROADMAP_TEMPLATE.mdassets/BACKLOG_TEMPLATE.mdassets/TRACKING_TEMPLATE.jsonreferences/roadmap-dialogue.mdscripts/locate-roadmap-item.shscripts/roadmap-tracking.jsscripts/sync-roadmap-progress.shscripts/bump-skill-version.shcc-plandevflow/ROADMAP.md 是方向真相源，devflow/BACKLOG.md 是进入下一轮规划的缓冲区。PLAYBOOK.mdreferences/roadmap-dialogue.md