By name: task-clarify
description: |
task-clarify workflow v3 — Stage ③.a 子任务澄清 sub-workflow (superpowers
brainstorm + mattpocock /grill-with-docs conditional invoke)。Per-subtask
repeat invoke 入口 — execute-task 每个 subtask 起步先走 task-clarify 评估 gate
(judgments.subtask-gate.brainstorming.fires) 是否激活 brainstorming + 条件性
fire grill-with-docs (phase.spec_ambiguous == true)。
schema_version: harnessed.workflow.v3 with disciplines_applied [6] + tools_available
[superpowers-brainstorming, grill-with-docs]. Triggered by harnessed CLI
harnessed task-clarify --task <text> or slash command /task-clarify after
harnessed setup.
trigger_phrases:
- "clarify this subtask"
- "task-clarify workflow"
- "Stage 3 clarify"
- "跑 task-clarify"
task-clarify workflow (v3)
Overview
Single-phase sub-workflow mapping the user's CLAUDE.md Stage ③.a 子任务澄清 discipline
onto the harnessed runtime, fully harnessed.workflow.v3 schema (Phase v3.0-3.4 W0
T3.4.W0.6 — D-09 L0 Discipline Substrate + D-05 conditional invokes_tools + D-04
gate ref).
| phase | id | upstream | model | capability / invokes_tools | gate |
|---|---|---|---|---|---|
| 1 | 01-brainstorm |
superpowers | sonnet | {{ capabilities.superpowers-brainstorming.cmd }} + invokes_tools: [{if: phase.spec_ambiguous, tool: grill-with-docs}] |
judgments.subtask-gate.brainstorming.fires |
Per-phase config loads from workflows/task/clarify/workflow.yaml; engine.runRouting
spawns each phase as a sub-agent via @anthropic-ai/claude-agent-sdk 0.3.142+.
Per-subtask repeat invoke pattern
task-clarify is NOT a one-shot 阶段 — execute-task master orchestrator delegates to task-clarify 每个 subtask 入口走一次 evaluate gate (subtask-gate.brainstorming .fires) 是否激活。Skip path (subtask.type in ['crud','standard_lib_call'] OR subtask.lines < 20) bypasses brainstorming entirely per CLAUDE.md "拿不准 → 倾向跳过"。
Discipline Substrate (L0 always-on)
6 disciplines (karpathy + output-style + language + operational + priority + protocols)
apply cross-cutting per D-09 L0 Discipline Substrate — workflow runtime pre-phase hook
loads discipline yaml + applies rules. Sentinel category behavioral SKIP cmd invoke;
runtime engine routes via discipline_ref ref to workflows/disciplines/<basename>.yaml.
Conditional grill-with-docs fire (D-05 invokes_tools)
Phase 01-brainstorm 条件性 fire grill-with-docs when phase.spec_ambiguous == true —
sister CLAUDE.md "Discuss / Research 阶段" mattpocock 招式按需召唤 pattern; NOT 强制
unconditional fire (D-05 invokes_tools 与 OnClause 并存, 但作用面不同 — invokes_tools
phase-level conditional tool fire NOT 决定 phase 是否走)。
How to invoke
Orchestrated CC-natively. Do NOT pipe to harnessed run task-clarify — that is the CI/headless
path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when
invoked from inside a Claude Code session).
Run the /task-clarify slash command instead (generated by harnessed setup at
~/.claude/commands/task-clarify.md). It drives the stage natively: harnessed gates → which
subs fire, harnessed prompt <sub> → each spawn-ready prompt, then a CC-native subagent
(Task / Agent tool) per fired sub, recording each outcome with harnessed checkpoint. The
full state-machine steps live in ~/.claude/commands/task-clarify.md; if that file is absent,
follow that same gates → prompt → spawn → checkpoint sequence yourself.
References
- D-09 — L0 Discipline Substrate always-on (6 disciplines)
- D-05 — phase-level
invokes_toolsconditional tool fire - D-04 —
gate4-level ref pre-resolved byjudgmentResolver - D-02 — SKILL.md
name:bare slash cmd (task-clarifyNOTtask/clarify) per ADR 0030 workflows/judgments/subtask-gate.yamltriggers.brainstormingworkflows/capabilities.yaml— superpowers-brainstorming + grill-with-docs entriesworkflows/defaults.yaml— ralph_max_iterations.task-clarify.* values (T3.4.W2.2 followup)docs/WORKFLOW.md— 4-stage workflow mermaid + Stage ③ Execute 章节