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