Dimon94

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.

Review and land one authenticated provider-native review item. Use when current-head review, landing, closeout, and remote-main parity are in scope.

Submit a named verified source for remote review. Use when explicit authority covers push and one review item, but not approval or landing.

Simplify verified changes before remote submission. Use for deletion-first, YAGNI, native-library, structural, and test-seam review.

Create narrow auditable local commits. Use when verified Dverity work must be staged and committed without absorbing unrelated changes.

Resolve an in-progress merge or rebase conflict from proven product intent. Use only when Git reports an actual conflict.

Find and reuse the nearest correct mechanism before adding another. Use when a Dverity change would add reusable code, policy, or workflow meaning.

Diagnose and repair confirmed defects to Verified Local. Use for evidence-first bug repair; remote submission requires separate explicit authority.

Gather evidence for Dverity repair decisions. Use when a repair hypothesis or boundary needs primary-source proof before mutation.

Diagnose and repair a confirmed defect to a Verified Local evidence packet. Use when a bug, defect, or regression needs evidence-first repair, or when another Dverity skill reroutes a confirmed defect. Remote promotion requires separate explicit authority.

Review and land one authenticated provider-native review item. Use when current-head review, landing, closeout, and remote-main parity are in scope.

Submit a named verified source for remote review. Use when explicit authority covers push and one review item, but not approval or landing.