Auto

verify master orchestrator (v3)

Overview

4-stage cadence Stage ④ master orchestrator delegating to 7 sub-workflows (bundled Verify-stage cadence — 9-phase composition compressed into 7 sub delegation via stage-routing.yaml):

order/mode	sub	gate ref	mode	when fires
1 (serial)	progress	(unconditional — verify 起点)	serial	always when stage=='verify'
parallel	code-review	(unconditional — multi-agent fan-out)	parallel	always
parallel	paranoid	judgments.stage-routing.verify-paranoid-critical.fires	parallel	phase.is_critical_module == true
parallel	qa	judgments.stage-routing.verify-qa-ui.fires	parallel	phase.has_ui_changes == true
parallel	security	judgments.stage-routing.verify-security-secrets.fires	parallel	phase.has_auth_or_secrets == true
parallel	design	judgments.stage-routing.verify-design-changes.fires	parallel	phase.has_design_changes == true
parallel	multispec	judgments.stage-routing.verify-multispec-critical-release.fires	parallel	is_critical_release == true (Pattern C 4-specialist Agent Team)
99 (serial)	simplify	(unconditional — 末尾 tail)	serial	always — code-simplifier 末尾移除重复 / 多余逻辑

Engine runtime per T3.5.W0.1 runMasterOrchestrator:

• serial chain: progress (order 1) 起点 → ... → simplify (order 99) 末尾收尾
• parallel fan-out: 5 conditional sub (code-review + paranoid + qa + security + design + multispec) spawn 并发, 按 gate-eval 结果 fire-or-skip
• K9 invariant enforced: every serial mode delegate carries explicit order

Verify cadence (sister CLAUDE.md "Verify 阶段" verbatim)

1. 子任务完成后立即 /gsd-verify-work + /gsd-progress (sub progress 起点必跑串行)
2. 项目 / 大功能整体完成后:
   • 先 code-review 多 Agent 并行 (sub code-review)
   • 关键模块强制 /review Paranoid Staff Engineer (sub paranoid, gate is_critical_module)
   • 可选 /qa (sub qa, gate has_ui_changes) / /cso (sub security, gate has_auth_or_secrets) / /design-review (sub design, gate has_design_changes)
   • 关键发布 / 大重构 PR 升级 4-specialist Agent Team Pattern C (sub multispec, gate critical-release-upgrade)
   • 再 code-simplifier 末尾 (sub simplify, serial order 99)

Capability refs

Sister workflows/capabilities.yaml:

• gsd-verify-work + gsd-progress — Bucket 2 (progress sub upstream)
• code-review + code-simplifier — Bucket 1 mattpocock (code-review + simplify subs)
• gstack-review + gstack-qa + gstack-cso + gstack-design-review — Bucket 3 治理关卡 (paranoid/qa/security/design subs)
• agent-teams-create — Bucket 5 agent-platform (multispec Pattern C 4-specialist team)
• planning-with-files — Bucket 4 核心 (progress.md sink throughout)

Invocation

• Slash command: /verify (bare per ADR 0030 namespace policy D-02 LOCK after harnessed setup)

How to invoke

!harnessed checkpoint intent verify

The banner above (when present) means this invocation is REGISTERED with the engine (an intent marker) — not yet compliant: steps 2-3 below seed the ledger, and a per-turn <workflow-intent> reminder persists until they run.

The numbered sequence below is the state machine — execute it step by step with Bash. Do NOT improvise an equivalent flow from the Overview above: freelancing bypasses the engine (no per-sub ledger, no evidence guard, no recovery). harnessed is the orchestration brain (harnessed gates says which subs fire, harnessed prompt gives each spawn-ready prompt, harnessed checkpoint records the ledger); YOU spawn with CC-native Task / Agent tools.

Do NOT pipe to harnessed run verify — that is the CI/headless path (in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs inside Claude Code).

1. If the clarification criteria fire for "$ARGUMENTS" (≥2 approaches / core algorithm / API contract / high error cost), clarify interactively in THIS session first (AskUserQuestion) and lock decisions; otherwise transparent-skip. Produce a locked spec.
2. Bash: harnessed gates verify --task "<locked spec>" --skip-sub clarify → parse the JSON {fire, skip, parallelism}. This is the plan SoT (no spawn). Keep the verbatim JSON.
3. Bash: harnessed checkpoint start verify --plan '<the verbatim gates JSON from step 2>' → seeds the per-sub ledger so harnessed status --recover can re-orient you after compaction.
4. If parallelism.escalate_to_teams === true: read ~/.claude/rules/agent-teams.md, then drive the fired subs as an Agent Team (TeamCreate → Agent(name, team_name, …) per sub with its harnessed prompt <sub> prompt → coordinate via SendMessage → SendMessage shutdown_request + TeamDelete). Still checkpoint each sub (complete / fail) as below.
5. Otherwise, for each fired sub in order (serial subs sequentially, parallel subs concurrently):
   • If the entry has is_master: true (a stage master — e.g. /auto firing plan/task/verify): do NOT prompt+spawn it. RECURSE: run that master’s own harnessed gates <sub> --task "<spec>" --skip-sub clarify → harnessed checkpoint start <sub> --plan '<json>' → repeat this loop for ITS fired subs.
   • Else (leaf sub): a. Bash: harnessed prompt <sub> --task "<spec>" --json → parse {prompt, max_iterations, model}. b. Spawn a CC-native subagent (Task / Agent tool) with that prompt + model, wrapped in the ralph-loop plugin: /ralph-loop "<prompt>" --max-iterations <max_iterations> --completion-promise "COMPLETE". If the plugin is absent, use the native goal gate instead (Claude Code 2.1.139+ / Codex): /goal "this subtask is delivered: the subagent's final output contains verbatim <promise>COMPLETE</promise>; or stop after <max_iterations> turns" then spawn the subagent and let the goal evaluator drive re-spawns until it clears. If /goal is unavailable too, self-loop: spawn → check output for <promise>COMPLETE</promise> → re-spawn with prior output appended (up to max_iterations). Set the goal only at the leaf subtask level — /goal is single-slot per session and a nested goal overwrites the outer one. c. If the output contains STATUS: NEEDS_CLARIFICATION + questions: STOP, relay them verbatim via AskUserQuestion, append the answers to the spec, then re-spawn the same sub. d. On <promise>COMPLETE</promise>: Bash harnessed checkpoint complete <sub> --summary "<one-line>". The evidence guard runs here (fail-CLOSED): if a declared artifacts_expected file is missing it exits non-zero — re-spawn to produce it, or pass --force only to deliberately override. e. If the sub cannot reach COMPLETE (max_iterations exhausted / unrecoverable error): Bash harnessed checkpoint fail <sub> --summary "<why>", then STOP and report to the user.
6. After all fired subs are done (or recorded failed), Bash harnessed status --recover to confirm the ledger and report a per-sub fired/skipped/done/failed summary to the user.

If you lose context (compaction / resume): run harnessed status --recover first — it reads the ledger and prints "you are here, this is next" so you resume at the first pending sub instead of restarting. If the ledger is empty, re-run steps 2-3.

<!-- harnessed-generated:v4.9.3 -->

References

• D-01 master orchestrator delegation pattern
• D-02 bare slash cmd convention (ADR 0030 namespace policy LOCK)
• D-12 gstack 治理关卡 ref (paranoid / qa / security / design subs)
• workflows/judgments/parallelism-gate.yaml — Pattern C 多维度审查 (multispec sub 4-specialist 互相质询)
• workflows/judgments/stage-routing.yaml — verify-* 6 triggers (7 sub delegation)
• workflows/verify/{progress,code-review,paranoid,qa,security,design,simplify,multispec}/workflow.yaml — 8 sub-workflow Phase 3.4 SHIPPED