discuss

原文涵盖的主题

• discuss master orchestrator (v3)
• Overview
• Chain-isolation 铁律 (sister CLAUDE.md "Fallback 三条铁律")
• Capability refs
• Invocation
• How to invoke
• References

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.strategic-gate.strategic-tier-delegate.fires | parallel | newproject / newmilestone / newfeature / ismajorrelease | | phase | judgments.phase-gate.gsd-discuss-phase.fires | parallel | opendecisions ≥ 2 / crossphasedataflow / scopedays > 1 / filestouched > 5 | | subtask | judgments.subtask-gate.brainstorming.fires | parallel | approaches ≥ 2 / corealgorithm / hasapicontract / errorcost=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)。 拿不准 → 倾向跳过, 但在响应里透明声明: "这次跳过了 X, 因为 Y。如果你认为需要请明说" 用户明示 → 覆盖判据 (用户说 "先 brainstorm" / "跑 office-hours" / "讨论一下" 时无条件激活) 链式互不前置: 跳过战略层 ≠ 必须跳过 phase 层; 每层独立判断 (防止 "上层没跑下层不敢跑" 的死板) Sister workflows/capabilities.yaml: planning-with-files — Bucket 4 核心 capability (impl: claude-code-p

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