verify-planlisted

# Verify Plan > Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference. Verify plans against real code before execution. Spawns one Opus subagent (`bdk:plan-verifier`) that runs a six-section checklist and returns a YAML verdict envelope. ## Invocation ``` /bdk:verify-plan docs/plans/2026-03-17-some-plan.md ``` `$ARGUMENTS` = plan file path. Read file first. ## Decision Flow ```mermaid flowchart TB start([Read plan file]) --> spawn[Spawn bdk:plan-verifier<br/>opus, six-section checklist] spawn --> parse[Parse YAML verdict envelope] parse --> status{status?} status -- PASS or<br/>PASS_WITH_WARNINGS --> save([Render verdict-template<br/>Write report]) status -- FAIL --> iter_check{iteration < 2?} iter_check -- YES --> delta[Build delta message<br/>SendMessage verifier_agent_id] delta -- reply --> parse iter_check -- NO 2 failures --> escalate([Plan needs rethink.<br/>Suggest /bdk:design]) classDef good fill:#d4edda,stroke:#3aa055 classDef bad fill:#f8d7da,stroke:#c25a1b class start,save good class escalate bad ``` ## Step 1 — Locate Plan File Parse `$ARGUMENTS`. Validate the path exists. Read the full content. Compute `plan-slug` = basename without `.md` extension. If the path is missing or empty, abort with a clear error and stop. ## Step 2 — Spawn `bdk:plan-verifier` Use the Agent tool with `subagent_type: "bdk:plan-verifier"` and this message body: ``` PLAN FILE: <path> ITERA