termination-gatekeeper

Task completion validation requires evidence of static, runtime, e2e, and clean-state checks. The termination-gatekeeper skill enforces this by executing validation scripts and generating task-specific evidence documentation to prove the work is finished.

Evidence-based task completion prevents premature task closure by requiring objective proof of work. You need it in software engineering workflows when thorough validation through static, runtime, e2e, and clean-state checks must be documented before a task is marked done.

Setting up validation scripts for task termination checks requires providing scripts that perform static, runtime, e2e, and clean-state validations. The skill recommends and executes these scripts to verify completion criteria and generate the necessary evidence documentation.

Yes, you need to provide your own scripts for termination checks. The skill is designed to recommend and execute your validation scripts to ensure thorough validation and generate proof of work through task-specific evidence documentation.

The best way to prevent premature task completion is to enforce evidence-based validation using static, runtime, e2e, and clean-state checks. Defining clear completion criteria with objective evidence ensures thorough validation and proof of work before closure.

Task completion validation requires four types of checks: static, runtime, e2e, and clean-state checks. These validation scripts ensure thorough validation and provide objective evidence that all completion criteria have been met before the task is terminated.