Menu
Plan-feature workflow phase 04 stub — orchestration phase planning (mock, Phase 3.3+ dogfood 时换真 gsd spawn)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Super-master orchestrator — 一行命令跑完整 6-stage feature 开发流 (research conditional → discuss → plan → task → verify → retro mandatory), 适合 trivial / well-defined feature OR 你 想 hands-off。每 stage 内部仍 fan-out sub-workflow per 现有 stage-master orchestrator pattern。 v3.2.0 强化:Phase 0 AI 1-shot complexity assessment + Phase 0.5 understanding check prompt + Phase 5 `/retro` mandatory。 schema_version: harnessed.workflow.v3 with delegates_to (6 sub: research conditional order 0 + 4 stage-master order 1-4 + retro mandatory order 5) + disciplines_applied (6 default) + tools_available (agent-teams-create + planning-with-files)。Fail-fast default; opt-in `--staged` flag 重现 stage gate UX (每 stage 完停 user review)。 Triggered by slash command `/auto` (bare per ADR 0030 namespace policy D-02 LOCK) after `harnessed setup`.
Stage ① Discuss master orchestrator — 3 sub-workflow parallel gate-eval (chain-isolation 铁律)。 战略层 / Phase 层 / 子任务层独立判断 gate, 可能 3 个全跑 / 1-2 个 / 全跳 + 透明声明。 schema_version: harnessed.workflow.v3 with delegates_to (3 sub: strategic + phase + subtask, mode parallel) + disciplines_applied (6 default) + tools_available (planning-with-files)。 Triggered by slash command `/discuss` (bare per ADR 0030 namespace policy D-02 LOCK) after `harnessed setup`.
多源调研 workflow — Tavily/Exa/ctx7 多源 fan-out + GSD discuss synth aggregate; harnessed v2.0 NEW per R20.7 (Stage ① Discuss 独立 call); schema bumped to harnessed.workflow.v3 in Phase v3.0-3.4 W1.1 (T3.4.W1.1) with disciplines_applied [6] + tools_available [tavily-mcp, exa-mcp, ctx7, gsd-discuss-phase], phases reuse v2 verbatim. Triggered by slash command `/research` after `harnessed setup`.
Stage ②.a 架构层 plan sub-workflow — gstack /plan-eng-review (复杂架构强制治理关卡; bundled plan-stage cadence: mandatory before complex-architecture phases)。schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available [plan-eng-review] + 1 phase (01-plan-eng-review) + gate literal expr `phase.is_complex_architecture == true`。Triggered by harnessed CLI `harnessed plan-architecture --module <name>` or slash command `/plan-architecture` after `harnessed setup`.
Stage ②.b 计划层 plan sub-workflow — GSD /gsd-plan-phase Wave A research + Wave B planner + Wave C plan-checker + planning-with-files Claude Code plugin /plan 持久化 task_plan.md + progress.md (bundled Plan-stage cadence: GSD + planning-with-files)。Stage ② 铁律: dual capability (GSD orchestration + planning-with-files plugin)。schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available [gsd-plan-phase, planning-with-files] + 2 phases (01-gsd-plan + 02-persist)。Triggered by harnessed CLI `harnessed plan-phase --phase <num>` or slash command `/plan-phase` after `harnessed setup`.
Standalone post-④ Verify retrospective workflow — gstack /retro 经验教训 / 决策 / lessons 系统总结 (项目 / 里程碑结束可选, bundled milestone-close retrospective cadence) + planning-with-files RETROSPECTIVE.md 持久化 (sister Phase v2.0-2.5 RETROSPECTIVE pattern)。Capability ref retro-gstack alias suffix per Pattern A E.2 LOCK (NOT bare retro 避免 standalone workflow / capability namespace 冲突)。 schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available (retro-gstack + planning-with-files) + 2 phase (01-retro gstack invoke + 02-persist RETROSPECTIVE.md sink)。Triggered by harnessed CLI `harnessed retro --milestone <name>` or slash command `/retro` after `harnessed setup`.
| name | plan-feature-plan |
| description | Plan-feature workflow phase 04 stub — orchestration phase planning (mock, Phase 3.3+ dogfood 时换真 gsd spawn) |
| allowed-tools | ["Read","Edit","Bash"] |
Phase 3.2 D-03 WIRED reference implementation. Returns mock decision output for workflow runtime verification.
This skill stub returns a mock result to simulate phase success transition:
{
"status": "ok",
"output": "<stub for plan-feature-plan>",
"decision": "mock-approved"
}
Phase 3.3+ dogfood: replace stub with actual gsd-plan-phase spawn + decision capture.