verification-before-completion

Solid

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

AI & Automation 814 stars 53 forks Updated today MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
42
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 1. IDENTIFY - What command proves this claim? 2. RUN - Execute the FULL command (fresh, complete) 3. READ - Full output, check exit code 4. VERIFY - Does output confirm the claim? 5. 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`

Details

Author
a5c-ai
Repository
a5c-ai/babysitter
Created
4 months ago
Last Updated
today
Language
JavaScript
License
MIT

Related Skills