validate-tests

Validate implementation test plans against guidelines and scenario conventions.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill validate-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-tests
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/validate-tests
Command: npx skills add https://github.com/gittower/git-flow-next --skill validate-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure an implementation plan has a complete, concrete, and reliable test strategy before coding begins, reducing rework and missed edge cases.

Core Features & Use Cases

  • Local test-plan validation: Checks the plan against project testing guidelines and scenario conventions.
  • Codex gate review: Uses an external review pass to find missing, underspecified, or mismatched test cases.
  • Plan hardening: Updates the plan with accepted findings and records applied or rejected feedback for traceability.
  • Use case: Before starting implementation on a Git workflow change, use this Skill to verify the plan covers normal paths, error cases, and Git-specific setup details.

Quick Start

Use the validate-tests skill to review the current implementation plan’s test section, fix gaps, and report whether it is ready for implementation.

Frequently Asked Questions about validate-tests

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

FAQPage Schema
How do I validate test scenarios in an implementation plan before coding starts?

Test scenario validation checks your implementation plan against project testing guidelines and scenario conventions to ensure concrete coverage of normal paths, error cases, and edge cases before development begins.

What is a codex gate review for test plans?

A codex gate review is an external review pass that analyzes your test plan to identify missing, underspecified, or mismatched test cases, helping harden the plan before implementation proceeds.

When do I need to validate test plans for Git workflow changes?

You need test plan validation for Git workflow changes when your implementation requires concrete scenario coverage, guideline compliance, and review of Git-specific setup details, error cases, and expected outcomes.

How do I record accepted or rejected findings from test plan validation?

Plan hardening updates your implementation plan with accepted findings from the review pass and records both applied and rejected feedback to maintain traceability of test coverage decisions.

What are the limitations of automated test plan validation?

Test plan validation requires authoritative source material and testing standards to function effectively. Without concrete project guidelines, the validation cannot reliably assess scenario coverage or identify gaps in error case handling.