Babysitter verification-before-completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Evidence before assertions.

install

source · Clone the upstream repo

git clone https://github.com/a5c-ai/babysitter

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/superpowers/skills/verification-before-completion" ~/.claude/skills/a5c-ai-babysitter-verification-before-completion-687d9c && rm -rf "$T"

manifest: library/methodologies/superpowers/skills/verification-before-completion/SKILL.md

Verification Before Completion

Overview

Claiming work is complete without verification is dishonesty, not efficiency.

Core principle: Evidence before claims, always.

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

Gate Function

IDENTIFY - What command proves this claim?
RUN - Execute the FULL command (fresh, complete)
READ - Full output, check exit code
VERIFY - Does output confirm the claim?
ONLY THEN - Make the claim

Red Flags

Using "should", "probably", "seems to"
Expressing satisfaction before verification
Trusting agent success reports without independent verification

Agents Used

Process agents defined in
```
verification-before-completion.js
```

Tool Use

Invoke via babysitter process:

methodologies/superpowers/verification-before-completion