spec-validation

Validate Phase II specifications for completeness, consistency, and readiness.

Updated Jan 6, 2026

Search Tags:#automation #documentation #specifications #validate #yaml-frontmatter #phase-ii

Ready to run

npx skills add https://github.com/Ahmednoorani258/Hackathon2-phase3 --skill spec-validation-ahmednoorani258

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-validation
Source: https://github.com/Ahmednoorani258/Hackathon2-phase3/tree/main/.claude/skills/spec-validation
Command: npx skills add https://github.com/Ahmednoorani258/Hackathon2-phase3 --skill spec-validation-ahmednoorani258

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Spec Validation solves the problem of ensuring Phase II specifications are complete, internally consistent, and ready for implementation by providing automated checks and guided manual reviews.

Core Features & Use Cases

Automated checks for required frontmatter, body sections, and placeholders
Cross-reference verification to plan.md and tasks.md with guidance on remediation
Manual qualitative review guidance covering completeness, consistency, and acceptance criteria quality
Gate decision guidance on readiness to proceed with implementation

Quick Start

Run python .claude/skills/spec-validation/scripts/validate_spec.py specs/<feature-name>/spec.md to start automated checks.

Frequently Asked Questions about spec-validation

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

FAQPage Schema

How do I validate Phase II specifications for completeness before implementation?▼

Validate Phase II specifications by running automated checks on required frontmatter, body sections, and placeholders. The script processes specs under the specs/ directory and verifies cross-references to plan.md and tasks.md.

What are the required frontmatter fields for a Phase II spec?▼

Required frontmatter fields are enforced through automated validation checks targeting Phase II specs. The validation script scans your spec.md files to ensure all mandatory metadata is present before implementation begins.

How do I check if my spec has unresolved placeholders or missing body sections?▼

Check for unresolved placeholders and missing body sections by running the validation script. It detects incomplete specifications and provides guided manual review prompts for qualitative completeness and consistency.

Can I verify cross-references between spec.md, plan.md, and tasks.md automatically?▼

Cross-reference verification to plan.md and tasks.md is performed automatically. The validator checks these dependencies within your specs/ directory and provides specific remediation guidance for any broken links.

Does the spec validation script require any external dependencies to run?▼

The spec validation script requires no external dependencies to run. It operates as a standalone Python script within the .claude/skills/ directory to evaluate specification readiness.

When should I use automated spec validation versus a manual review process?▼

Use automated validation first to catch missing frontmatter and placeholders, then follow the guided manual review for qualitative checks. This combined approach evaluates acceptance criteria quality and provides a gate decision on implementation readiness.