verify
SolidInvoke AFTER tdd+ or sdd+ implementation is complete. Wraps superpowers:verification-before-completion with evidence standards, spec drift check, and full-suite test run. This is the ONLY phase where full test suite runs are appropriate.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- franklywatson
- Repository
- franklywatson/claude-rig
- Created
- 5 months ago
- Last Updated
- 3 days ago
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
session-verify
Evidence-based verification workflow for completed features and plans. Produces a falsifiable proof artifact that implementation matches design spec, identifying defects, stubs, and spec-vs-reality gaps. Triggers on "/session-verify" or when user says "verify this feature", "prove this works", "run verification", or "confirm the implementation".
verify
Build a test plan from a task's acceptance criteria, document it (or push it to Jira), run the verification (unit + E2E + app behavior), and record a pass/fail verdict in the task log. Used by the Tester agent on IN_TEST tasks. Does not edit production code — proposes fixes back to the Coder. Pushing the test plan to Jira is a HIGH action (approval-gated).
verification-before-completion
Use when about to claim work is done, fixed, passing, or ready to merge — it forces a real run of the verifying command first. Not for reporting a failure honestly, which needs no gate. Runs last, after any review skill.