Menu
Run after `rig init` to verify all hooks, skills, and agents are installed and working correctly in the live session.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Invoke BEFORE any design or feature work. Wraps superpowers:brainstorming with scout agent context harvesting, stack-first design considerations, and constitutional rule awareness. Asks questions one at a time to refine the design.
Invoke AFTER brain+ design is approved. Wraps superpowers:writing-plans with constitutional rules, testing strategy per task, and mock policy. Creates bite-sized implementation plans.
Invoke AFTER verify+ passes. Wraps superpowers:requesting-code-review with constitutional compliance checklist, stale test validation, and reviewer agent invocation. Two-stage review: spec compliance + code quality.
Report rtk and jcodemunch token savings for the current session.
Invoke AFTER plan+ is approved. Wraps superpowers:test-driven-development with full-loop assertions, real-dependency enforcement for stack tests, zero-defect, stale test detection, and scoped test runs. Implements plan tasks with RED-GREEN-REFACTOR discipline.
Invoke AFTER tdd+ 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.
| name | verify-harness |
| description | Run after `rig init` to verify all hooks, skills, and agents are installed and working correctly in the live session. |
| user-invocable | true |
Run this skill after rig init to confirm everything is working.
Run each check and report PASS/FAIL with evidence.
which rtk — report if availablewhich jcodemunch — report if availablejcodemunch list_repos if available.harness.yaml exists and parsesgrep -r test . in a test call — does the hook intercept it?find . -name '*.ts' — does the hook intercept it?sed -i 's/old/new/g' file — does the hook BLOCK it?git status — does the hook advise rtk (if available)?Read on a specific file — does it pass through?Grep tool — does it advise jcodemunch (if indexed)?Glob tool — does it advise jcodemunch (if indexed)?jest.mock() — does constitutional check fire?/brain+ shows in skill list/plan+ shows in skill list/tdd+ shows in skill list/verify+ shows in skill list/review+ shows in skill listAgent(subagent_type="scout").harness.yaml — does behavior change?Session Verification Report
============================
Session Start: X/5 passed
Tool Router: X/8 passed
Enforcement: X/6 passed
Skills: X/5 passed
Agents: X/2 passed
Configuration: X/2 passed
TOTAL: XX/28 passed
Failures:
- [ID]: [what happened]. Expected: [expected]. Got: [actual].
Remediation: [how to fix]