verify

To verify code changes before claiming completion, run fresh build, test, and lint commands in the current session to inspect outputs and validate exit codes. This enforces evidence-backed confirmation of software delivery outcomes before transitioning to review.

Post-implementation verification is a gated phase that delegates diff review and readability checks to an implementation-verifier agent. It requires fresh command execution and output inspection to prevent premature success claims before transitioning to review or returning to execute-plan.

To prevent false completion claims during software testing, enforce an Iron Law requiring fresh command execution and explicit exit-code failure handling within the same session. This ensures evidence-grounded status reporting before any done status is accepted.

No, the verify skill operates with no dependencies and no components. It delegates build, test, lint, diff review, and readability checks directly to an implementation-verifier agent within your existing software delivery workflow.

When linting or build checks fail during verification, the workflow automatically returns to execute-plan to address the errors. It only transitions to review when all executed commands pass their exit-code validations and produce fresh evidence.

You need to run formal verification checks immediately after your execute-plan run finishes. This produces fresh, command-backed evidence from build, test, and lint outputs required to confirm outcomes within the same session before moving to review.