ln-11-plan-reviewer

Validates implementation plans against repository evidence before execution.

556|83|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-11-plan-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-11-plan-reviewer
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/plugins/review-suite/skills/ln-11-plan-reviewer
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-11-plan-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementation plans often contain unverified assumptions, missing failure handling, or references to code that does not exist, and these defects surface only after costly execution begins. This Skill performs a read-only, evidence-first second pass over a plan to expose gaps and risks before any code is written.

Core Features & Use Cases

  • Evidence-grounded verification: Checks every path, symbol, command, and dependency named in the plan against the actual repository, Git state, and official external documentation.
  • Multi-perspective review: Applies 15 review lenses covering architecture, security, failure modes, testing, and simplicity, plus one independent challenge round with blind reviewers.
  • Decision-complete verdicts: Produces a structured report with BLOCKER/MAJOR/MINOR findings and a clear verdict of READY, READY WITH CONCERNS, REVISE, or BLOCKED, including a corrected plan when needed.
  • Use Case: Before handing a migration plan to an implementation agent, run this Skill to confirm the plan's referenced schemas exist, its sequencing is safe, and its external API claims match current vendor documentation.

Quick Start

Ask the AI to review the implementation plan in docs/migration-plan.md against the current repository before execution.

Frequently Asked Questions about ln-11-plan-reviewer

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

FAQPage Schema
How do I validate an implementation plan before coding?

Run a plan review that verifies every referenced path, symbol, and command against the actual repository, then checks external claims against official documentation. This Skill produces a verdict of READY, READY WITH CONCERNS, REVISE, or BLOCKED with evidence-backed findings.

What is the difference between plan review and code review?

Plan review validates a proposed implementation before execution, checking feasibility, completeness, and repository fit. Code review examines completed changes. This Skill is explicitly for plans and must not be used for completed delivery review.

Can the plan reviewer modify my code or plan files?

No, the review is strictly read-only. It never mutates the source plan, implementation, branch, or external systems; corrected plans appear only inside the review response.

When should a plan review return BLOCKED instead of REVISE?

BLOCKED applies when a required user choice, access, or authoritative fact is unavailable and no concrete plan can be safely evaluated. REVISE applies when correctable BLOCKER or MAJOR findings exist and a replacement plan can be provided.

Does plan review require internet access for documentation?

Only when the plan depends on external claims such as library versions, API behavior, deprecations, or security requirements. Purely repository-local questions are resolved from files, Git history, and code intelligence without web research.