verify-planlisted
Install: claude install-skill shashankcm95/claude-power-loom
# verify-plan — Pre-approval verification skill
Before exiting plan mode on a HETS-routed phase, spawn architect + code-reviewer agents in parallel to verify the plan. This catches concrete bugs (bash quoting issues, false-positive auto-passes in validators, empty-release-notes bugs) and plan-honesty issues (self-rationalizing audits, overstated ordering claims, unresolved design choices) BEFORE the user invests review time.
**Codifies drift-note 40** (H.7.22 + H.7.23): the parallel-spawn pattern paid for itself in both phases that ran it.
## When this skill applies
- The current plan file is HETS-routed: `## HETS Spawn Plan` present (with substantive content, not "N/A") OR `Routing Decision` JSON contains `"recommendation": "route"`.
- Plan is in `~/.claude/plans/<name>.md` or in `$CLAUDE_PLAN_DIR/`.
- Plan-mode is active (you're about to ExitPlanMode).
## When this skill does NOT apply
- Trivial / single-file fixes (route-decide returned `root`).
- Hotfixes shipped without plan mode (e.g., H.7.22.1/2/3 — small enough to feel exempt; the cost of `/verify-plan` would exceed the benefit on micro-scope).
- Doc-only edits.
## Procedure (6 steps)
### 1. Read the plan file
```bash
PLAN_PATH="${PLAN_PATH:-$HOME/.claude/plans/$(ls -t $HOME/.claude/plans/*.md 2>/dev/null | head -1 | xargs basename)}"
[ -f "$PLAN_PATH" ] || { echo "ERROR: no plan file at $PLAN_PATH"; exit 1; }
```
Or take `$ARGUMENTS` if explicit path provided. Use the most-recently-modified `.md` in `~/.cla