/deep-dive

Phase-by-phase deep inspection of any multi-phase plan. Stop at each phase, assess completeness, quality, and future-readiness before moving on.

Structured execution spec: protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the @STAMP date.

Caller Options. Before executing, run the Caller Options protocol (caller-options/SKILL.md): triage this invocation for material optionality across the venues declared in front-matter; if one path clearly dominates, proceed silently; otherwise surface the options. For very long plans, delegated keeps the main context clean while a sub-agent walks the phases and returns the verdict log.

Iterative Depth Protocol. /plan-create produces the plan. /deep-dive pressure-tests it phase by phase. Never batch or skip phases — the value is in the forced stops.

When to escalate to plan-create

If phase-by-phase inspection surfaces gaps that would require redesigning the plan rather than tweaking it (missing phase, wrong sequencing, fundamental approach issue), stop the deep-dive and recommend /plan-create to redesign.

Phase 1 — Load & Enumerate

Identify the active plan. Load implementation_plan.md, PLAN.md, or the current multi-phase artifact (e.g. a multi-phase plan presented inline in the conversation, or a plan document at any path the user has referenced). Extract the ordered list of phases.

Verification step: before entering Phase 2, present the loaded artifact's title and first substantive line to the user and ask: "Is this the correct and current plan?" Do not proceed until confirmed.