gza-plan-review

Evaluate plan tasks with an interactive five-area quality gate.

11|1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/mhawthorne/gza --skill gza-plan-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gza-plan-review
Source: https://github.com/mhawthorne/gza/tree/main/src/gza/skills/gza-plan-review
Command: npx skills add https://github.com/mhawthorne/gza --skill gza-plan-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan tasks require human-in-the-loop validation to determine readiness for implementation. This skill provides an interactive quality gate to verify a plan task and decide Go/No-Go.

Core Features & Use Cases

  • Five-area quality gate: scope clarity, acceptance criteria, risks, dependencies, and test strategy.
  • Interactive questioning via AskUserQuestion to surface assumptions.
  • Generates a structured Plan Review output with task context, gate results, and follow-up actions for execution.

Quick Start

Supply a plan task ID to begin the interactive quality gate and generate a go/no-go recommendation.

Frequently Asked Questions about gza-plan-review

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

FAQPage Schema
What is a plan task go/no-go quality gate and when do I need one?

A plan task go/no-go quality gate interactively verifies scope, acceptance criteria, risks, dependencies, and test strategy before implementation begins. You need one to confirm plan readiness and surface hidden assumptions prior to development.

How do I run an interactive plan review for a specific task ID?

Supply a plan task ID to initiate the interactive five-area quality gate. The process uses AskUserQuestion to surface assumptions, inspects tasks with uv commands, and generates a structured go/no-go recommendation with follow-up actions.

Can I use this quality gate to verify risks and dependencies for plan-type tasks?

Yes, the quality gate explicitly verifies risks and dependencies for plan-type tasks. It evaluates five core areas—scope clarity, acceptance criteria, risks, dependencies, and test strategy—to produce a comprehensive go or no-go readiness recommendation.

What does the plan review output include after the interactive questioning?

The output includes task context, five-area gate results, and proposed follow-up actions for execution. It delivers a structured go or no-go recommendation based on the interactive validation of scope, criteria, risks, dependencies, and test strategy.

What are the limitations of using a five-area gate for planning workflow validation?

The five-area gate is limited to validating scope, acceptance criteria, risks, dependencies, and test strategy for plan-type tasks. It requires human-in-the-loop interaction throughout and does not automatically execute implementation or validate post-development outcomes.