Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/verification-gates
Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding.
Passed 18 of 23 test cases with the skill, and 15 of 23 without it.
and 5 more in the full report
6 fixed12 passed either way2 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a tight deadline for a new payments service. The team wants to skip verifying requirements edge cases and jump straight into coding the payment processor interfaces to save time, planning to resolve missing requirements during unit testing. How should this workflow be structured?
| Checked | Without skill | With skill |
|---|---|---|
| States that implementation or design must not proceed with unverified assumptions from previous phases. | Missed | Passed |
| Identifies Requirements Verification as Gate 1 prior to starting design work. | Missed | Passed |
The instructions your model reads when the skill loads.
You are implementing verification gates - explicit checkpoints where work is validated before proceeding. This prevents cascading errors and ensures quality at each phase.
Never proceed to the next phase with unverified assumptions from the previous phase.
A verification gate is a deliberate pause to confirm that prerequisites are met before continuing.
Before starting design:
Actions:
Before starting implementation:
Actions:
test cases passed, vs 15 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.