plan-test-validate

Validate test plan documents against the SDD standard for structure and coverage.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill plan-test-validate-nsevteev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-test-validate
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/plan-test-validate
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill plan-test-validate-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates test plan documents to ensure they meet the SDD standard, including required frontmatter, naming conventions, and coverage of REQ-N/STS-N, markers, matrix, and ownership zones.

Core Features & Use Cases

  • Validation of frontmatter fields and naming conventions in plan-test documents.
  • Coverage verification for REQ-N and STS-N references, matrix, markers, and ownership notes.
  • Useful during plan creation, peer reviews, or pre-commit checks to ensure consistency before publication.

Quick Start

Run /plan-test-validate specs/analysis/0001-auth-oauth2/plan-test.md to validate that plan.

Frequently Asked Questions about plan-test-validate

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

FAQPage Schema
How do I validate test plan documents against SDD standards?▼

To validate test plan documents against SDD standards, run a validation check on your plan files to verify required frontmatter, naming conventions, and REQ-N/STS-N coverage. This ensures consistent structure and compliance before publication.

Can I check an entire directory of test plans for SDD compliance?▼

Yes, you can check an entire directory of test plans for SDD compliance by using the --all option. This processes all plan files in the directory, validating frontmatter, markers, matrix, and ownership notes collectively.

What does SDD test plan validation check for in my files?▼

SDD test plan validation checks for required frontmatter fields like name and description, verifies plan structure, and ensures evidence of REQ-N/STS-N coverage, markers, matrix, and ownership zones are present.

How do I generate JSON reports for test plan validation results?▼

To generate JSON reports for test plan validation results, use the --json option when running the validator. This outputs structured reporting data detailing the compliance status of frontmatter and coverage markers.

When should I run a test plan validation check in my workflow?▼

You should run a test plan validation check during plan creation, peer code reviews, or as a pre-commit hook in CI/CD. This ensures quality assurance and catches structural inconsistencies before plans are published.