plan-review-gate

Validate C-1/C-2/C-3 gates and authorize plan execution.

2|Updated Sep 13, 2025
One-click install
npx skills add https://github.com/s977043/plangate --skill plan-review-gate-s977043
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review-gate
Source: https://github.com/s977043/plangate/tree/main/.agents/skills/plan-review-gate
Command: npx skills add https://github.com/s977043/plangate --skill plan-review-gate-s977043

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-driven development workflows rely on multi-stage review gates (C-1, C-2, C-3) before starting execution. This Skill ensures that a plan has passed all required gates and is safe to begin execution, reducing the risk of premature or unsafe AI actions.

Core Features & Use Cases

  • Gate validation: verifies that C-1, C-2, and C-3 checks are satisfied by inspecting the latest review artifacts (review-self.md, review-external.md, status.md) and ensuring issues are addressed.
  • Evidence consolidation: aggregates plan status, completed tasks, and test cases to support a clear go/no-go decision.
  • Use scenarios: applicable when you need a formal checkpoint to authorize exec after plan reviews, especially in strict CD/CI-like AI workflows.

Quick Start

Check the current plan review status to determine whether execution may begin.

Frequently Asked Questions about plan-review-gate

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

FAQPage Schema
What is an AI development plan review gate and when do I need one?

An AI development plan review gate is a formal checkpoint that validates multi-stage reviews before execution starts. You need one in strict AI-driven workflows to ensure plan.md, todo.md, and test-cases.md are current and safe, reducing the risk of premature AI actions.

How do I validate C-1, C-2, and C-3 review gates before starting execution?

To validate review gates, inspect the latest review artifacts including review-self.md, review-external.md, and status.md. This process verifies that C-1, C-2, and C-3 checks are satisfied, issues are addressed, and plan execution is authorized based on a consolidated go/no-go decision.

Can I use a review gate to block manual task progression if plan artifacts are outdated?

Yes, you can block manual-cloud-task progression if review gates are not satisfied. The gate enforces that plan.md, todo.md, and test-cases.md are strictly current, ensuring the final decision blocks execution until all review artifacts validate the required checks.

Does the plan review gate check test cases and todo status before authorizing execution?

Yes, the plan review gate aggregates plan status, completed tasks, and test cases to support a clear go/no-go decision. It ensures test-cases.md and todo.md are up to date alongside review-self.md and review-external.md before allowing execution to start.

Why does my AI workflow execution not start after the plan review?

Execution may not start because the C-1, C-2, or C-3 gates are not fully satisfied. The review gate blocks progression if review-self.md, review-external.md, or status.md indicate unresolved issues, or if plan artifacts are not current, resulting in a no-go decision.