plan-deep-dive

Inspects each phase of a multi-phase plan for gaps, quality issues, and future risks.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill plan-deep-dive-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-deep-dive
Source: https://github.com/allemaar/open-skills/tree/main/skills/plan-deep-dive
Command: npx skills add https://github.com/allemaar/open-skills --skill plan-deep-dive-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-phase plans often contain hidden gaps, unstated assumptions, and future risks that only surface during execution. This Skill forces a phase-by-phase inspection with mandatory stops, so weaknesses are caught and amended before any work begins. ## Core Features & Use Cases - Iterative Phase Drill-Down: Walks every phase through gap, quality, and future-readiness assessments, never batching or skipping phases. - Verdict System: Assigns each phase a PASS, AMEND, or RETHINK verdict with a running verdict log cited in the final synthesis report. - User-Gated Amendments: Applies fixes to the plan artifact only after explicit user approval of named findings. - Use Case: After drafting a six-phase migration plan, run a deep dive to catch a missing rollback step in Phase 3 and an undeclared dependency in Phase 2 before execution starts. ## Quick Start Ask the agent to do a deep dive on the current implementation plan and inspect each phase for anything missing.

Frequently Asked Questions about plan-deep-dive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a multi-phase plan before executing it?

Run a phase-by-phase deep dive that stops at each phase to assess completeness, quality, and future-readiness. Each phase receives a PASS, AMEND, or RETHINK verdict, and amendments are applied only after you approve the findings.

What is the difference between plan-create and plan-deep-dive?

plan-create produces a new plan from an objective, while plan-deep-dive pressure-tests an existing plan phase by phase. If a deep dive surfaces fundamental design issues, it escalates back to plan-create for a redesign.

Can I deep dive a plan that is not in a file?

Yes. The skill loads implementation_plan.md, PLAN.md, or any multi-phase plan presented inline in the conversation or referenced at any path. It confirms the loaded artifact with you before starting the inspection.

When does a phase get a RETHINK verdict?

A phase gets RETHINK when its primary deliverable is undefined, it depends on undeclared work, or its approach contradicts a stated plan constraint. RETHINK stops the deep dive and recommends redesigning with plan-create.

Why does the deep dive refuse to skip or batch phases?

The forced stops are the core value of the method: batching phases lets gaps and assumptions slip through unexamined. Each phase must pass gap, quality, and future assessments with at least one named finding or an explicit justification.