plan-review

Analyze plan findings in a forked context and generate a _plan-review.md.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/mcsdodo/kniha-jazd --skill plan-review-mcsdodo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/mcsdodo/kniha-jazd/tree/main/.claude/skills/plan-review-skill
Command: npx skills add https://github.com/mcsdodo/kniha-jazd --skill plan-review-mcsdodo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Review provides a structured, forked-context analysis to validate plans before committing implementation, reducing rework and misaligned expectations.

Core Features & Use Cases

  • Two-phase review: analyze/document findings in a forked context, then apply approved changes in the main context.
  • Iterative findings with a 4-round limit, clear categorizations (Critical/Important/Minor), and structured recommendations.
  • Generates a _plan-review.md with findings and a final recommendation.

Quick Start

Feed the plan path to the skill and generate a _plan-review.md with findings and a recommendation.

Frequently Asked Questions about plan-review

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

FAQPage Schema
How do I validate project plans before implementation to reduce rework?

Plan validation isolates your project plans in a forked context to analyze completeness, feasibility, and risks, returning a structured review document with actionable recommendations to reduce rework.

What is the best way to review project plans for completeness and risks?

Reviewing project plans for risks works best by documenting findings iteratively up to four rounds, categorizing issues as Critical, Important, or Minor, and generating a structured markdown file for traceability.

How do I generate a plan review document with actionable recommendations?

Generate a plan review document by feeding the plan path into the review process, which analyzes the content in a forked context and outputs a _plan-review.md file containing findings and a final recommendation.

Does the plan review process apply changes directly to the main project context?

No, the plan review process uses a two-phase approach where analysis and documentation happen in an isolated forked context, ensuring only approved changes are later applied to the main context.

What is the iteration limit for analyzing and categorizing plan findings?

The iteration limit for analyzing and categorizing plan findings is four rounds, ensuring a structured yet bounded review process that captures critical, important, and minor issues effectively.