plan-review

Reviews implementation plans against the actual codebase with an independent agent before execution.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/forhas/pure-dev --skill plan-review-forhas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/forhas/pure-dev/tree/main/plugins/notion-dev/skills/plan-review
Command: npx skills add https://github.com/forhas/pure-dev --skill plan-review-forhas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Implementation plans are typically self-reviewed by the same agent that wrote them, so defects like nonexistent file paths, forward task dependencies, and missing test coverage are only discovered after the implementation has already been paid for. This skill dispatches a fresh, review-only agent that verifies the plan against the real repository and returns a machine-parseable verdict before any code is written. ## Core Features & Use Cases - Independent codebase-verified review: A fresh agent reads every file the plan touches, greps for claimed-missing symbols, and checks scope, codebase fit, dependency order, and test coverage using a structured rubric. - Finding triage and plan revision: Each finding is accepted, declined with reasoning, or marked unresolved; accepted fixes are edited into the plan and verified, with deferred work triaged as absorb, file, or drop. - Machine-parseable verdict with graceful degradation: Emits a PLAN-REVIEW output block (clean, proceed-with-warnings, blocked, degraded) that orchestrating flows can gate on, and never blocks the build when the reviewer itself fails. - Use Case: On the notion-dev superpowers build path, the ticket flow invokes this skill with a plan file and context packet; the reviewer catches that Task 4 modifies a file that does not exist, the plan is revised, and the run proceeds with a clean verdict. ## Quick Start Ask the agent to review the implementation plan at plans/my-feature.md against the repository before starting implementation.

Frequently Asked Questions about plan-review

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

FAQPage Schema
How do I review an implementation plan before coding starts?

Invoke the skill with --plan=<path> pointing at the plan file, plus an INTENT block describing the requirement. A fresh review-only agent verifies the plan against the actual repository, and the skill triages findings, revises the plan, and returns a verdict.

What does the plan reviewer check in the repository?

The reviewer reads every file the plan modifies, greps for symbols the plan claims are missing, and checks four axes: scope discipline, codebase fit, dependency order and actionability, and test coverage via a coverage map. Findings are labeled Critical, Required, Optional, Nit, or FYI.

What happens if the review agent fails or returns nothing?

The skill retries once, handles zero-byte and never-returning dispatches explicitly, and can run a PONG control probe to diagnose harness failures. If the reviewer still cannot run, it emits PLAN-REVIEW: degraded and the build proceeds — the review never blocks development on its own failure.

Can a plan with a NOT-CLEAN verdict still proceed?

Yes. Status is computed from unresolved findings after triage, not the raw verdict. If every Critical or Required finding is declined with stated reasoning, the result is clean; unresolved Required findings yield proceed-with-warnings, and only unresolved Critical findings block an auto run.

When should I not use plan-review?

Do not use it on the feature-dev flow, which produces no plan artifact to review. It is designed for the superpowers build path or direct user requests to check a written plan, not for reviewing code diffs — that is handled later by the code review and merge gate.