staff-verification-before-completion

To prevent false completion claims before a pull request, this Skill mandates running the exact verification command, reading the full output, and confirming a passing result before permitting any success language. It ensures evidence precedes statements that work is done.

Evidence-first verification for software builds is a workflow mechanism that requires a current command run and full output review before any status claim is made. It distinguishes actual passing builds from assumptions or stale results by grounding success language in fresh evidence.

Yes, you can use this verification discipline for agent handoffs and commits. It applies to any scenario where evidence must precede success language, ensuring that fresh verification confirms the result before work is marked complete or handed off to another agent.

Stale test output leads to premature completion claims because it allows assumptions or partial checks to substitute for actual passing results. This Skill mitigates the issue by requiring a fresh command run and full output confirmation before any statement that work is done.

No, this verification gate does not require specific testing frameworks or dependencies. It enforces a process discipline that applies to any testing, builds, or quality assurance commands, requiring you to run the exact proving command and confirm the output before claiming completion.