plan-review-gate

Validates implementation plans using three parallel adversarial reviewers before user presentation.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/seal-harness/seal-harness --skill plan-review-gate-seal-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review-gate
Source: https://github.com/seal-harness/seal-harness/tree/main/.agents/skills/plan-review-gate
Command: npx skills add https://github.com/seal-harness/seal-harness --skill plan-review-gate-seal-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Implementation plans drafted by AI agents often contain fabricated file paths, missing requirements, or scope creep that only surface during execution. This skill blocks flawed plans from reaching the user by requiring three independent adversarial reviews to pass before any plan is presented. ## Core Features & Use Cases - Parallel Adversarial Review: Spawns three fresh Task() instances — Feasibility, Completeness, and Scope & Alignment reviewers — that independently verify the plan against the real codebase with read-only access. - Binary PASS/FAIL Gate: Every reviewer produces an evidence-backed verdict; any single BLOCKING issue fails the gate and forces plan revision, with a maximum of 3 iterations before escalation to the user. - Reviewer Isolation: Fresh instances on every iteration with no cross-reviewer visibility prevent anchoring bias and confirmation bias from the original planner. - Use Case: After an agent drafts a multi-file refactoring plan, the gate verifies every referenced file exists via glob, maps each user requirement to a work unit, and rejects scope creep before you ever see the plan. ## Quick Start Ask the agent to draft an implementation plan for your feature request and the gate will automatically review it before presenting it to you.

Frequently Asked Questions about plan-review-gate

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

FAQPage Schema
How do I validate an AI-generated implementation plan before execution?

Run the plan through an adversarial review gate that spawns independent reviewers to check feasibility, completeness, and scope against the actual codebase. Each reviewer returns a PASS or FAIL verdict with cited evidence, and all three must pass before the plan is presented.

What does the plan review gate check for?

It checks three dimensions: Feasibility verifies file paths exist and dependencies are ordered correctly, Completeness maps every user requirement to a plan item with verification steps, and Scope & Alignment detects scope creep or under-scoping relative to the request.

When should I skip the plan review gate?

Skip it only for trivial changes such as single-file bug fixes, copy edits, or config tweaks. Any plan with at least 2 work units or touching 3 or more files should go through the gate.

What happens if a plan fails the review gate?

The planner receives consolidated feedback from all reviewers, revises the plan or rebuts findings with evidence, and three entirely fresh reviewer instances re-review it. After 3 failed iterations, the gate escalates to the user with remaining issues and options to override, revise, simplify, or cancel.

Why must reviewers be fresh instances with no prior context?

Reusing reviewer instances causes anchoring bias, where reviewers check for previous findings instead of reviewing independently. Fresh Task() instances with no cross-reviewer visibility ensure each review cycle is a genuine independent check.