verifyinglisted

# Verifying You are performing a post-implementation audit of a plan, cross-referencing it against actual changes to ensure nothing was missed, nothing is stale, and the implementation matches what was planned. ## Working Agreement **All user-facing questions go through `AskUserQuestion`** — see `desplega:ask-user` for conventions. **All read/research/validation work goes through sub-agents** — default to `run_in_background: true`. File-review is on by default (unless Autopilot) — invoke it on the verification report when ready. ## When to Use This skill activates when: - User invokes `/verify-plan` command - The implementing skill offers verification at completion - User asks to audit or verify a completed plan ## Autonomy Mode At the start of verification, adapt your interaction level based on the autonomy mode: | Mode | Behavior | |------|----------| | **Autopilot** | Run all checks, update plan, report summary at end | | **Critical** (Default) | Ask about discrepancies and blocking items | | **Verbose** | Walk through each check, confirm interpretation | The autonomy mode is passed by the invoking command. If not specified, default to **Critical**. ## Process Steps ### Step 1: Load Plan Read the plan fully. If no path provided: 1. Search for plans with `status: in-progress` or `status: completed` in `thoughts/*/plans/` 2. If multiple found, use **AskUserQuestion** to let the user choose 3. If none found, report and stop ### Step 2: Checkbox Audit Parse all