validate-plan-file

Validating orchestrator plan files against a JSON schema requires checking base and domain-specific constraints to prevent malformed inputs. This skill applies validation at creation or before workers read them, covering bug, security, dead-code, and dependency workflows.

Preventing downstream failures from malformed orchestrator plans requires schema-based validation before processing. By validating plan content against shared JSON schemas, you catch misconfigurations and unsafe behavior early at commit time or prior to deployment.

JSON schema validation supports all orchestrator plan types, including bug, security, dead-code, and dependency workflows. It enforces both base and domain-specific checks to ensure plans meet required structural and contextual constraints.

Detailed error reporting for orchestrator plan validation issues is generated automatically when schema loading and checks are applied. This reporting guides quick remediation by pinpointing exactly where and how a plan file violates defined constraints.

Validating orchestrator plan files is needed at creation or commit time, and before workers read them. This prevents runtime errors and ensures workers only consume structurally sound, schema-compliant plans in relevant environments.

Orchestrator plan validation works without external dependencies, relying solely on defined JSON schemas and internal loading mechanisms. It applies base and domain-specific constraints independently to verify plan files.