validate-plan-file

To validate a plan file, the Skill checks it against JSON Schema Draft-07 specifications to ensure structural integrity. It verifies required fields, data types, enum constraints, and pattern matching to prevent runtime errors before processing.

Plan file validation applies to all orchestrator types including bug, security, dead code, and dependency workflows. The schema validation ensures each specific workflow type adheres to its required parameters and structural constraints.

Security scanning failures occur when plan files lack required fields or contain invalid enum values. Validating the plan file structure and parameters before the worker reads it prevents runtime errors and ensures the scan is configured correctly.

Yes, JSON Schema Draft-07 validation enforces enum constraints, type checking, and pattern matching for plan files. This ensures strict schema compliance and identifies missing fields or incorrect data types during the validation process.

The best way to check for missing fields is validating the JSON plan file against its predefined schema. This error detection process identifies missing fields, incorrect data types, and invalid enum values to ensure consistency.