review-plan

Review PLAN.md files as blind-handoff execution contracts and emit P# findings with ready verdicts.

2|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/siarhei-belavus/agent-public --skill review-plan-siarhei-belavus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/siarhei-belavus/agent-public/tree/main/skills/atelier-workflow/review-plan
Command: npx skills add https://github.com/siarhei-belavus/agent-public --skill review-plan-siarhei-belavus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans handed off between agents often contain ambiguity, hidden assumptions, and choice-language that force the executing agent to guess intent. This Skill reviews a PLAN.md as a strict execution contract and blocks plans that are not safe for blind handoff. ## Core Features & Use Cases - Multi-pass plan review: Runs ambiguity, self-sufficiency, no-choice-language, standards, artifact hygiene, ownership-and-reuse, compatibility-policy, final-state-authoring, and handoff-readiness passes against the plan text. - Structured findings output: Writes a PLAN_REVIEW.md containing a ready/not_ready verdict, compact P# findings ordered by severity, required changes, and preserve-notes. - Initiative child packet checks: Verifies child packets are not placeholder plans and align with the parent initiative, imported context, and contract decisions. - Use Case: Before dispatching a task packet to an implementer agent, run this review to catch vague validation steps like "test it", unnamed owners, or unjustified backward-compatibility shims, then send the findings back to the requesting lead. ## Quick Start Review the PLAN.md in the current task packet as a blind-handoff execution contract and write the verdict and P# findings to PLAN_REVIEW.md.

Frequently Asked Questions about review-plan

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

FAQPage Schema
How do I review a plan before handing it off to another agent?▼

Run the review against the PLAN.md text only, simulating an executor with no conversation context. The review produces a PLAN_REVIEW.md with a ready or not_ready verdict, P# findings ordered by severity, required changes, and preserve-notes.

What makes a plan ready for blind handoff?▼

A plan is ready only when it is unambiguous, self-contained, directive rather than suggestive, explicit about output and validation, free of hidden assumptions, and clear about ownership and reuse. Even one material follow-up question means not_ready.

What wording gets flagged during plan review?▼

Choice-language such as "or", "if needed", "where possible", "consider", "maybe", and "might" is flagged in execution instructions. Vague validation like "test it", unnamed artifacts or owners, and references to unspecified "standard patterns" are also findings.

Does the review handle backward-compatibility decisions?▼

Yes. Internal-only compatibility work is flagged as unnecessary complexity, while plans touching real external boundaries without resolving whether compatibility is required are marked not_ready pending explicit human clarification.

When should a plan not be approved even if it seems workable?▼

Do not approve when the plan relies on conversation context, contains parallel same-purpose implementations without justification, preserves old/new hybrid vocabulary, or requires any material guess. "Probably workable" never counts as ready.