What problem does it solve? After implementing a BeeSDK issue, teams need independent verification that acceptance criteria are met, public contracts remain compatible, and no scope creep or unsafe changes slipped in. This Skill performs that post-implementation verification and applies only the minimal corrections required by unsatisfied criteria or explicit review blockers. ## Core Features & Use Cases - Independent Verification: Evaluates every acceptance criterion as satisfied, partially satisfied, not satisfied, not verifiable, or not applicable, with a strict target safety gate checking worktree, branch, and git status before any work. - Scoped Corrections: Applies only minimal, KISS-compliant fixes tied to unsatisfied criteria or explicit final-review blockers, prohibiting unrelated refactoring, new comments, or speculative changes. - Structured Evidence Report: Produces a consolidated 18-section report covering acceptance criteria coverage, corrections made, tests and commands, security review, dependencies, and final readiness. - Use Case: After a developer implements an approved BeeSDK issue, run this workflow to independently verify the diff, run required checks like pytest and package build, fix any blocking findings, and return evidence for read-only review. ## Quick Start Verify the implemented BeeSDK issue in the current worktree against its approved task contract and return the final evidence report.
