v2-schema-reference

The v2.0 schema defines required fields, data types, and constraints for epics, stories, and tasks. It specifies both mandatory and optional fields for each item type to ensure consistent metadata structure and prevent validation errors across project workflows.

You validate epic and story metadata by checking your records against the v2.0 schema reference, which specifies required fields, data types, and constraints for each item type. This ensures consistent metadata structure and prevents validation errors across teams.

Task metadata validation fails when records do not meet the required fields, data types, or constraints defined in the v2.0 schema. Inconsistent metadata across epics, stories, and tasks leads to validation errors and miscommunication across teams.

Yes, the v2.0 schema reference serves as onboarding and documentation material for teams adopting the schema. It documents constraints, relationships, and best practices to support validation and tooling for epics, stories, and tasks.

The best way to ensure consistent metadata structure is to apply the canonical v2.0 schema reference across project workflows that create or validate metadata. This defines required and optional fields, types, and constraints for each item type.