quest-verify

Automate phase verification by running a command that reads goals from PHASES.md and PLAN.md, spawns a subagent to validate prerequisites, and emits status events. It loops through PASS or FAIL paths until the phase succeeds or hits a human checkpoint.

Automated phase validation confirms that a specific execution phase was completed correctly against planned goals. It prevents progress drift by applying per-phase validation, retry logic, and state updates across codebases.

Yes, you need PLAN.md and PHASES.md files to verify quest phases. The verification process reads phase goals and tasks directly from these files to confirm expected outcomes and validate prerequisites.

When verification fails, retry logic triggers a phase_retrying event and loops the workflow to attempt execution again. The system applies state updates and continues looping until success or a human checkpoint is reached.

Yes, you can use human checkpoints during automated phase validation. The looping workflow automatically pauses and raises a checkpoint when needed, allowing manual intervention before advancing through phases.

During quest QA workflows, the system emits status events like phase_verified and phase_retrying. These events surface phase status and enable downstream automation to react to success or retry states.