test-plan-reviewer

Assess and validate Test Plans for verifiable behavior and coverage.

11|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ylxmf2005/AgentCorp --skill test-plan-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-plan-reviewer
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/test-plan-reviewer
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill test-plan-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Judges the quality of Test Plans before implementation to prevent test theater by ensuring the plan contains verifiable, observable checks rather than vague promises. It helps identify gaps where coverage, risk handling, and execution prerequisites are missing and ensures the plan supports measurable outcomes.

Core Features & Use Cases

  • Coverage validation: maps every objective to a verifiable check and ties risk to test coverage.
  • Critical-path and failure-mode focus: highlights essential paths, error handling, concurrency, rollback, and data/permissions boundaries.
  • Falsifiability and contract clarity: requires explicit, testable assertions and public contract checks that enable end-to-end verification.
  • Executability and context alignment: ensures the plan can be run against the declared testing context with concrete steps and environment requirements.

Quick Start

Open test/test-plan.md and the associated plan_files to issue a verdict following the four possible outcomes.

Frequently Asked Questions about test-plan-reviewer

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

FAQPage Schema
How do I review a test plan to ensure it verifies actual behavior?

A test plan review assesses coverage, critical paths, falsifiability, and end-to-end executability against validated requirements to ensure it verifies actual behavior rather than presenting superficial checks.

What is test theater and how do I prevent it in my test plan?

Test theater occurs when a test plan presents superficial checks instead of verifiable assertions. Prevent it by validating that every objective maps to an observable check, ensuring critical paths and failure modes are explicitly covered.

How do I validate test coverage and critical paths before implementation?

Validate test coverage by mapping every objective to a verifiable check and tying risk to test coverage. Focus on critical paths, error handling, concurrency, rollback, and data boundaries to ensure the plan supports measurable outcomes.

Can I issue a formal go-no-go decision for a test plan using automated review?

Yes, you can issue a formal go-no-go decision by analyzing the test plan's executability and context alignment, resulting in a verdict of approve, request_changes, needs_more_evidence, or blocked.

What do I need to provide to assess a test plan for end-to-end executability?

To assess end-to-end executability, you need to provide the test-plan set including test/test-plan.md and plan_files, along with the validated requirements to ensure the plan can run against the declared testing context.

When should I request more evidence during a test plan review?

You should request more evidence when the test plan lacks explicit, testable assertions or public contract checks, preventing a clear approve decision and requiring further validation of its observable outcomes.