plan-validate

Validate plan frontmatter fields, values, and structure for consistency.

Updated Jan 20, 2026

Search Tags:#metadata #pre-commit #ci-cd #quality-assurance #frontmatter #plan-validation #design-planning

Ready to run

npx skills add https://github.com/spencerbeggs/claude-design-coordinator --skill plan-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-validate
Source: https://github.com/spencerbeggs/claude-design-coordinator/tree/main/.claude/skills/plan-validate
Command: npx skills add https://github.com/spencerbeggs/claude-design-coordinator --skill plan-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Plans often miss essential frontmatter and formatting, leading to inconsistent project tracking and miscommunication. This skill validates plan documents to ensure required fields exist and values meet defined constraints.

Core Features & Use Cases

Validates required frontmatter fields (name, title, created, status, progress) and their data types.
Checks status-progress alignment, date formats, and required conditional fields (completed/outcome, abandoned/archival).
Generates actionable feedback and can be integrated into pre-commit or CI workflows.

Quick Start

Run the plan validation command for a specific plan or use --all to validate all plans.

Frequently Asked Questions about plan-validate

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

FAQPage Schema

How do I validate frontmatter metadata in design plan documents?▼

To validate frontmatter metadata in design plan documents, run the validation command on a specific plan or use the --all flag. This identifies missing required fields, invalid values, and structural issues across active and archived entries in .claude/plans.

What's the best way to enforce required fields and date formats in plan frontmatter?▼

Enforcing required fields and date formats in plan frontmatter requires a validation script that checks data types, status-progress alignment, and conditional field rules. This ensures metadata consistency and governance across all design plan documents.

Can I integrate plan frontmatter validation into pre-commit hooks or CI workflows?▼

Yes, you can integrate plan frontmatter validation into pre-commit hooks or CI workflows. The validation generates actionable feedback and provides integration hooks to automate quality assurance checks before code commits.

How does status-progress alignment validation work for design plan metadata?▼

Status-progress alignment validation checks that the progress value matches the declared status in plan frontmatter. It enforces required conditional fields like completed/outcome for finished plans and abandoned/archival entries for dropped ones to maintain tracking accuracy.

Why do my design plans fail metadata consistency checks in .claude/plans?▼

Design plans fail metadata consistency checks when required frontmatter fields like name, title, created, status, or progress are missing, contain invalid data types, or violate conditional field rules. The validator reports these structural issues with actionable feedback.