plan
Turn a settled discussion into an executable plan — lock the architecture for complex work first, then persist it to task_plan.md.
原文 · 译文尚未补齐适用对象：对象待分类。自动收录 · 待核查。
原作者说明节选
从固定版本的 SKILL.md 提取，保留原文语言。以下内容属于作者说明，本站尚未验证安装、兼容或运行结果。
查看英文原文
原文涵盖的主题
- plan master orchestrator (v3)
- Overview
- Capability refs
- Routing rules (sister CLAUDE.md "Plan 阶段")
- Invocation
- How to invoke
- References
4-stage cadence Stage ② master orchestrator delegating to 2 sequential sub-workflows (bundled Plan-stage cadence + D-06 planning-with-files cross-cutting tool): | order | sub | gate ref | mode | when fires | | ----- | --- | -------- | ---- | ---------- | | 1 | architecture | judgments.stage-routing.plan-architecture-delegate.fires | serial | phase.iscomplexarchitecture == true | | 2 | phase | (unconditional — plan-phase always fires when stage=='plan') | serial | always | Engine runtime spawns 2 sub-workflow phases sequentially via runMasterOrchestrator per T3.5.W0.1 — order 1 (architecture conditional) MUST complete before order 2 (phase unconditional, GSD plan-phase + planning-with-files /plan taskplan.md 持久化)。K9 invariant enforced: every serial mode delegate carries explicit order。 Sister workflows/capabilities.yaml: planning-with-files — Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan) plan-eng-review — Bucket 7 gstack 33 optional (impl: gstack, cmd: /plan-eng-review) gsd-plan-phase — Bucket 2 special-purpose (impl: gsd, cmd: /gsd-plan-phase) sub architecture upstream → plan-eng-review sub phase upstream → gsd-plan-phase + planning-with-files 复杂架构必须先跑 /plan-eng-rev
这里只展示节选，请以完整原文和当前要求为准。
- 来源仓库
- easyinplay/harnessed
- 源文件
- workflows/plan/auto/SKILL.md
- 固定版本
- f272b6e2bcc05793dde6ad7146da602381fe1351
来源与内容状态
本条为自动发现的元数据，尚未完成人工文档核查；适用性与运行结果待核查。
原作者：easyinplay/harnessed · 原作者仓库元数据。文档核查：未核查。最近来源检查：2026-11-10T08:01:58.133Z。
分类由名称、说明与路径规则生成，分类不代表已核实适配。
许可与权利归属
Apache-2.0。第三方内容及版权归原作者，使用条件以原文为准。
许可原文 ↗本站没有因同步、复制或用户自报成功而将资源标为运行验证通过。
限制与注意事项
- 元数据收录不代表本站已经安装、适配、实测或进行安全审查。