builder-verification

This verification workflow enforces quality gates by managing states like verified, unverified, and skipped, blocking task completion until UI verification is successfully passed or explicitly overridden.

Handling prerequisite failures requires clear classification to differentiate between test environment setup issues and actual feature defects, which guides the appropriate fix strategy and remediation path for development tasks.

Recovering from environmental issues involves identifying conflicts like port or process conflicts and attempting automated resolution using dedicated recovery mechanisms before requesting new skills for unhandled environment issues.

You need to classify verification failures when addressing incomplete UI verification, prerequisite failures, or environmental issues, as clear classification directly guides the appropriate remediation and fix strategy for the task.

You can skip code quality verification for a specific task through an explicit override, although the workflow enforces quality gates by default and blocks progress when UI verification remains incomplete.

A task remains unverified when the workflow detects incomplete UI verification, prerequisite failures, or environmental issues, blocking progress until the verification failure is clearly classified and resolved or explicitly overridden.