What problem does it solve?
This Skill prevents developers from declaring work finished or committing code before the implementation has been independently checked against the approved requirement contract. It addresses the common failure mode where code is technically correct and tests pass, but the delivered behavior still misses acceptance criteria, exceeds scope, or diverges from the intended design.
Core Features & Use Cases
- Independent acceptance review: Requires a separate subAgent to verify implementation against story.md and, when present, design.md rather than relying on the implementer's self-assessment.
- Dual-contract validation: Checks both user intent and implementation plan using six criteria covering completeness, correctness, redundancy, bias, scope creep, and missing in-scope functionality.
- Commit-time quality gate: Supports a git commit workflow by prompting verification whenever related approved stories have not yet been marked verified.
- Traceable verification reports: Produces round-based verify-report files that preserve evidence, failures, user-decision items, and remediation history.
- Use case: When a feature branch appears complete, use this Skill to review the actual diff against the approved story and design, generate a verification report, and only then mark the story as verified before committing.
Quick Start
Use the verification-gate skill to review my current feature changes against the related approved story and generate a verification report before I commit.
