verification-before-completion

To enforce running tests before marking a task complete, this skill applies a checklist-driven protocol that aggregates command outputs and prevents false success claims by requiring evidence before assertions. It automatically blocks completion declarations until verification commands are executed and shown.

Verification before completion is a quality assurance guardrail that ensures evidence from test suites and linters is shown before declaring work done. It prevents false success claims by aggregating command outputs and validating that requested behaviors work without regressions in previously passing tests.

To show test and linter output before claiming a bug is fixed, run the verification workflow to aggregate command outputs and validate the specific behavior requested. This protocol transparently presents evidence of results, ensuring no regressions exist in previously passing tests before marking tasks complete.

Yes, this verification protocol works without additional dependencies. It functions across software development pipelines by applying a checklist-driven protocol to aggregate command outputs, requiring no external components to enforce evidence before assertions and prevent false success claims during quality assurance.

CI-CD guardrails prevent false success claims by enforcing a checklist-driven protocol that requires running tests and linters, then aggregating their outputs. This ensures evidence is transparently shown before any task is marked complete, stopping unverified assertions of completion.

You should use verification commands instead of just marking tasks done to prevent false success claims and ensure no regressions in previously passing tests. Evidence before assertions provides transparent, verifiable proof that requested behaviors work, maintaining pipeline quality assurance.