メニュー
Use before any done, fixed, passing, ready, install, or merge claim, and when closing a branch — fresh evidence on this worktree; hooks vary by host, this skill is the checklist.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when writing or designing code: name premise and blast radius, deepen modules at seams, TDD at agreed seams, diagnose before patching, and keep producer→consumer contracts honest.
Use when premises or options must be pressure-tested, a short plan/handoff is needed, or a large plan must be sliced — grill facts locally, ask decisions one at a time.
Use when a project needs a lean `.do-it/handbook/` for stable project truth plus `.do-it/worklog/` for daily or goal notes.
Use only when the user explicitly asks to enable, disable, inspect, report, or persist opt-in local do-it behavioral feedback.
Use when starting any non-trivial repo task: pick Light / Standard / Heavy tier, then self-select meaning skills — not a fixed pipeline.
Use when repo terms or invariants are drifting, or when user/docs/code naming disagrees and a canonical glossary is needed — `.do-it/CONTEXT.md` is the downstream source of truth for names, relationships, and facts.
| name | do-it-verify |
| description | Use before any done, fixed, passing, ready, install, or merge claim, and when closing a branch — fresh evidence on this worktree; hooks vary by host, this skill is the checklist. |
Evidence before status. This skill is the universal checklist; host hooks may block, remind, or be unavailable. Never let a hook substitute for claim-specific proof.
Leading words: fresh evidence, this worktree, claim.
tests pass, bug fixed, review clean, ready to merge, …).NOT_VERIFIED with why).Old CI, worker summaries, and memory are context, not closeout proof. Prefer checks that hit the changed surface.
| Claim | Needs |
|---|---|
tests pass | Fresh test output + exit code |
bug fixed | Original symptom or regression now green |
review clean | No unresolved Blocking/Important on both axes |
ready to merge | Verify + review + intended diff + commit policy |
ready to install | Package/doctor/setup evidence for the changed surface |
runs in production | Production-side evidence (health check, metric, log) — local test output alone is not proof |
When closing a branch, PR, merge, or cleanup:
TODO(@owner)) and surface leftovers in the claim.do-it/runtime/pointer when merged or discardedSubagents do not commit, merge, push, or delete branches by default.
If verification fails: do not soften wording → capture → debug/fix → re-verify. If blocked: NOT_VERIFIED + missing command — never claim done / ready / fixed for that surface.
Claim; branch/worktree; evidence command; VERIFIED / FAILED / NOT_VERIFIED; remains; residual risk; next action.