Discuss Subtask

discuss-subtask workflow (v3)

Overview

1-phase sub-workflow mapping CLAUDE.md "Stage ①.c 子任务层 — superpowers brainstorming" onto harnessed runtime (Phase v3.0-3.4 W0.3 — D-04 Stage ① Discuss 三层 + D-05 phase.invokes_tools conditional fire + Pattern A sub-workflow ship)。

| phase | id | upstream | model | capability / invokes_tools | gate | | ----- | -- | -------- | ----- | -------------------------- | ---- | | 1 | 01-brainstorm | superpowers | opus | {{ capabilities.superpowers-brainstorming.cmd }} + conditional invokes_tools[grill-with-docs, grill-me] | gate: judgments.subtask-gate.brainstorming.fires |

Capability refs

Sister workflows/capabilities.yaml entries:

• superpowers-brainstorming — Bucket 4 (impl: superpowers, cmd: superpowers:brainstorming)
• grill-with-docs — Bucket 1 mattpocock (impl: mattpocock-skills, cmd: /grill-with-docs)
• grill-me — Bucket 1 mattpocock (impl: mattpocock-skills, cmd: /grill-me)

Gate ref

Sister workflows/judgments/subtask-gate.yaml:

• brainstorming.fires — subtask.approaches >= 2 or subtask.core_algorithm == true or subtask.has_api_contract == true or subtask.error_cost == 'high'

Conditional tool invocation (D-05 invokes_tools)

• phase.spec_ambiguous == true → fire grill-with-docs
• phase.spec_ambiguous == true AND phase.no_docs == true → fire grill-me

Invocation

• Slash command: /discuss-subtask (after harnessed setup)

Routing rules

跳过条件 (sister CLAUDE.md "子任务层 ❌ 跳过"):

• 常规 CRUD / 跟现有模式一致
• 单一明显实现 (< 20 行 / 一个文件)
• 标准库直接调用
• 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 the execution stages.

1. 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

1. For each layer that fires, hold the dialogue with the user (use AskUserQuestion for option-style decisions) and lock every open decision.
2. Transparent-skip layers that don't fire — state which were skipped and why.
3. 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-05 phase.invokes_tools conditional fire (NEW v3)
• workflows/capabilities.yaml — superpowers-brainstorming / grill-with-docs / grill-me
• workflows/judgments/subtask-gate.yaml — brainstorming trigger
• workflows/defaults.yaml — ralphmaxiterations.discuss-subtask.* values (W2.2 backfill)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: easyinplay
• Source: easyinplay/harnessed
• License: Apache-2.0
• Homepage: https://harnessed.cc/

Install and usage instructions live in the source repository linked above.