dos-verify-done-claimslisted

# Verify done-claims against ground truth, not the agent's word ## Overview When an AI agent says "done", "shipped", or "fixed", that is a **claim**, not a fact — and a claim the agent checks by re-reading its own work is *consistency, not grounding*. This skill replaces that self-report with a verdict from a witness the agent did not author: it shells the **DOS kernel** (`dos verify`, `dos commit-audit`) to confirm the claimed effect from git ancestry and the commit's actual diff. DOS is deterministic — no API key, no LLM, no network. This skill adapts the DOS reference "witness-claim" pattern (`anthony-chaudhary/dos-kernel`) into a host-agnostic screenplay. ## When to Use This Skill - Use when an agent reports a task/phase/feature as **complete** and you want that "done" confirmed from evidence before building on it. - Use right after a commit, to confirm the commit's **message matches its diff** (catch a `fix:` that only touched a README, or a "tests pass" that deleted the assertions). - Use when folding many sub-agents' results — verify each claimed effect instead of trusting the return string. - **Do not** use it to judge whether code is *correct* — that is what the test suite is for. This skill checks did-the-claimed-thing-actually-ship. ## How It Works ### Step 1: Install the kernel (once) ```bash pip install dos-kernel # provides the `dos` CLI; deterministic, no key ``` ### Step 2: Audit the latest commit's claim vs its diff A commit subject