verifying-task-templates

To verify YAML task templates against Unity prefabs, place your templates in the Assets/InfiniteCorridorTask/Configurations directory and run the verification process. It compares template fields like cue mappings and trigger types against pre-baked values and actual prefab state.

A YAML task template may not match the Unity prefab configuration due to stale data or incorrect template entries. This Skill flags inconsistencies in zone ranges and cue mappings, guiding you to compare against actual prefab files to identify the exact discrepancy source.

The discrepancy diagnosis workflow enforces reading and comparing actual prefab files when mismatches are detected. It validates YAML task templates against pre-baked values from EXPECTED_VALUES.md and performs Step 2 validation against actual prefab files to identify stale data or incorrect templates.

Yes, you can use this Skill to validate cue mappings, zone ranges, and trigger types for VR corridor task templates. It targets verification workflows specifically for the Infinite Corridor project, ensuring YAML configurations align with the Unity scene setup.

Yes, EXPECTED_VALUES.md is required because the verification enforces the use of pre-baked values from this file. It serves as the baseline to compare YAML task template fields against before performing deeper Step 2 validation against actual Unity prefab files.