Enforces rigorous evidence-based verification before marking any coding task, bug fix, or build as complete.
The Strict Task Verification skill eliminates assumptions and 'should work' claims by requiring fresh, empirical evidence for every assertion of success. It mandates the execution of specific verification commands—such as test suites, build scripts, or linter checks—before allowing a task to be closed or a commit to be made. By utilizing a specialized test-runner agent to handle verbose outputs, it prevents context pollution while ensuring that every success criterion is explicitly met and documented with actual command results.
Key Features
01Integration with test-runner agents to prevent context pollution
02Mandatory execution of verification commands before status updates
03Low-freedom enforcement to eliminate human error and assumptions
04Detailed success criteria mapping for task and epic completion
05Evidence-based reporting requirements for all technical claims
0613 GitHub stars
Use Cases
01Ensuring full build success rather than relying on partial linter passes
02Validating bug fixes against original symptoms before committing code
03Verifying complex project epics by checking all sub-task dependencies
