task

原文涵盖的主题

• task master orchestrator (v3)
• Overview
• completion gate orthogonal wrapper (D-10)
• Capability refs
• Invocation
• How to invoke
• References

4-stage cadence Stage ③ master orchestrator delegating to 4 sequential sub-workflows per subtask (bundled Execute-stage cadence + karpathy 心法 always-on): | order | sub | gate ref | mode | when fires | | ----- | --- | -------- | ---- | ---------- | | 1 | clarify | judgments.subtask-gate.brainstorming.fires | serial | approaches ≥ 2 / corealgorithm / hasapicontract / errorcost=high | | 2 | code | (unconditional — karpathy 心法 always-on + mattpocock conditional route) | serial | always | | 3 | test | judgments.tdd-gate.tdd-strongly-suggested.fires | serial | 核心业务 / 算法 / 数据处理 / 回归 risk / reliability (6 fireswhen OR-chain) | | 4 | deliver | (unconditional — completion gate COMPLETE wrapper) | serial | always | Engine runtime spawns 4 sub-workflow phases sequentially via runMasterOrchestrator per T3.5.W0.1 — clarify → code → test → deliver。K9 invariant enforced: every serial mode delegate carries explicit order。Each subtask 入口走一次此 master orchestrator。 完成闸门是正交 wrapper, 套在 deliver sub 的 01-deliver phase 外层保 completion-promise verbatim "COMPLETE" (R20.10)。任何执行单元 (subagent / team / 主 session) 都可外层套它 保 completion-promise (bundled subagent vs {{ host.team.attributive }} routing — orthogonal wra

这里只展示节选，请以完整原文和当前要求为准。