discusslisted

# discuss master orchestrator (v3) ## Overview 4-stage cadence Stage ① master orchestrator delegating to 3 independent sub-workflows (bundled 3-tier independent clarification: strategic / phase / subtask): | sub | gate ref | mode | when fires | | --- | -------- | ---- | ---------- | | `strategic` | `judgments.stage-routing.discuss-strategic-delegate.fires` | parallel | new_project / new_milestone / new_feature / is_major_release | | `phase` | `judgments.stage-routing.discuss-phase-delegate.fires` | parallel | open_decisions ≥ 2 / cross_phase_data_flow / scope_days > 1 | | `subtask` | `judgments.stage-routing.discuss-subtask-delegate.fires` | parallel | approaches ≥ 2 / core_algorithm / has_api_contract / error_cost=high | Engine runtime spawns 3 sub-workflow phases via `runMasterOrchestrator` per T3.5.W0.1 (sister sub-workflow `runWorkflow` SDK pattern, parallel fan-out via subagent default — Path A `query()` parallel OR Path B sub-shell fallback per T3.5.W2.1 dogfood cycle decision LOCK)。 ## Chain-isolation 铁律 (sister CLAUDE.md "Fallback 三条铁律") - 拿不准 → 倾向跳过, 但在响应里**透明声明**: "这次跳过了 X, 因为 Y。如果你认为需要请明说" - 用户明示 → 覆盖判据 (用户说 "先 brainstorm" / "跑 office-hours" / "讨论一下" 时无条件激活) - **链式互不前置**: 跳过战略层 ≠ 必须跳过 phase 层; 每层独立判断 (防止 "上层没跑下层不敢跑" 的死板) ## Capability refs Sister `workflows/capabilities.yaml`: - `planning-with-files` — Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan, discuss sink findings.md) - sub `strategic` upstream → `gstack-office-hours` + `gstack-plan-ceo