goalforge-verifylisted
Install: claude install-skill Truncuso/cogwright
# SDD Verify
Advances a WP from `executing → verified` after confirming all evidence
requirements are met. Delegates to `superpowers:verification-before-completion`.
## Plans root
The `<wp-path>` argument points to a WP folder inside `<PLANS_ROOT>/<feature>/`.
Resolve `<PLANS_ROOT>` per `${CLAUDE_PLUGIN_ROOT}/references/schema.md`
§PLANS_ROOT resolution: env `SDD_PLANS_DIR` → project git-root `plans/` →
global `~/.claude/plans/`.
## Preconditions
Before any verification work begins, this skill performs a hard gate check.
**Both conditions must be true, or the skill refuses and halts:**
1. **All child tasks are `implemented`** (or already `verified` on a re-run) —
every `task-*.md` in the WP folder must have `status: implemented` (committed,
deterministic eval passed) or `verified`. A task still `pending`/`in-progress`
means execution is unfinished. (goalforge-verify is the gate that *promotes*
`implemented → verified`; it does not require tasks to be `verified` going in.)
2. **`findings.md` exists** — the WP folder must contain a `findings.md` file.
This is the structural precondition; the final invariant from
`goalforge/references/schema.md` — `verified` ⇒ all child tasks `verified` +
`findings.md` exists — is satisfied by the promotion step in Completion below.
If either condition is not met, the skill MUST:
- Print which tasks are not yet `implemented` (list them by name).
- State whether `findings.md` is present or absent.
- Refuse to advance the WP st