auto

Topics in the source

• auto super-master orchestrator (v3.2.0 enhanced)
• Overview
• Default behavior
• Optional flag
• When to use /auto vs 4 stage-master 手动
• Capability refs
• Invocation
• How to invoke

v3.2.0 NEW — 6-stage cadence (research conditional → discuss → plan → task → verify → retro mandatory), sister 4 stage-master /discuss /plan /task /verify 独立 invoke 仍 work; /auto 是 opt-in 一行命令 chain。 | order | sub | gate ref | mode | when fires | | ----- | --- | -------- | ---- | ---------- | | 0 | research | judgments.stage-routing.auto-research-unclear.fires | serial | userunderstandingunclear == true (Phase 0.5 prompt n) | | 1 | discuss | (unconditional — 4-stage chain 起点) | serial | always | | 2 | plan | (unconditional — stage 2) | serial | always | | 3 | task | (unconditional — stage 3) | serial | always | | 4 | verify | (unconditional — stage 4 收尾) | serial | always | | 5 | retro | (unconditional — auto mode mandatory) | serial | always | Engine runtime spawns 6 sub workflow.yaml via runMasterOrchestrator per T3.5.W0.1 — recursive 一层抽象 (super-master → stage-master OR standalone → sub-workflow): top-level invoke /auto → load workflows/auto/workflow.yaml → runAutoPreFlight hook pre-flight Phase 0: assessComplexity(taskDescription) → small/medium auto continue; large → prompt user 切 --staged (y) OR abort 建议手动 (n) pre-flight Phase 0.5: promptUserUnderstanding() → y skip research;

This is an excerpt. Refer to the complete source and its current requirements.