restart-life

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.

盲点圆桌审查层。Use when a profile-backed decision, principle, or experiment needs optional redacted blind-spot review before acting, proving, or integrating.

durable memory 写入门禁。Use when updating PROFILE, profile.json, COMPASS, PRINCIPLES, ROADMAP, BACKLOG, versions, or any long-lived artifact from discovery, proof, or integration.

实验执行层。Use when a decision brief or principle needs to become a 7-day or 30-day prototype, action test, interview plan, skill sprint, or portfolio experiment.

Odyssey 多路径决策层。Use when a usable profile exists and the user is comparing life/career directions, choosing among options, or needs a decision brief before a bounded experiment.

困惑和痛苦调查层。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.

证据评审层。Use when an experiment log exists and the user asks whether a direction is reliable, whether to continue, or whether profile/compass/roadmap can be updated.

Use when a requirement, roadmap item, or bug needs scope clarification, design decisions, and executable task breakdown before coding starts.

Use when a planned or investigated change needs fresh verification evidence, layered gate proof, review truth, and an honest pass fail blocked verdict before entering cc-act.

Use when implementing planned tasks, resuming interrupted work, applying a frozen investigation handoff, or landing review feedback after cc-plan or cc-investigate.

Use when a bug, regression, broken task, or unexpected behavior needs root-cause investigation, reproducible evidence, and a frozen repair handoff before cc-do resumes coding.

Use when defining, resetting, or narrowing project direction, stage order, or backlog priority before a concrete requirement enters the PDCA loop.

Review changed code for reuse, quality, efficiency, and spec drift, then fix any issues found or flag the drift for the user.

Use when you need to initialize capability specs under `devflow/specs/`, create or evolve capability truth sources, generate `change-meta.json`, or validate roadmap/change/spec links before roadmap, planning, or closeout work continues.

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 a planned or investigated change needs fresh verification evidence, layered gate proof, review truth, and an honest pass fail blocked verdict before entering cc-act.

Use when implementing planned tasks, resuming interrupted work, applying a frozen investigation handoff, or landing review feedback after cc-plan or cc-investigate.

Use when a bug, regression, broken task, or unexpected behavior needs root-cause investigation, reproducible evidence, and a frozen repair handoff before cc-do resumes coding.

Use when a requirement, roadmap item, or bug needs scope clarification, design decisions, and executable task breakdown before coding starts.

Use when defining, resetting, or narrowing project direction, stage order, or backlog priority before a concrete requirement enters the PDCA loop.

Review changed code for reuse, quality, efficiency, and spec drift, then fix any issues found or flag the drift for the user.

Use when you need to initialize capability specs under `devflow/specs/`, create or evolve capability truth sources, generate `change-meta.json`, or validate roadmap/change/spec links before roadmap, planning, or closeout work continues.