check-work

What problem does it solve?

This Skill prevents premature completion claims by forcing fresh, concrete verification after code, UI, config, docs, or other project changes. It helps teams replace guesswork and stale assumptions with reproducible evidence, while making any verification gaps and risks explicit.

Core Features & Use Cases

• Evidence-first verification: Runs the right proof for the change type, such as tests, builds, typechecks, curl checks, browser observation, or screenshots.
• False-green prevention: Enforces strong assertion discipline, red-green-revert validation for bug fixes, and spec-to-evidence traceability so passing checks actually prove the intended behavior.
• Cross-phase handoff support: Validates subagent or plugin output, aggregates child evidence manifests, and routes failures back to debugging or implementation when proof does not hold.
• Use cases: Verify a bug fix with regression evidence, confirm a UI change through browser observation, validate API behavior with command output, or document limitations when infrastructure prevents a full check.

Quick Start

After making a change, use check-work to run fresh verification commands, capture the exact proof lines, and produce an evidence block before saying the work is done.