squad-creator-validate

To validate a squad manifest, run the validator against your squad path to check SQUAD.yaml parsing, enforce naming conventions, and verify agent references. This process catches structural configuration errors before execution.

Strict mode validation for multi-agent squads treats configuration warnings as errors. It enforces schema v2 compliance, flags missing chiefs or tags, and prevents deployment if any best practice checks fail.

To check required directories in your squad configuration, the validator performs structure verification to ensure required folders like agents/ and skills/ exist alongside a correctly parsed SQUAD.yaml manifest file.

Squad manifest validation fails on agent references when naming conventions are violated or default executor and reviewer designations are missing. The validator enforces these rules to maintain multi-agent configuration integrity.

Yes, you can validate squad configurations without strict mode. The validator will still check SQUAD.yaml schema conformance and directory structures, but will only flag potential issues like missing tags as warnings rather than failing execution.

You need schema validation for your squad manifest before deploying a new squad to prevent runtime errors. Validating against the v2 schema ensures your multi-agent configurations are correctly defined and ready for execution.