validate-task

You can validate task metadata against schema v2.0 by checking required fields, verifying correct formats, and enforcing bidirectional parent-child links to ensure compliance and report actionable pass or fail details.

Metadata validation for workflow items is the process of checking tasks, stories, epics, bugs, and techdebt against schema v2.0 to prevent inconsistencies, verify cross-item relationships, and avoid downstream errors.

Apply a validation check after TaskUpdate or TaskCreate to verify item integrity, ensuring required fields are present, formats are correct, and bidirectional parent-child links are properly established across items.

Yes, you can validate cross-item relationships for bugs and techdebt by verifying bidirectional parent-child links and checking versioning against schema v2.0 to ensure all item types maintain structural integrity.

The best way to fix metadata schema violations is to generate actionable pass/fail reports with specific remediation guidance, identifying exactly which required fields or formats need correction after task creation or updates.

Task metadata drifts from schema requirements when items are created or updated without enforcing compliance checks, leading to missing required fields, broken parent-child links, and inconsistencies that cause downstream workflow errors.