Verification before completion
Skill krzemienski/deepest-plan-plugin/skills/verification-before-completion
Pre-completion checklist for phase transitions and claims. Requires running verification commands and citing evidence before asserting work is "complete" or "ready to ship". Cited inside every phase_gate regression_check in deepest-plan output.From its SKILL.md
npx -y skills add krzemienski/deepest-plan-plugin --skill verification-before-completionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.2 KB, as published. Nobody here has run it
Verification Before Completion
Scope
Forces an explicit verification pass before any completion claim. Complements gate-validation-discipline (which governs per-gate verdicts) by gating the phase-transition or final "done" moment.
When to Run
- Before claiming a phase is complete
- Before transitioning to the next phase (precondition for phase_gate)
- Before marking any task "shipped"
- Before creating a PR or merging
- Before sending a "ready for review" message
The Gate Function
1. IDENTIFY what you are about to claim
2. RUN the verification command(s) that would falsify the claim
3. READ the output — not just the exit code
4. VERIFY output matches every asserted property
5. Only then CLAIM completion — with evidence cited
Claim-Type Verification Matrix
| If you are about to claim… | Verification MUST include |
|---|---|
| "Tests pass" | Run the tests; read output; confirm zero failures (N failures ≠ 0) |
| "Build succeeds" | Run the build; read stdout+stderr; confirm exit 0 AND no warnings promoted to errors |
| "Feature works" | Exercise through real UI; capture evidence; match to PASS criteria |
| "Phase complete" | Re-run every prior gate; confirm each still PASSES with fresh evidence |
| "Ready to merge" | All gates PASS + preflight CLEAR + linter clean + no new warnings |
| "Ready to ship" | All above + accessibility clean + responsive verified + rollback plan documented |
Red Flags (stop — do not claim yet)
- "It should work now" → not evidence
- "The last time I ran it, it passed" → re-run
- "The error went away" → what caused it? is the root fixed or masked?
- "Tests pass (I think)" → read the output
- "Ready for review" without running the verification script → no
- "Just need to push" without local preflight CLEAR → no
Phase-Transition Use
In a deepest-plan <phase_gate>:
<phase_gate id="PG-2" from_phase="01" to_phase="02"
verdict_by="gate-validation-discipline">
<regression_check skill="verification-before-completion">
Re-execute VG-1 and VG-2 (prior-phase gates).
Read evidence at e2e-evidence/vg1-*, vg2-*.
Each must still PASS with cited evidence.
</regression_check>
<current_phase_summary>VG-3 PASS with cited evidence.</current_phase_summary>
<verdict>PASS → enter phase 02 | FAIL → fix regression first, halt.</verdict>
</phase_gate>
Rules
- Never claim completion without running the verification command
- Never claim completion without reading the output
- Never skip the phase-transition regression check
- Always cite evidence when making a completion claim
- "It should work" / "I'm pretty sure" / "probably fine" are forbidden phrases at verification time
Security Policy
Read-only verification. Never modifies code, configs, or state during the verification pass.