discuss-phase

# discuss-phase workflow (v3) ## Overview 2-phase sub-workflow mapping CLAUDE.md "Stage ①.b Phase 层 — GSD /gsd-discuss-phase 灰色澄清" onto harnessed runtime (Phase v3.0-3.4 W0.2 — D-04 Stage ① Discuss 三层 + Pattern A sub-workflow ship)。 | phase | id | upstream | model | capability / invokes | gate / artifacts | | ----- | -- | -------- | ----- | -------------------- | ---------------- | | 1 | `01-gsd-discuss` | gsd | sonnet | `{{ capabilities.gsd-discuss-phase.cmd }}` | `gate: judgments.phase-gate.gsd-discuss-phase.fires` | | 2 | `02-persist` | planning-with-files | haiku | `{{ capabilities.planning-with-files.cmd }}` + `invokes: /plan` | `artifacts_expected: [findings.md, knowledge.md]` | ## Capability refs Sister `workflows/capabilities.yaml` entries: - `gsd-discuss-phase` — Bucket 2 (impl: gsd, cmd: /gsd-discuss-phase) - `planning-with-files` — Bucket 4 (impl: claude-code-plugin, cmd: /plan) ## Gate refs Sister `workflows/judgments/phase-gate.yaml`: - `gsd-discuss-phase.fires` — `phase.open_decisions >= 2 or phase.has_cross_phase_data_flow == true or phase.scope_days > 1` ## Invocation - Slash command: `/discuss-phase <num>` (after `harnessed setup`) ## Routing rules 跳过条件 (sister CLAUDE.md "Phase 层 ❌ 跳过"): - 单一明确子任务 - 跟前 phase 同 module 同 pattern - < 1 天工作量 - bug 修复且已有最小复现 ## 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 ...