plan-review-gate

Run three parallel adversarial reviews to validate implementation plans with PASS/FAIL verdicts.

Updated Apr 6, 2018

Search Tags:#automation #planning #verification #adversarial #gate #plan-review

Ready to run

npx skills add https://github.com/montoyaedu/Trish --skill plan-review-gate-montoyaedu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-review-gate
Source: https://github.com/montoyaedu/Trish/tree/main/.claude/plugins/metaswarm/skills/plan-review-gate
Command: npx skills add https://github.com/montoyaedu/Trish --skill plan-review-gate-montoyaedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gatekeepers ensure proposed implementation plans pass independent adversarial reviews before user presentation.

Core Features & Use Cases

Three independent reviewers evaluate each plan in parallel; all must PASS.
Iterative review until consensus or max iterations, with escalation.
Binary PASS/FAIL verdict with evidence-backed findings.

Quick Start

Submit a drafted plan to the gate to trigger parallel adversarial reviews.

Frequently Asked Questions about plan-review-gate

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

FAQPage Schema

How does automated plan verification work before delivery?▼

Automated plan verification works by running three independent adversarial reviews in parallel to enforce a binary PASS/FAIL verdict on feasibility, completeness, and scope alignment before delivery.

What is an adversarial gate review for implementation planning?▼

An adversarial gate review is a validation mechanism where independent reviewers evaluate a drafted implementation plan, requiring a unanimous PASS verdict from all reviewers before delivery.

How do I validate an implementation plan with multiple work units?▼

You validate an implementation plan with multiple work units by submitting the drafted plan to trigger parallel adversarial reviews, iterating up to three times until all reviewers reach a PASS consensus or escalate.

What happens if a plan fails the feasibility or completeness review?▼

If a plan fails the feasibility or completeness review, the system iterates the review process up to three times to achieve consensus before escalating the unresolved failed plan to the user.

Do I need any specific dependencies to run automated plan reviews?▼

No specific dependencies are required to run automated plan reviews. The verification process operates independently without external components or frameworks needed.