validate-plan-file

Validation checks plan files against structured JSON schemas by matching filename patterns to appropriate schemas, then loading base and domain schemas to catch misconfigurations before they reach workers. This prevents invalid configurations in bug, security, dead-code, and dependency workflows.

Plan file validation provides detailed error reporting on missing fields, invalid values, and constraint violations like priority/severity mismatches or exceeded max items, guiding corrections with specific field-level feedback.

Validate plan files at quality gates before use—during pre-read validation, post-create checks, and debugging stages—to catch schema violations early and prevent propagation of invalid configurations to workers.

Yes, domain-specific validation checks fields like priority, severity, and max items constraints by loading both base schemas and domain-specific schemas matched to your plan filename pattern.

Plan validation uses standardized filename patterns to map files to their appropriate schemas—for example, .bug-detection-plan.json maps to the bug detection schema for automated schema lookup and validation.