easyinplay discuss-strategic workflow (v3)
Overview
3-phase sub-workflow mapping CLAUDE.md "Stage ①.a 战略层 — 新功能启动前强制 🔒" onto harnessed runtime (Phase v3.0-3.4 W0.1 — D-04 Stage ① Discuss 三层 + D-12 gstack 治理关卡 + Pattern A sub-workflow ship)。
| phase | id | upstream | model | capability / invokes | gate / artifacts |
|---|---|---|---|---|---|
| 1 | 01-office-hours |
gstack | opus | {{ capabilities.gstack-office-hours.cmd }} |
gate: judgments.strategic-gate.office-hours.fires |
| 2 | 02-plan-ceo-review |
gstack | opus | {{ capabilities.gstack-plan-ceo-review.cmd }} |
gate: judgments.strategic-gate.plan-ceo-review.fires |
| 3 | 03-persist |
planning-with-files | haiku | {{ capabilities.planning-with-files.cmd }} + invokes: /plan |
artifacts_expected: [findings.md] |
Capability refs
Sister workflows/capabilities.yaml entries:
gstack-office-hours— Bucket 3 治理关卡 (impl: gstack, cmd: /office-hours)gstack-plan-ceo-review— Bucket 3 治理关卡 (impl: gstack, cmd: /plan-ceo-review)planning-with-files— Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan)
Gate refs
Sister workflows/judgments/strategic-gate.yaml:
office-hours.fires—phase.type in ['new_project', 'new_milestone', 'new_feature']plan-ceo-review.fires—phase.type == 'new_project' or phase.is_major_release == true
Invocation
- Slash command:
/discuss-strategic <text>(afterharnessed setup)
Routing rules
跳过条件 (sister CLAUDE.md "战略层 ❌ 跳过"):
- bug 修复 / 技术债 / 实现细节
- scope 已在历史
.planning/或 design doc 定义 - continuing 已有 phase 的执行
- 用户已给明确 ticket / spec
How to invoke
Clarification needs real user dialogue, so run this stage directly in THIS session — do NOT spawn it, and do NOT improvise: follow these steps so the locked spec is persisted for the execution stages.
- Evaluate the clarification criteria for "$ARGUMENTS":
- Strategic — new feature / milestone / unclear business scope → gstack
/office-hours+/plan-ceo-review - Phase — ≥2 open implementation decisions / unclear cross-phase API contract → GSD
/gsd-discuss-phase - Subtask — ≥2 distinct approaches / core algorithm / API contract design / high error cost → superpowers brainstorming
- Strategic — new feature / milestone / unclear business scope → gstack
- For each layer that fires, hold the dialogue with the user (use AskUserQuestion for option-style decisions) and lock every open decision.
- Transparent-skip layers that don't fire — state which were skipped and why.
- Persist the locked decisions to
.planning/via planning-with-files (findings.md/task_plan.md).
Output: a locked spec the execution stages (/plan → /task → /verify) consume without further user input.
References
- D-04 Stage ① Discuss 三层 (战略 / phase / 子任务)
- D-12 gstack 治理关卡强制
- workflows/capabilities.yaml — gstack-office-hours / gstack-plan-ceo-review / planning-with-files
- workflows/judgments/strategic-gate.yaml — office-hours / plan-ceo-review triggers
- workflows/defaults.yaml — ralph_max_iterations.discuss-strategic.* values (W2.2 backfill)