verification-before-completion

To enforce verification before claiming task completion, use a structured approach that requires running verification commands, inspecting outputs, and attaching evidence to your status report before declaring success.

A quality gate prevents unverified claims by mandating explicit steps and evidence collection during development, testing, and release workflows, ensuring outputs are validated before signaling task completion.

Capture command outputs as evidence for testing workflows by executing verification commands through a structured checklist and attaching the resulting outputs directly to your task status report.

Yes, automated verification steps work across development, testing, and release workflows by guiding you to identify verification commands, execute them, and validate results before committing.

The best way to avoid premature success claims is to enforce step-by-step verification, gather evidence from command outputs, and require clear reporting before marking any development task as complete.