Verify Continue Here
Run the full verification loop on a handoff draft, and stop at the first round that passes, or after round 3. It runs on the draft between write-continue-here Steps 3 and 4; that skill alone resolves the location and installs.
When to Use
- The reader may not run
read-continue-here (a human, an unattended loop), the next session is days away, or the single pass left a finding unsettled
Inputs
- Required: The draft, its facts file, and at least one source: the previous edition, or the plan the work follows when there is none
Procedure
Step 1: Run Rounds Until the First Pass, Up to Round 3
From an almanac checkout or plugin install (<almanac> is two directories above the realpath of this skill's directory), run workflows/verify-handoff.mjs as Workflow({ scriptPath: '<almanac>/workflows/verify-handoff.mjs', args: { drafts: [{ key, draft, facts, sources, context }], round: N } }). An npm install ships no workflows/. A copy saved as .claude/workflows/verify-handoff.js runs by name but does not update itself; a .mjs there is not discovered (tests/results/2026-10-14-workflow-loader-probe/RESULT.md). context says what the file is, who consumes it, and which repositories the agents must not read. Coming from write-continue-here Step 3, start at round 2 with its findings file among sources; otherwise start at round 1. After each round, read the gate from the run's return value, not its log:
blocking is 0 and coverage.complete is true: stop. The gate is met, and each further round costs minutes and hundreds of thousands of tokens.
- Otherwise, write the findings to
handoff-findings-rN.md beside the facts file, apply them, add that file to sources, and run round N+1, up to round 3.
Expected: A round that returned blocking 0 and coverage.complete true, and one findings file per earlier round.
On failure: A draft without a facts file is dropped, and without a source the completeness lens is skipped, so coverage stays incomplete: fix the inputs rather than counting the round. Answer a finding you disagree with in the draft (tag the claim, cite the fact), never by deleting it.
Step 2: Record the Passing Round
Set the header to Verified: verify-handoff round N, 0 blocking, coverage complete, with N the round that passed, and return to write-continue-here Step 4 to install.
Expected: The draft names its passing round, so read-continue-here skips the recheck of repaired lines; it still re-confirms the branch, HEAD: and the named PRs and issues.
On failure: If round 3 does not pass, stop and hand the open findings to the user. The user decides whether to keep working, or to install with Verified: verify-handoff round 3, N blocking open, coverage <complete|incomplete>, findings <file>. Any value other than the full-gate one makes read-continue-here re-check the repaired lines.
Validation
Common Pitfalls
- Running past the first pass, or reading the log: the gate is
blocking and coverage.complete in the return value, and a round after it passes costs minutes and tokens to re-open a closed question.
Related Skills
write-continue-here — drafts the handoff, verifies it once, and installs it
read-continue-here — re-confirms every handoff, and re-checks its repaired lines when it stopped short of this gate
1---2name: verify-continue-here3description: >4 Verify a CONTINUE_HERE.md draft to the full gate before it is installed:5 rounds of the verify-handoff workflow against a facts file and at least one6 source, applying findings between rounds and stopping at the first round7 with no blocking finding and complete coverage, or after round 3. Use when the reader may not8 run read-continue-here, the next session is days away, or a single pass left9 a finding unsettled.10license: MIT11allowed-tools: Read Write Bash Grep Glob12metadata:13 source: https://skillmd.com/skills/pjt222/verify-continue-here14 author: Philipp Thoss15 version: "1.0"16 domain: general17 complexity: intermediate18 language: multi19 tags: session, continuity, handoff, verification, workflow20---2122# Verify Continue Here2324Run the full verification loop on a handoff draft, and stop at the first round that passes, or after round 3. It runs on the draft between `write-continue-here` Steps 3 and 4; that skill alone resolves the location and installs.2526## When to Use2728- The reader may not run `read-continue-here` (a human, an unattended loop), the next session is days away, or the single pass left a finding unsettled2930## Inputs3132- **Required**: The draft, its facts file, and at least one source: the previous edition, or the plan the work follows when there is none3334## Procedure3536### Step 1: Run Rounds Until the First Pass, Up to Round 33738From an almanac checkout or plugin install (`<almanac>` is two directories above the `realpath` of this skill's directory), run `workflows/verify-handoff.mjs` as `Workflow({ scriptPath: '<almanac>/workflows/verify-handoff.mjs', args: { drafts: [{ key, draft, facts, sources, context }], round: N } })`. An npm install ships no `workflows/`. A copy saved as `.claude/workflows/verify-handoff.js` runs by name but does not update itself; a `.mjs` there is not discovered (`tests/results/2026-10-14-workflow-loader-probe/RESULT.md`). `context` says what the file is, who consumes it, and which repositories the agents must not read. Coming from `write-continue-here` Step 3, start at round 2 with its findings file among `sources`; otherwise start at round 1. After each round, read the gate from the run's return value, not its log:39401. `blocking` is 0 and `coverage.complete` is true: **stop**. The gate is met, and each further round costs minutes and hundreds of thousands of tokens.412. Otherwise, write the findings to `handoff-findings-rN.md` beside the facts file, apply them, add that file to `sources`, and run round N+1, **up to round 3**.4243**Expected:** A round that returned `blocking` 0 and `coverage.complete` true, and one findings file per earlier round.4445**On failure:** A draft without a facts file is dropped, and without a source the completeness lens is skipped, so coverage stays incomplete: fix the inputs rather than counting the round. Answer a finding you disagree with in the draft (tag the claim, cite the fact), never by deleting it.4647### Step 2: Record the Passing Round4849Set the header to `Verified: verify-handoff round N, 0 blocking, coverage complete`, with N the round that passed, and return to `write-continue-here` Step 4 to install.5051**Expected:** The draft names its passing round, so `read-continue-here` skips the recheck of repaired lines; it still re-confirms the branch, `HEAD:` and the named PRs and issues.5253**On failure:** If round 3 does not pass, stop and hand the open findings to the user. The user decides whether to keep working, or to install with `Verified: verify-handoff round 3, N blocking open, coverage <complete|incomplete>, findings <file>`. Any value other than the full-gate one makes `read-continue-here` re-check the repaired lines.5455## Validation5657- [ ] Every round had the facts file and a source, and each earlier findings file was among the next round's sources58- [ ] The loop stopped at the first round with `blocking` 0 and `coverage.complete` true, or after round 3; `Verified:` names what happened, and `write-continue-here` installed the draft5960## Common Pitfalls6162- **Running past the first pass, or reading the log**: the gate is `blocking` and `coverage.complete` in the return value, and a round after it passes costs minutes and tokens to re-open a closed question.6364## Related Skills6566- `write-continue-here` — drafts the handoff, verifies it once, and installs it67- `read-continue-here` — re-confirms every handoff, and re-checks its repaired lines when it stopped short of this gate