harnessed 2.0.1 → 3.0.1

package/workflows/plan/phase/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: plan-phase
+description: |
+  Stage ②.b 计划层 plan sub-workflow — GSD /gsd-plan-phase Wave A research + Wave B planner +
+  Wave C plan-checker + planning-with-files Claude Code plugin /plan 持久化 task_plan.md +
+  progress.md (sister ~/.claude/CLAUDE.md "Plan 阶段 GSD + planning-with-files")。Stage ② 铁律:
+  dual capability (GSD orchestration + planning-with-files plugin)。schema_version:
+  harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available [gsd-plan-phase,
+  planning-with-files] + 2 phases (01-gsd-plan + 02-persist)。Triggered by harnessed CLI
+  `harnessed plan-phase --phase <num>` or slash command `/plan-phase` after `harnessed setup`.
+trigger_phrases:
+  - "plan phase"
+  - "计划层 phase"
+  - "gsd plan phase"
+  - "持久化计划"
+  - "跑 plan-phase"
+---
+
+# plan-phase workflow (v3)
+
+## Overview
+
+2-phase sub-workflow mapping CLAUDE.md "Plan 阶段 — GSD + planning-with-files" onto harnessed
+runtime (Phase v3.0-3.4 W0.5 — D-04 Stage ② Plan 二层 + D-15 planning-with-files
+claude-code-plugin /plan + Pattern A sub-workflow ship)。
+
+| phase | id | upstream | model | capability / invokes | artifacts |
+| ----- | -- | -------- | ----- | -------------------- | --------- |
+| 1 | `01-gsd-plan` | gsd | sonnet | `{{ capabilities.gsd-plan-phase.cmd }}` | (Wave A research + Wave B planner + Wave C plan-checker) |
+| 2 | `02-persist` | planning-with-files | haiku | `{{ capabilities.planning-with-files.cmd }}` + `invokes: /plan` | `artifacts_expected: [task_plan.md, progress.md]` |
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` entries:
+- `gsd-plan-phase` — Bucket 2 (impl: gsd, cmd: /gsd-plan-phase)
+- `planning-with-files` — Bucket 4 (impl: claude-code-plugin, cmd: /plan;
+  plugin_path: ~/.claude/plugins/cache/planning-with-files/...; outputs:
+  task_plan.md + progress.md + findings.md)
+
+## Stage ② 铁律 — dual capability
+
+GSD `/gsd-plan-phase` orchestrate (Wave A research → Wave B planner → Wave C
+plan-checker) → planning-with-files `/plan` 持久化 (plugin 真生成 task_plan.md +
+progress.md, NOT fs.writeFile self-impl per D-15 Q-AUDIT-5a claude-code-plugin
+reframe)。
+
+## Invocation
+
+- CLI: `harnessed plan-phase --phase <num>`
+- Slash command: `/plan-phase <num>` (after `harnessed setup`)
+
+## Output artifacts
+
+- `task_plan.md` — 主任务清单 + 文件路径 + 依赖 + 验收标准
+- `progress.md` — phase 进度跟踪 + cross-session 恢复
+- (`findings.md` 由 discuss-* sub-workflow 产出, 此处不重复)
+
+## References
+
+- D-04 Stage ② Plan 二层 (架构 / 计划)
+- D-15 Q-AUDIT-5a planning-with-files claude-code-plugin reframe (NOT npm-sdk)
+- ~/.claude/CLAUDE.md "Plan 阶段 GSD + planning-with-files"
+- workflows/capabilities.yaml — gsd-plan-phase / planning-with-files (Bucket 4)
+- workflows/defaults.yaml — ralph_max_iterations.plan-phase.* values (W2.2 backfill)

package/workflows/plan/phase/workflow.yaml

@@ -0,0 +1,37 @@
+# workflows/plan/phase/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.5
+#
+# Stage ②.b 计划层 sub-workflow — GSD /gsd-plan-phase Wave A research + Wave B planner +
+# Wave C plan-checker + planning-with-files /plan 持久化 task_plan.md (sister
+# ~/.claude/CLAUDE.md "Plan 阶段 GSD + planning-with-files")。Stage ② 铁律: dual capability
+# (gsd-plan-phase + planning-with-files /plan invokes)。
+#
+# Sister refs:
+#   - workflows/capabilities.yaml — gsd-plan-phase / planning-with-files
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 sub-stage example verbatim
+
+schema_version: harnessed.workflow.v3
+workflow: plan-phase
+description: |
+  Stage ②.b 计划层 — GSD /gsd-plan-phase Wave A research + Wave B planner + Wave C plan-checker
+  + planning-with-files /plan 持久化 task_plan.md + progress.md (sister CLAUDE.md "Plan 阶段
+  GSD + planning-with-files")。Stage ② 铁律: dual capability (GSD orchestration + planning-with-files
+  Claude Code plugin /plan invocation)。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [gsd-plan-phase, planning-with-files]
+
+phases:
+  - id: 01-gsd-plan
+    name: gsd-plan-phase (Wave A research + Wave B planner + Wave C plan-checker)
+    upstream: gsd
+    capability: '{{ capabilities.gsd-plan-phase.cmd }}'
+    model: sonnet
+    max_iterations: '{{ defaults.ralph_max_iterations.plan-phase.01-gsd-plan }}'
+
+  - id: 02-persist
+    name: planning-with-files /plan (task_plan.md + progress.md 持久化)
+    upstream: planning-with-files
+    capability: '{{ capabilities.planning-with-files.cmd }}'
+    invokes: '/plan'
+    model: haiku
+    artifacts_expected: [task_plan.md, progress.md]

package/workflows/research/SKILL.md

@@ -1,12 +1,16 @@
 ---
 name: research
-description: 多源调研 workflow — Tavily/Exa/ctx7 多源 fan-out + GSD discuss synth aggregate; harnessed v2.0 NEW per R20.7 (Stage ① Discuss 独立 call). Triggered by harnessed CLI `harnessed research --topic <text>` or slash command `/research` after `harnessed setup`.
+description: 多源调研 workflow — Tavily/Exa/ctx7 多源 fan-out + GSD discuss synth aggregate; harnessed v2.0 NEW per R20.7 (Stage ① Discuss 独立 call); schema bumped to harnessed.workflow.v3 in Phase v3.0-3.4 W1.1 (T3.4.W1.1) with disciplines_applied [6] + tools_available [tavily-mcp, exa-mcp, ctx7, gsd-discuss-phase], phases reuse v2 verbatim. Triggered by harnessed CLI `harnessed research --topic <text>` or slash command `/research` after `harnessed setup`.
 preamble-tier: 2
+schema_version: harnessed.workflow.v3
 ---
 
 # research workflow
 
-Multi-source research workflow shipped with harnessed v2.0 (Stage ① Discuss).
+Multi-source research workflow shipped with harnessed v2.0 (Stage ① Discuss);
+`workflow.yaml` schema bumped to `harnessed.workflow.v3` in Phase v3.0-3.4 W1.1
+(T3.4.W1.1 — D-09 L0 Discipline Substrate + D-05 tools_available cross-validate);
+phases content (01-fan-out + 02-synth) verbatim reused from v2 SHIPPED unchanged.
 
 ## Phases (2)
 

package/workflows/research/workflow.yaml

@@ -1,9 +1,40 @@
-schema_version: harnessed.workflow.v2
+# workflows/research/workflow.yaml — Phase v3.0-3.4 W1 T3.4.W1.1
+# (v2 19L → v3 ~25L schema bump per RESEARCH-workflows Area 2 Standalone section)
+#
+# Standalone Stage ① alternate — 多源调研 Tavily MCP (默认关键词) + Exa MCP (描述式 / 学术)
+# + ctx7 CLI (库 API 文档) fan-out + GSD discuss synth aggregate; sister
+# ~/.claude/rules/web-search.md + context7.md routing 机器化 per R20.7 + D-08。
+#
+# v2 → v3 字段 delta (W1.1 schema bump scope):
+#   BUMP `schema_version: harnessed.workflow.v3`              (17th surface — sister Phase 3.3 W0.11)
+#   ADD  `disciplines_applied: [6 basename]`                  (D-09 L0 Discipline Substrate)
+#   ADD  `tools_available: [tavily-mcp, exa-mcp, ctx7, gsd-discuss-phase]`
+#                                                              (D-05 + Contract C1 cross-validate)
+#   KEEP phases verbatim (01-fan-out + 02-synth) — phases 内容 reuse v2 SHIPPED
+#                                                              (per PLAN L455 "phases 内容 reuse v2")
+#
+# Sister refs:
+#   - .planning/phase-v3.0-3.2/PLAN.md L450-457 (T3.4.W1.1 spec verbatim)
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 Standalone research v3 example
+#   - workflows/capabilities.yaml tavily-mcp + exa-mcp + ctx7 + gsd-discuss-phase
+#     (Phase 2.3 W0.1 SHIPPED)
+#   - workflows/disciplines/{karpathy,output-style,language,operational,priority,protocols}.yaml
+#     (Phase 3.3 W0.4 SHIPPED, L0 substrate)
+#   - src/workflow/schema/workflow.ts WorkflowSchemaV3 (Phase 3.3 W0.5 SHIPPED 122L)
+
+schema_version: harnessed.workflow.v3
 workflow: research
-description: 多源调研 workflow — Tavily MCP (默认关键词) + Exa MCP (描述式/学术) + ctx7 CLI (库 API 文档) fan-out + GSD discuss synth aggregate; sister ~/.claude/rules/web-search.md + context7.md routing 机器化 per R20.7 + D-08
+description: |
+  Standalone Stage ① alternate — 多源调研 Tavily MCP (默认关键词) + Exa MCP (描述式 /
+  学术) + ctx7 CLI (库 API 文档) fan-out + GSD discuss synth aggregate; sister
+  ~/.claude/rules/web-search.md + context7.md routing 机器化 per R20.7 + D-08。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [tavily-mcp, exa-mcp, ctx7, gsd-discuss-phase]
 
 phases:
-  # 01-fan-out: 多源 fan-out — Tavily / Exa / ctx7 各源并行查询 (subagent fan-out per CLAUDE.md 子任务并行执行机制); generic shape — workflow engine 按 capability route 触发 3 source sequentially
+  # 01-fan-out: 多源 fan-out — Tavily / Exa / ctx7 各源并行查询 (subagent fan-out per CLAUDE.md
+  # 子任务并行执行机制); generic shape — workflow engine 按 capability route 触发 3 source sequentially
   - id: 01-fan-out
     upstream: web-search
     model: sonnet

package/workflows/retro/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: retro
+description: |
+  Standalone post-④ Verify retrospective workflow — gstack /retro 经验教训 / 决策 / lessons
+  系统总结 (项目 / 里程碑结束可选, sister ~/.claude/CLAUDE.md "项目 / 里程碑结束: 可选跑
+  /retro 总结" verbatim) + planning-with-files RETROSPECTIVE.md 持久化 (sister Phase
+  v2.0-2.5 RETROSPECTIVE pattern)。Capability ref retro-gstack alias suffix per Pattern A
+  E.2 LOCK (NOT bare retro 避免 standalone workflow / capability namespace 冲突)。
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (retro-gstack + planning-with-files) + 2 phase (01-retro gstack invoke + 02-persist
+  RETROSPECTIVE.md sink)。Triggered by harnessed CLI `harnessed retro --milestone <name>` or
+  slash command `/retro` after `harnessed setup`.
+trigger_phrases:
+  - "项目总结"
+  - "里程碑结束"
+  - "经验教训"
+  - "retro"
+---
+
+# retro workflow (v3 NEW standalone)
+
+## Overview
+
+2-phase standalone workflow mapping CLAUDE.md "项目 / 里程碑结束: 可选跑 /retro 总结" onto
+harnessed runtime (Phase v3.0-3.4 W1.2 — D-04 NEW v3 standalone workflow + Pattern A E.2
+retro-gstack alias suffix LOCK)。
+
+| phase | id | upstream | model | capability / invokes | artifacts |
+| ----- | -- | -------- | ----- | -------------------- | --------- |
+| 1 | `01-retro` | gstack | opus | `{{ capabilities.retro-gstack.cmd }}` | gstack /retro 经验教训系统总结 |
+| 2 | `02-persist` | planning-with-files | haiku | `{{ capabilities.planning-with-files.cmd }}` + `invokes: /plan` | `artifacts_expected: [RETROSPECTIVE.md]` |
+
+Per-phase config loads from `workflows/retro/workflow.yaml`; engine spawns phase 01 gstack
+`/retro` (alias resolve to retro-gstack carrier per capabilities.yaml entry), phase 02
+planning-with-files `/plan` invoke 持久化 RETROSPECTIVE.md sink。
+
+## Capability refs (Pattern A E.2 LOCK)
+
+Sister `workflows/capabilities.yaml` entries:
+- `retro-gstack` — Bucket 7 gstack optional **alias suffix** per Pattern A E.2 LOCK
+  (impl: gstack, cmd: /retro, aliases to harnessed-bundled /retro, fires_when: is_milestone_close)
+  — 解决 namespace 冲突 (NOT bare `retro` capability 因 standalone workflow 已占 retro 名)
+- `planning-with-files` — Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan)
+
+## Routing rules (sister CLAUDE.md "项目 / 里程碑结束")
+
+- ✅ **触发**: 项目结束 / 里程碑结束 / 用户明示 "复盘 / retro / lessons learned"
+- ❌ **跳过**: 日常 PR / 单 phase 完成 (常规 verify-progress 已够用)
+
+## CLI invocation
+
+```bash
+# Dry-run preview — arbitrate-only, never spawns SDK.
+harnessed retro --milestone <name> --dry-run --non-interactive
+
+# Apply path — real SDK spawn + 2-phase serial (gstack /retro → planning-with-files RETROSPECTIVE.md sink).
+harnessed retro --milestone <name> --apply
+```
+
+## References
+
+- D-04 NEW v3 standalone workflow (research v3 bump + retro NEW)
+- Pattern A E.2 LOCK — 2 alias suffix `-gstack` 解决 namespace 冲突 (retro-gstack + investigate-gstack)
+- Pattern A reconcile D.2 — gstack 30 optional naming bare 例外
+- ~/.claude/CLAUDE.md "项目 / 里程碑结束: 可选跑 /retro 总结" verbatim
+- workflows/capabilities.yaml — retro-gstack (alias suffix) + planning-with-files
+- workflows/defaults.yaml — ralph_max_iterations.retro.* values (W2.2 backfill)
+- sister Phase v2.0-2.5 RETROSPECTIVE.md sink pattern

package/workflows/retro/workflow.yaml

@@ -0,0 +1,40 @@
+# workflows/retro/workflow.yaml — Phase v3.0-3.4 W1 T3.4.W1.2 NEW
+#
+# Standalone post-④ Verify — gstack /retro 经验教训总结 (项目 / 里程碑结束可选,
+# sister ~/.claude/CLAUDE.md "项目 / 里程碑结束: 可选跑 /retro 总结" verbatim)。
+# Sink RETROSPECTIVE.md (sister Phase v2.0-2.5 RETROSPECTIVE pattern)。
+#
+# Sister refs:
+#   - ~/.claude/CLAUDE.md "项目 / 里程碑结束: 可选跑 /retro 总结" verbatim
+#   - workflows/capabilities.yaml — retro-gstack (Bucket 7 gstack optional alias suffix per
+#     Pattern A E.2 LOCK, 解决 namespace 冲突 — retro carrier 自带 gstack 字符串 NOT prefix policy)
+#   - workflows/capabilities.yaml — planning-with-files (Bucket 4 核心 capability /plan)
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 Standalone retro example verbatim
+#   - Pattern A reconcile D.2 (gstack 30 optional naming 2 alias suffix retro-gstack / investigate-gstack)
+
+schema_version: harnessed.workflow.v3
+workflow: retro
+description: |
+  Standalone post-④ — gstack /retro 经验教训总结 (项目 / 里程碑结束可选, sister CLAUDE.md
+  "项目 / 里程碑结束: 可选跑 /retro 总结")。Sink RETROSPECTIVE.md (sister Phase v2.0-2.5
+  RETROSPECTIVE pattern)。Capability ref retro-gstack alias suffix per Pattern A E.2 LOCK
+  (NOT bare retro 避免 standalone workflow / capability namespace 冲突)。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [retro-gstack, planning-with-files]
+
+phases:
+  - id: 01-retro
+    name: gstack-retro (经验教训 / 决策 / lessons 系统总结)
+    upstream: gstack
+    capability: '{{ capabilities.retro-gstack.cmd }}'
+    model: opus
+    max_iterations: '{{ defaults.ralph_max_iterations.retro.01-retro }}'
+
+  - id: 02-persist
+    name: planning-with-files RETROSPECTIVE.md (经验教训持久化)
+    upstream: planning-with-files
+    capability: '{{ capabilities.planning-with-files.cmd }}'
+    invokes: '/plan'
+    model: haiku
+    artifacts_expected: [RETROSPECTIVE.md]

package/workflows/task/auto/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: task
+description: |
+  Stage ③ Task master orchestrator — 串行 invoke 4 sub per subtask (clarify → code → test → deliver)。
+  ralph-loop COMPLETE wrapper 在 deliver phase 内 (D-10 orthogonal wrapper)。tdd-gate conditional
+  fire on test sub。schema_version: harnessed.workflow.v3 with delegates_to (4 sub: clarify order 1
+  conditional + code order 2 + test order 3 conditional + deliver order 4) + disciplines_applied
+  (6 default) + tools_available (8 entry: superpowers-brainstorming + tdd + grill-with-docs +
+  zoom-out + improve-codebase-architecture + diagnose + ralph-loop + planning-with-files)。
+  Triggered by harnessed CLI `harnessed task --subtask <text>` or slash command `/task`
+  (bare per ADR 0030 namespace policy D-02 LOCK) after `harnessed setup`.
+trigger_phrases:
+  - "task"
+  - "子任务执行"
+  - "stage 3 execute"
+  - "ralph loop"
+  - "执行子任务"
+---
+
+# task master orchestrator (v3)
+
+## Overview
+
+4-stage cadence Stage ③ master orchestrator delegating to 4 sequential sub-workflows
+per subtask (per ~/.claude/CLAUDE.md "Execute 阶段" 节 + karpathy 心法 always-on):
+
+| order | sub | gate ref | mode | when fires |
+| ----- | --- | -------- | ---- | ---------- |
+| 1 | `clarify` | `judgments.subtask-gate.brainstorming.fires` | serial | approaches ≥ 2 / core_algorithm / has_api_contract / error_cost=high |
+| 2 | `code` | (unconditional — karpathy 心法 always-on + mattpocock conditional route) | serial | always |
+| 3 | `test` | `judgments.tdd-gate.tdd-strongly-suggested.fires` | serial | 核心业务 / 算法 / 数据处理 / 回归 risk / reliability (6 fires_when OR-chain) |
+| 4 | `deliver` | (unconditional — ralph-loop COMPLETE wrapper) | serial | always |
+
+Engine runtime spawns 4 sub-workflow phases sequentially via `runMasterOrchestrator`
+per T3.5.W0.1 — clarify → code → test → deliver。K9 invariant enforced: every serial
+mode delegate carries explicit `order`。Each subtask 入口走一次此 master orchestrator。
+
+## ralph-loop orthogonal wrapper (D-10)
+
+ralph-loop 是正交 wrapper, 套在 deliver sub 的 01-deliver phase 外层保 completion-promise
+verbatim "COMPLETE" (R20.10)。任何执行单元 (subagent / team / 主 session) 都可外层套 ralph-loop
+保 completion-promise (sister ~/.claude/CLAUDE.md 子任务并行执行机制 "正交 wrapper")。
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml`:
+- `superpowers-brainstorming` — Bucket 4 核心 capability (sub clarify upstream)
+- `tdd` — Bucket 4 核心 capability TDD red-green-refactor (sub test upstream)
+- `grill-with-docs` — Bucket 1 mattpocock conditional invoke (clarify)
+- `zoom-out` — Bucket 1 mattpocock conditional invoke (code, unfamiliar_module)
+- `improve-codebase-architecture` — Bucket 1 mattpocock conditional invoke (code, architecture_health_audit)
+- `diagnose` — Bucket 1 mattpocock conditional invoke (code/test, bug_root_cause_unknown / test_fail)
+- `ralph-loop` — Bucket 4 核心 capability orthogonal wrapper (deliver)
+- `planning-with-files` — Bucket 4 核心 capability (code + deliver progress.md update)
+
+## Invocation
+
+- CLI: `harnessed task --subtask "<text>"`
+- Slash command: `/task <text>` (bare per ADR 0030 namespace policy D-02 LOCK after `harnessed setup`)
+
+## References
+
+- D-01 master orchestrator delegation pattern
+- D-02 bare slash cmd convention (ADR 0030 namespace policy LOCK)
+- D-10 ralph-loop orthogonal wrapper
+- ~/.claude/CLAUDE.md "Execute 阶段" 节 verbatim (karpathy 心法 + mattpocock 招式 + ralph-loop COMPLETE)
+- workflows/judgments/{subtask-gate,tdd-gate}.yaml — brainstorming + tdd-strongly-suggested triggers
+- workflows/task/{clarify,code,test,deliver}/workflow.yaml — 4 sub-workflow Phase 3.4 SHIPPED

package/workflows/task/auto/workflow.yaml

@@ -0,0 +1,57 @@
+# workflows/task/auto/workflow.yaml — Phase v3.0-3.5 W1 T3.5.W1.3
+#
+# Stage ③ Task master orchestrator — 串行 invoke 4 sub per subtask (clarify → code → test → deliver)
+# per ~/.claude/CLAUDE.md "Execute 阶段" 节 + RESEARCH-workflows § Area 2。
+# ralph-loop COMPLETE wrapper 在 deliver phase 内 (D-10 orthogonal wrapper not master concern)。
+# tdd-gate conditional fire on test sub (sister task/test/workflow.yaml gate
+# judgments.tdd-gate.tdd-strongly-suggested.fires)。
+#
+# Sister refs:
+#   - ~/.claude/CLAUDE.md "Execute 阶段 (GSD orchestration + superpowers 子任务执行)" 节
+#   - workflows/judgments/subtask-gate.yaml — brainstorming trigger (clarify)
+#   - workflows/judgments/tdd-gate.yaml — tdd-strongly-suggested trigger (test conditional)
+#   - workflows/task/{clarify,code,test,deliver}/workflow.yaml — 4 sub-workflow Phase 3.4 SHIPPED
+#   - workflows/capabilities.yaml — superpowers-brainstorming + tdd + grill-with-docs + zoom-out +
+#     improve-codebase-architecture + diagnose + ralph-loop + planning-with-files
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 Master Orchestrator yaml Examples
+#   - src/workflow/schema/workflow.ts WorkflowSchemaV3 + DelegationClause (Phase 3.3 W0.5 SHIPPED)
+#
+# Master invariant (per WorkflowSchemaV3 runtime + check-workflow-schema.mjs K9):
+#   - phases 缺省 (master only has delegates_to[])
+#   - 4 delegates_to mode serial — 必带 explicit order (K9 invariant T3.3.W0.10)
+#   - clarify conditional (subtask-gate brainstorming) + code/deliver unconditional + test conditional (tdd-gate)
+
+schema_version: harnessed.workflow.v3
+workflow: task
+description: |
+  Stage ③ Task master orchestrator — 串行 invoke 4 sub per subtask (clarify → code → test → deliver);
+  ralph-loop COMPLETE wrapper 在 deliver phase 内 (D-10 orthogonal wrapper not master concern)。
+  tdd-gate conditional fire on test sub (核心业务 / 算法 / 数据处理 / 回归 risk high / reliability
+  required, 6 fires_when OR-chain per ~/.claude/CLAUDE.md)。execute-task 每个 subtask 入口走一次。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available:
+  - superpowers-brainstorming
+  - tdd
+  - grill-with-docs
+  - zoom-out
+  - improve-codebase-architecture
+  - diagnose
+  - ralph-loop
+  - planning-with-files
+
+delegates_to:
+  - sub: clarify
+    gate: judgments.subtask-gate.brainstorming.fires
+    mode: serial
+    order: 1
+  - sub: code
+    mode: serial
+    order: 2
+  - sub: test
+    gate: judgments.tdd-gate.tdd-strongly-suggested.fires
+    mode: serial
+    order: 3
+  - sub: deliver
+    mode: serial
+    order: 4

package/workflows/task/clarify/SKILL.md

@@ -0,0 +1,83 @@
+---
+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 是否走)。
+
+## CLI invocation
+
+```bash
+# Dry-run preview — arbitrate-only, never spawns SDK.
+harnessed task-clarify --task "<text>" --dry-run --non-interactive
+
+# Apply path — real SDK spawn + 1-phase (conditional brainstorming via gate evaluation).
+harnessed task-clarify --task "<text>" --apply
+```
+
+## Forward-looking note
+
+The `trigger_phrases:` frontmatter is active after `harnessed setup` copies this
+SKILL.md to `~/.claude/skills/task-clarify/` — Claude Code then loads the slash
+command `/task-clarify` automatically (Gap B fix — sister v1.0.2 mechanism).
+
+## References
+
+- D-09 — L0 Discipline Substrate always-on (6 disciplines)
+- D-05 — phase-level `invokes_tools` conditional tool fire
+- D-04 — `gate` 4-level ref pre-resolved by `judgmentResolver`
+- D-02 — SKILL.md `name:` bare slash cmd (`task-clarify` NOT `task/clarify`) per ADR 0030
+- ~/.claude/CLAUDE.md "Execute 阶段" 节 brainstorming 子任务层判据
+- `workflows/judgments/subtask-gate.yaml` triggers.brainstorming
+- `workflows/capabilities.yaml` — superpowers-brainstorming + grill-with-docs entries
+- `workflows/defaults.yaml` — ralph_max_iterations.task-clarify.* values (T3.4.W2.2 followup)
+- `docs/WORKFLOW.md` — 4-stage workflow mermaid + Stage ③ Execute 章节

package/workflows/task/clarify/workflow.yaml

@@ -0,0 +1,39 @@
+# workflows/task/clarify/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.6 (D-09 + D-05 + D-04)
+#
+# Stage ③.a 子任务澄清 — superpowers brainstorm + mattpocock /grill-with-docs conditional invoke
+# (子任务 ≥2 approach OR core_algorithm OR has_api_contract OR error_cost=high)。
+# Sister gate: judgments.subtask-gate.brainstorming.fires (与 discuss/subtask 同 gate;
+# 但 Stage ③.a 是 per-subtask repeat invoke — execute-task 每个 subtask 入口走一次)。
+#
+# Sister refs:
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 task/clarify sub yaml example
+#   - workflows/judgments/subtask-gate.yaml triggers.brainstorming (Phase 2.3 W0.2 SHIPPED)
+#   - workflows/capabilities.yaml superpowers-brainstorming + grill-with-docs (Phase 2.3 W0.1 SHIPPED)
+#   - workflows/defaults.yaml ralph_max_iterations.task-clarify.* (T3.4.W2.2 followup wire)
+#   - src/workflow/schema/workflow.ts WorkflowSchemaV3 (Phase 3.3 W0.5 SHIPPED 122L)
+#
+# disciplines_applied: 6 default 全开 per D-09 L0 Discipline Substrate always-on
+# tools_available: 2 entry ∈ capabilities.yaml entry set (T3.3.W0.10 Contract C1 catch)
+
+schema_version: harnessed.workflow.v3
+workflow: task-clarify
+description: |
+  Stage ③.a 子任务澄清 — superpowers brainstorm + mattpocock /grill-with-docs (子任务
+  ≥2 approach 或核心算法 / API contract / 错误成本高 时激活)。Gate: judgments.subtask-gate
+  .brainstorming.fires (与 discuss-subtask 同 gate, 但 Stage ③.a 是 per-subtask repeat
+  invoke — execute-task 每个 subtask 入口走一次)。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [superpowers-brainstorming, grill-with-docs]
+
+phases:
+  - id: 01-brainstorm
+    name: brainstorm (子任务级澄清 multi-approach 探索)
+    upstream: superpowers
+    capability: '{{ capabilities.superpowers-brainstorming.cmd }}'
+    model: sonnet
+    gate: judgments.subtask-gate.brainstorming.fires
+    invokes_tools:
+      - if: 'phase.spec_ambiguous == true'
+        tool: grill-with-docs
+    max_iterations: '{{ defaults.ralph_max_iterations.task-clarify.01-brainstorm }}'

package/workflows/task/code/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: task-code
+description: |
+  task-code workflow v3 — Stage ③.b 子任务编码 sub-workflow (karpathy 4 心法
+  always-on + mattpocock conditional route + planning-with-files progress.md update)。
+  2-phase composition: 01-code (karpathy 心法 + zoom-out 陌生模块 / improve-arch
+  周期审查 / diagnose bug conditional invokes_tools) → 02-progress (Claude Code plugin
+  /plan 更新 progress.md 跨 session 进度同步)。
+  schema_version: harnessed.workflow.v3 with disciplines_applied [6] + tools_available
+  [zoom-out, improve-codebase-architecture, diagnose, planning-with-files]. Triggered
+  by harnessed CLI `harnessed task-code --task <text>` or slash command `/task-code`
+  after `harnessed setup`.
+trigger_phrases:
+  - "code this subtask"
+  - "task-code workflow"
+  - "Stage 3 code"
+  - "跑 task-code"
+---
+
+# task-code workflow (v3)
+
+## Overview
+
+2-phase sub-workflow mapping the user's CLAUDE.md Stage ③.b 子任务编码 discipline
+onto the harnessed runtime, fully `harnessed.workflow.v3` schema (Phase v3.0-3.4 W0
+T3.4.W0.7 — D-09 L0 Discipline Substrate + D-05 conditional `invokes_tools` + D-15
+planning-with-files plugin).
+
+| phase | id | upstream | model | capability / invokes_tools |
+| ----- | -- | -------- | ----- | -------------------------- |
+| 1 | `01-code` | karpathy | sonnet | `invokes_tools: [{if: phase.unfamiliar_module, tool: zoom-out}, {if: phase.architecture_health_audit, tool: improve-codebase-architecture}, {if: subtask.bug_root_cause_unknown, tool: diagnose}]` |
+| 2 | `02-progress` | planning-with-files | haiku | `{{ capabilities.planning-with-files.cmd }}` / `invokes: /plan` / `artifacts_expected: [progress.md]` |
+
+Per-phase config loads from `workflows/task/code/workflow.yaml`; engine.runRouting
+spawns each phase as a sub-agent via `@anthropic-ai/claude-agent-sdk` 0.3.142+.
+
+## Karpathy 4 心法 (L0 Discipline Substrate always-on)
+
+Phase 01-code 的 upstream 是 `karpathy` — runtime engine 加载 `workflows/disciplines/
+karpathy.yaml` discipline rules 应用 cross-cutting (Think Before Coding / Simplicity
+First / Surgical Changes / Goal-Driven Execution + ≤200L hard limit + no-feature-creep
++ trust-internal-code + no-comments-default). 不 invoke slash cmd, 通过 hook 强制
+behavioral rule per D-09 L0 Discipline Substrate.
+
+## mattpocock conditional route (D-05 invokes_tools)
+
+Phase 01-code 按 phase fact context 条件性 fire 3 mattpocock 招式:
+- `zoom-out` — 陌生模块导航 (when `phase.unfamiliar_module == true`)
+- `improve-codebase-architecture` — 周期架构健康审查 (when `phase.architecture_health_audit == true`)
+- `diagnose` — bug 系统化排错 (when `subtask.bug_root_cause_unknown == true`)
+
+3 触发条件 OR-chain, 任 1 fire 即 invoke 对应招式 — 不互斥 (sister CLAUDE.md
+"mattpocock 招式按需召唤" pattern, NOT exclusive). 无触发 = pure karpathy 心法 only.
+
+## Phase 02-progress planning-with-files plugin 真接 (Q-AUDIT-5a LOCKED Option A)
+
+02-progress invokes the **Claude Code plugin** slash command `/plan` to update
+`progress.md` in `.planning/<phase-id>/` — 跟踪 subtask 完成 / blocked / next step
+per CLAUDE.md "跨 session 恢复" 模式 + R20.6 Manus-style 持久化。Plugin path
+verified at `~/.claude/plugins/cache/planning-with-files/planning-with-files/2.34.0/`
+(2026-05-20).
+
+## CLI invocation
+
+```bash
+# Dry-run preview — arbitrate-only, never spawns SDK.
+harnessed task-code --task "<text>" --dry-run --non-interactive
+
+# Apply path — real SDK spawn + 2-phase chain.
+harnessed task-code --task "<text>" --apply
+```
+
+## Forward-looking note
+
+The `trigger_phrases:` frontmatter is active after `harnessed setup` copies this
+SKILL.md to `~/.claude/skills/task-code/` — Claude Code then loads the slash
+command `/task-code` automatically (Gap B fix — sister v1.0.2 mechanism).
+
+## References
+
+- D-09 — L0 Discipline Substrate always-on (karpathy 心法 4 条 cross-cutting)
+- D-05 — phase-level `invokes_tools` conditional tool fire
+- D-15 + Q-AUDIT-5a — planning-with-files = Claude Code plugin slash cmd `/plan`
+- D-02 — SKILL.md `name:` bare slash cmd (`task-code` NOT `task/code`) per ADR 0030
+- ~/.claude/CLAUDE.md "Execute 阶段" 节 karpathy 心法 + mattpocock 招式按需召唤
+- `workflows/disciplines/karpathy.yaml` — 4 心法 + ≤200L hard limit 等 rules (L0 substrate)
+- `workflows/capabilities.yaml` — zoom-out / improve-codebase-architecture / diagnose / planning-with-files entries
+- `workflows/defaults.yaml` — ralph_max_iterations.task-code.* values (T3.4.W2.2 followup)
+- `docs/WORKFLOW.md` — 4-stage workflow mermaid + Stage ③ Execute 章节