superpowers-verification-before-completion

Fresh verification evidence is concrete, reproducible proof of task completion. It requires running a proving command and reading its outputs to ensure no premature task closures or archives proceed without valid checks.

To enforce a verification gate before task completion, apply a multi-step process that identifies the proving command, runs the checks, and reports pass or fail while providing guardrails to ensure evidence remains concrete and auditable.

To reconcile verification results with proposal.md and tasks.md, apply the verification gate before any completion claim, task closure, or archive step, and compare the proving command outputs against the documented project proposals and tasks.

You need to run a verification gate in SPARK-workflow before making any completion claim, task closure, or archive step. This prevents premature closures by enforcing fresh verification evidence prior to finalizing work.

You cannot archive tasks without fresh verification evidence. The process enforces a formal multi-step gate that requires identifying a proving command and reading its outputs to report a clear pass or fail result.