validation-scripts

You validate Copilot agent frontmatter and YAML structure by running PowerShell scripts that automatically check required metadata fields and file structure. This centralized validation catches structural issues in agents, prompts, and instructions early before orchestration proceeds.

Automating Copilot asset validation during phase implementations is best handled by running PowerShell validation scripts at conductor pause points and phase milestones. This gates progress by enforcing required metadata fields and catching structural errors before orchestration continues.

Yes, you need PowerShell to check Copilot conductor file structure and metadata because these validation scripts are PowerShell-based. They enforce required metadata fields and document auto-approved versus approval-needed scripts to ensure safe execution.

Yes, you can run validation scripts automatically after changes to Copilot prompts to catch structural errors. The scripts verify frontmatter, YAML, and file structure, integrating at phase-related milestones to gate progress and prevent unintended changes.

Auto-approved validation scripts differ from approval-needed scripts by executing safely without manual intervention, while approval-needed scripts require explicit permission to prevent unintended changes to Copilot assets. This distinction ensures safe execution during validation workflows.

Copilot orchestration fails after modifying agent frontmatter because required metadata fields or YAML structure are invalid. Running PowerShell validation scripts verifies frontmatter correctness and catches structural errors before orchestration proceeds.