Verify Validate Phase

verify-validate-phase workflow (v3)

Overview

1-phase sub-workflow auditing requirement→test coverage gaps (v13.0 P43 upstream re-sync — D-04 Stage ④ Verify conditional sub + GSD validate-phase wire)。回溯审计 phase 完成后的 requirement→test 覆盖缺口,为未覆盖 requirement 生成测试 (gsd-nyquist-auditor agent), 补 TDD 前向写测试之外的后向查漏。

Per-phase config loads from workflows/verify/validate-phase/workflow.yaml; engine 4-level gate resolver evaluates phase.requires_coverage_audit == true via expr-eval — true 则 invoke GSD /gsd-validate-phase (Nyquist 覆盖审计 → VALIDATION.md), false 则 skip。

Capability refs

Sister workflows/capabilities.yaml entries:

• gsd-validate-phase — Bucket 2 special-purpose (impl: gsd, cmd: /gsd-validate-phase, fires_when: requires_coverage_audit)

Gate ref

Sister workflows/judgments/stage-routing.yaml:

• verify-validate-phase-coverage.fires — phase.stage == 'verify' and phase.requires_coverage_audit == true

How to invoke

!harnessed checkpoint intent verify-validate-phase

The banner above (when present) means this invocation is REGISTERED with the engine (an intent marker) — not yet compliant: the steps below (prompt → spawn → checkpoint complete) resolve it, and a per-turn <workflow-intent> reminder persists until they run.

The numbered sequence below is the state machine — execute it with Bash. Do NOT improvise an equivalent flow from the Overview above: freelancing bypasses the engine (no ledger, no evidence guard). harnessed gives you the spawn-ready prompt; YOU spawn the subagent with a CC-native Task / Agent tool (keeps the session responsive + lets clarification round-trips reach the user).

Do NOT pipe to harnessed run verify-validate-phase — that is the CI/headless path (in-process SDK spawn that blocks the session inside Claude Code).

1. Bash: harnessed prompt verify-validate-phase --task "$ARGUMENTS" --json → parse {prompt, max_iterations, model}.
2. Spawn a CC-native subagent (Task / Agent tool) with that prompt and model, then drive delivery with harnessed's own completion gate:
   • on return, write the subagent's final output to a file and run harnessed checkpoint complete verify-validate-phase --result-file <path> — it is fail-closed on the declared artifacts, the TDD boundary, and the verbatim <promise>COMPLETE</promise>.
   • if it blocks, run harnessed checkpoint fail verify-validate-phase --failing-tests <n> to record the attempt; it prints BUDGET-EXHAUSTED / NO-PROGRESS / BREAK-LOOP when a stop condition is reached.
   • respawn ONLY while none of those three has fired. Any one of them means stop: re-scope the subtask, fix the blocker, or escalate to the user. Never respawn past a stop directive.
3. If the output contains STATUS: NEEDS_CLARIFICATION + a question list: STOP, relay them verbatim via AskUserQuestion, append the answers to the spec, then re-spawn the same sub.
4. On <promise>COMPLETE</promise>: write the subagent’s final output to a file, then Bash harnessed checkpoint complete verify-validate-phase --result-file <path> --summary "<one-line>". Fail-CLOSED — it blocks unless every declared artifacts_expected file exists, the TDD boundary passes (non-empty evidence / both the red and green sides present / the test file was not deleted), and the result carries a verbatim <promise>COMPLETE</promise> (or a structured COMPLETE status). --result <text> is the inline variant; --result-file wins and is quoting-safe on Windows. --force records an audited override (evidence_status=overridden) — it does not silently pass.
5. If the complete gate blocked: Bash harnessed checkpoint fail verify-validate-phase --failing-tests <n> to record the attempt. It prints BUDGET-EXHAUSTED / NO-PROGRESS / BREAK-LOOP once a stop condition is reached. Respawn ONLY while none of those three has fired; any one of them means STOP — re-scope the subtask, fix the blocker, or escalate to the user.

References

• D-04 Stage ④ Verify conditional sub 分解
• v13.0 P43 upstream re-sync — GSD validate-phase wire (Nyquist 覆盖后向查漏, TDD 前向之外)
• workflows/capabilities.yaml — gsd-validate-phase
• workflows/judgments/stage-routing.yaml — verify-validate-phase-coverage trigger
• workflows/verify/eval-review/workflow.yaml — sister conditional-sub pattern (v13.0 P42)