done-or-not

Why this exists

AI agents routinely announce tasks are complete without verifying anything actually ran. This skill enforces a proof gate: the agent must run the real check (tests, build, typecheck, lint, a curl against the endpoint — whatever demonstrates the claim), record a tamper-evident receipt, and only then may it report done.

The gate records: the command, its exit code, and a SHA-256 of its full output. Freshness is judged by the epoch inside the receipt (not file mtime, which touch could forge). A receipt can only clear one stop — it is consumed on use.

When to use

Use whenever you are about to tell the user that a task, build, test, fix, or verification step is finished. A completion claim requires proof from the gate, not confidence or memory.

How to use

Portable skill command

1. Identify the command that verifies the work. Choose the smallest check that

actually verifies the claim: tests, build, typecheck, lint, a curl against a running endpoint, or another command with meaningful pass/fail behavior.

1. Run the verifying command through the proof gate. This works even when this

skill was installed without the repo-root gate scripts:

   npx agent-done-or-not capture --label check -- <your verifying command>

If the protected repo was initialized with local scripts, these faster local forms are also valid:

   bash done-gate.sh capture --label check -- <your verifying command>
   pwsh -File done-gate.ps1 capture --label check -- <your verifying command>

The gate records the command, its exit code, and a SHA-256 of the output. It exits with the command's own code, so a failing check fails the capture.

1. Only report the work complete after a fresh PASSING receipt exists.

1. If the check fails, fix the problem and capture again. Never report success

on a red check.

Windows (native PowerShell — no bash required)

npx agent-done-or-not capture --label check -- <your verifying command>
pwsh -File done-gate.ps1 capture --label check -- <your verifying command>
# or, on Windows PowerShell 5.1:
powershell -NoProfile -File done-gate.ps1 capture --label check -- <your verifying command>

Hard enforcement

The Stop gate enforces this rule where the harness supports it: it blocks the agent from ending the turn until a fresh passing receipt exists. Do not work around the gate; produce the proof.

Wire the hard stop hook in Claude Code (settings.json):

{
  "hooks": {
    "Stop": [{
      "hooks": [{
        "type": "command",
        "command": "bash \"$CLAUDE_PROJECT_DIR/stop-gate.sh\""
      }]
    }]
  }
}

On Windows, replace with:

"command": "powershell -NoProfile -File \"$env:CLAUDE_PROJECT_DIR\\stop-gate.ps1\""

Installation options

Configuration