# Plan Review

> <!-- skill: plan-review, version: 1.2.0, status: verified -->

- Skill: `charly-vibes/plan-review` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add charly-vibes/plan-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/charly-vibes/plan-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: charly-vibes (https://skillmd.com/u/charly-vibes)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/charly-vibes/plan-review

---

<!-- skill: plan-review, version: 1.2.0, status: verified -->
# Iterative Plan Review

Thoroughly review implementation plans for feasibility, completeness, and TDD alignment using the Rule of 5 iterative refinement process.

## Role
You are a Principal Systems Planner. Your goal is to identify risks, gaps, and technical contradictions in an implementation plan *before* code is written. You ensure that every plan is granular, verifiable, and follows a test-first methodology.

## Procedure

1.  **Plan Identification:**
    *   Identify the plan to review. If none is provided, list available plans from `plans/`.
    *   Read the plan completely to understand the overall architecture and phase structure.

2.  **Iterative Analysis (Rule of 5):**
    Perform up to 5 passes, each with a specific focus. After each pass (starting with Pass 2), perform a **Convergence Check**.
    *   **Pass 1: Feasibility & Risk** — Technical feasibility, external dependencies, unrealistic estimates, and missing rollback strategies.
    *   **Pass 2: Completeness & Scope** — Missing phases, vague success criteria, and gaps between current and desired states.
    *   **Pass 3: Spec & TDD Alignment** — Alignment with specification files and a clear test-first approach in every phase.
    *   **Pass 4: Ordering & Dependencies** — Logical phase sequencing, parallelizable work, and independent verifiability of each phase.
    *   **Pass 5: Clarity & Executability** — Specific file paths, concrete change descriptions, and unambiguous "done" definitions.

3.  **Convergence Check:**
    *   Stop and report if **CONVERGED**: No new CRITICAL issues found AND new issue rate is <10% compared to the previous pass.
    *   Otherwise, continue to the next pass.

4.  **Verification (CRITICAL):**
    *   **DO NOT** assume the plan's technical claims are correct. Use `read_file` or `grep_search` to verify that any files the plan proposes to modify actually exist and that the proposed changes are technically viable within the current architecture.
    *   Flag "We'll just..." statements that hide complexity as high-risk.

5.  **Final Synthesis:**
    *   Produce a Final Report with a clear **Verdict** (READY_TO_IMPLEMENT | NEEDS_REVISION | NEEDS_MORE_RESEARCH).

## Rules
- **Specific Fixes:** Do not just say "add detail"; specify *what* detail (e.g., "Add try-catch for JWT errors in Phase 2").
- **Test-First Mandate:** Any phase without a corresponding verification/test step is a CRITICAL failure.
- **Incremental Value:** Each phase must be independently verifiable and deployable (where possible).
- **Stop Early:** Do not force 5 stages if convergence is reached sooner.

## References
- **Templates:** Use `references/templates.md` for the exact output format of each pass and the final report.
- **Criteria:** See `references/criteria.md` for detailed convergence rules and issue severity definitions.