harnessed 3.4.3 → 3.5.0

package/workflows/execute-task/workflow.yaml

@@ -0,0 +1,93 @@
+# workflows/execute-task/workflow.yaml — v3.4.4 Phase 4 Commit 1 NEW (Path A)
+# Former v2 `phases.yaml` (74L) deleted v3.4.4 Phase 6 Wave 3c — this v3
+# workflow.yaml is now the single SoT. Authored fresh per HANDOFF-v3.4.4 L745
+# Path A decision + PHASE-4-SPEC L101-180 verbatim.
+#
+# 4-phase chain mirrors v2 verbatim:
+#   01-clarify  superpowers-brainstorming  opus    gate: subtask-gate.brainstorming.fires
+#   02-code     karpathy 心法 + on[]       sonnet  conditional: tdd / grill-with-docs / zoom-out
+#   03-test     superpowers TDD            sonnet  on: test_fail → diagnose
+#   04-deliver  ralph-loop                 haiku   args.completion_promise=COMPLETE + fallback
+#
+# v2 → v3 字段 delta (PHASE-4-SPEC L13 + L116-178):
+#   BUMP `schema_version: harnessed.workflow.v3` (sister Phase 3.3 W0.5 WorkflowSchemaV3)
+#   ADD  `disciplines_applied: [6 basename]` (D-09 L0 Discipline Substrate, Pattern A A.1 strict Literal Union)
+#   ADD  `tools_available: [7 capabilities.yaml entry name]` (D-05 Contract C1 cross-validate)
+#   KEEP phases verbatim from former v2 phases.yaml (Path A1 — coexisted through Phase 5; v2 deleted Phase 6 Wave 3c)
+#
+# Per-phase model tier (intel CD-2 § 第 4 条) preserved verbatim from v2:
+#   opus / sonnet / sonnet / haiku
+# Override via CLI: `--model-tier inherit` (B-10 escape hatch).
+#
+# Sister refs:
+#   - .planning/v3.4.4/PHASE-4-SPEC.md L101-180 (NEW yaml shape verbatim)
+#   - workflows/execute-task/phases.yaml (former v2 SoT — DELETED v3.4.4 Phase 6 Wave 3c; this workflow.yaml is sole SoT)
+#   - workflows/research/workflow.yaml (v3 standalone shape reference)
+#   - workflows/verify/simplify/workflow.yaml (v3 sub-workflow shape reference)
+#   - workflows/capabilities.yaml (7 capability refs: superpowers-brainstorming/tdd/grill-with-docs/zoom-out/diagnose/ralph-loop/planning-with-files)
+#   - workflows/defaults.yaml ralph_max_iterations.execute-task.{01..04}
+#   - workflows/disciplines/{karpathy,output-style,language,operational,priority,protocols}.yaml (L0 substrate)
+#   - src/workflow/schema/workflow.ts WorkflowSchemaV3 (Phase 3.3 W0.5 SHIPPED 122L)
+
+schema_version: harnessed.workflow.v3
+workflow: execute-task
+description: |
+  子任务执行 workflow — 4-phase chain (brainstorming → karpathy + mattpocock route by
+  condition → TDD + diagnose → ralph-loop COMPLETE) triggered by harnessed CLI
+  `harnessed execute-task --task <text>` OR universal `harnessed run execute-task`.
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [superpowers-brainstorming, tdd, grill-with-docs, zoom-out, diagnose, ralph-loop, planning-with-files]
+
+phases:
+  - id: 01-clarify
+    name: brainstorming
+    upstream: superpowers brainstorming
+    capability: '{{ capabilities.superpowers-brainstorming.cmd }}'
+    model: opus
+    max_iterations: '{{ defaults.ralph_max_iterations.execute-task.01-clarify }}'
+    gate: judgments.subtask-gate.brainstorming.fires
+
+  - id: 02-code
+    name: code (karpathy 心法 always-on + mattpocock conditional route)
+    upstream: karpathy
+    model: sonnet
+    max_iterations: '{{ defaults.ralph_max_iterations.execute-task.02-code }}'
+    on:
+      - if: 'judgments.tdd-gate.tdd-strongly-suggested.fires'
+        invoke: '{{ capabilities.tdd.cmd }}'
+      - if: 'phase.spec_ambiguous == true'
+        invoke: '{{ capabilities.grill-with-docs.cmd }}'
+      - if: 'phase.unfamiliar_module == true'
+        invoke: '{{ capabilities.zoom-out.cmd }}'
+
+  - id: 03-test
+    name: test (conditional TDD + diagnose on fail)
+    upstream: superpowers TDD
+    capability: '{{ capabilities.tdd.cmd }}'
+    model: sonnet
+    max_iterations: '{{ defaults.ralph_max_iterations.execute-task.03-test }}'
+    on:
+      - if: 'test_fail == true'
+        invoke: '{{ capabilities.diagnose.cmd }}'
+
+  - id: 04-deliver
+    name: deliver (ralph-loop COMPLETE gate + max-iter fallback)
+    upstream: ralph-loop
+    capability: '{{ capabilities.ralph-loop.cmd }}'
+    model: haiku
+    args:
+      completion_promise: COMPLETE
+      max_iterations: '{{ defaults.ralph_max_iterations.execute-task.04-deliver }}'
+    gate: judgments.parallelism-gate.fires
+    parallelism: judgments.parallelism-gate.ralph-loop-wrapper.fires
+    on:
+      - if: 'subtask.lines >= 20 and subtask.type != "single_command_query"'
+        invoke: '{{ capabilities.ralph-loop.cmd }}'
+      - if: 'subtask.lines < 20 or subtask.type == "single_command_query"'
+        action: skip
+    fallback:
+      max_iterations_exceeded:
+        action: emit_warning_and_halt
+        message: '⚠️ ralph-loop max-iterations ({{ args.max_iterations }}) exceeded for execute-task 04-deliver. Sub-task likely incomplete — see workflow engine catch handler for manual options.'
+        exit_code: 1

package/workflows/judgments/fallback.yaml

@@ -1,5 +1,5 @@
 # workflows/judgments/fallback.yaml
-# Fallback 三条铁律 — 机器化 ~/.claude/CLAUDE.md 「Fallback 三条铁律」 verbatim
+# Fallback 三条铁律 — bundled judgment (unsure → tend to skip with transparent disclosure / explicit user signal overrides / tiers independent)
 # Sister: 不同于 triggers (fires_when/skips_when 模式), 本 file 使用 'rules' 顶级 key
 # Phase v2.0-2.3 Wave 0 T2.3.W0.2 ship per R20.16 + D-16
 

package/workflows/judgments/parallelism-gate.yaml

@@ -1,6 +1,7 @@
 # workflows/judgments/parallelism-gate.yaml
-# Parallelism 判据 — 机器化 ~/.claude/CLAUDE.md 「子任务并行执行机制 (subagent vs Agent Teams 路由)」节
-# Sister: ~/.claude/rules/agent-teams.md (5 升级触发完整生命周期)
+# Parallelism 判据 — bundled subagent vs Agent Teams routing rules
+# (4 triggers: subagent-default / main-session-fallback / agent-teams-upgrade / ralph-loop-wrapper)
+# Bundled Agent Teams lifecycle: 5 upgrade triggers + cleanup discipline
 # Phase v2.0-2.3 Wave 0 T2.3.W0.2 ship per D-11 (parallelism-gate) + R20.10 (ralph-loop 正交 wrapper)
 
 schema_version: harnessed.judgment.v1
@@ -23,7 +24,7 @@ triggers:
 
   agent-teams-upgrade:
     description: |
-      Upgrade — Claude Code Agent Teams 升级 per ~/.claude/rules/agent-teams.md
+      Upgrade — Claude Code Agent Teams 升级 (bundled rule):
       5 任一触发即可 (teammate SendMessage 互通 / subagent context overflow /
       共享 task list 自协调 / 对立假设辩论 / 全栈三路协同)。
       开 team 前 token 成本估算 team_cost < 2 × subagent_cost 才划算。

package/workflows/judgments/phase-gate.yaml

@@ -1,6 +1,6 @@
 # workflows/judgments/phase-gate.yaml
-# Phase 层 (Phase tier) 判据 — 机器化 ~/.claude/CLAUDE.md 「澄清/审查触发判据」节
-# Sister: GSD /gsd-discuss-phase orchestration gate (also /gsd-new-project, /gsd-next)
+# Phase 层 (Phase tier) 判据 — bundled judgment (3-tier independent clarification: strategic / phase / subtask)
+# Pairs with: GSD /gsd-discuss-phase orchestration gate (also /gsd-new-project, /gsd-next; when capability available)
 # Phase v2.0-2.3 Wave 0 T2.3.W0.2 ship per D-04 + D-16 multi-file 分类
 
 schema_version: harnessed.judgment.v1

package/workflows/judgments/strategic-gate.yaml

@@ -1,6 +1,6 @@
 # workflows/judgments/strategic-gate.yaml
-# 战略层 (Strategy tier) 判据 — 机器化 ~/.claude/CLAUDE.md 「澄清/审查触发判据」节
-# Sister: gstack /office-hours + /plan-ceo-review governance gate
+# 战略层 (Strategy tier) 判据 — bundled judgment (3-tier independent clarification: strategic / phase / subtask)
+# Pairs with: gstack /office-hours + /plan-ceo-review governance gate (when capability available)
 # Phase v2.0-2.3 Wave 0 T2.3.W0.2 ship per D-04 + D-16 multi-file 分类
 
 schema_version: harnessed.judgment.v1

package/workflows/judgments/subtask-gate.yaml

@@ -1,6 +1,6 @@
 # workflows/judgments/subtask-gate.yaml
-# 子任务层 (Subtask tier) 判据 — 机器化 ~/.claude/CLAUDE.md 「澄清/审查触发判据」节
-# Sister: superpowers:brainstorming skill (与 superpowers TDD red-green-refactor 并行评估)
+# 子任务层 (Subtask tier) 判据 — bundled judgment (3-tier independent clarification: strategic / phase / subtask)
+# Pairs with: superpowers:brainstorming skill (与 superpowers TDD red-green-refactor 并行评估; when capability available)
 # Phase v2.0-2.3 Wave 0 T2.3.W0.2 ship per D-04 + D-16 multi-file 分类
 
 schema_version: harnessed.judgment.v1

package/workflows/judgments/tdd-gate.yaml

@@ -1,6 +1,6 @@
 # workflows/judgments/tdd-gate.yaml
-# TDD 判据 — 机器化 ~/.claude/CLAUDE.md 「Execute 阶段 TDD 强烈建议开启」节
-# Sister: superpowers:test-driven-development skill (alias mattpocock /tdd per D-13)
+# TDD 判据 — bundled judgment (Execute-stage TDD: red-green-refactor strongly recommended for core logic / algorithms / high-reliability)
+# Pairs with: superpowers:test-driven-development skill (alias mattpocock /tdd per D-13; when capability available)
 # Phase v2.0-2.3 Wave 0 T2.3.W0.2 ship per D-13 (6 fires + 3 skips)
 
 schema_version: harnessed.judgment.v1

package/workflows/judgments/web-design-routing.yaml

@@ -1,5 +1,5 @@
 # workflows/judgments/web-design-routing.yaml
-# Sister: ~/.claude/rules/web-design.md ui-ux-pro-max 默认 + frontend-design 补充 + 仲裁
+# Bundled routing rule: ui-ux-pro-max 默认主方案 (数据驱动) + frontend-design 创意补充 + arbitration
 # Phase v3.0-3.2 Wave A RESEARCH → 3.3 W0.3 ship per D-11
 #
 # 默认 ui-ux-pro-max 优先 (数据驱动 / 标准化 / 可解释);

package/workflows/judgments/web-search-routing.yaml

@@ -1,5 +1,5 @@
 # workflows/judgments/web-search-routing.yaml
-# Sister: ~/.claude/rules/web-search.md 条件式 fallback + Tavily/Exa MCP routing
+# Bundled routing rule: 条件式 fallback + Tavily/Exa MCP routing (with WebFetch / gh CLI / ctx7 CLI fallbacks)
 # Phase v3.0-3.2 Wave A RESEARCH → 3.3 W0.3 ship per D-11
 #
 # 路由优先级 (per rules/web-search.md):

package/workflows/judgments/web-testing-routing.yaml

@@ -1,5 +1,5 @@
 # workflows/judgments/web-testing-routing.yaml
-# Sister: ~/.claude/rules/web-testing.md 三层职责矩阵 + 决策树机器化
+# Bundled routing rule: 三层职责矩阵 (脑 @playwright/test / 手 playwright-cli / 筋骨 webapp-testing) + 决策树
 # Phase v3.0-3.2 Wave A RESEARCH → 3.3 W0.3 ship per D-11
 #
 # 三层职责矩阵 verbatim:

package/workflows/plan/architecture/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: plan-architecture
 description: |
-  Stage ②.a 架构层 plan sub-workflow — gstack /plan-eng-review (复杂架构强制治理关卡,
-  sister ~/.claude/CLAUDE.md "⚠️ 复杂架构前 plan-eng-review")。schema_version:
+  Stage ②.a 架构层 plan sub-workflow — gstack /plan-eng-review (复杂架构强制治理关卡;
+  bundled plan-stage cadence: mandatory before complex-architecture phases)。schema_version:
   harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
   [plan-eng-review] + 1 phase (01-plan-eng-review) + gate literal expr
   `phase.is_complex_architecture == true`。Triggered by harnessed CLI `harnessed
@@ -52,44 +52,23 @@ trigger `is-complex-architecture` 重构 ref。
 - 性能 / scaling 关键路径
 - 引入显著技术债 / migration 风险
 
-<!-- v3.4.3-dual-path-invocation -->
 ## How to invoke
 
-**Preferred path** (when the upstream specialist is installed): use the SlashCommand tool to run `{{ capabilities.plan-eng-review.cmd }}` — the upstream specialist takes over.
-
-**Fallback path** (when the upstream isn't installed or returns no result): use the Task tool to spawn a general-purpose subagent with this prompt:
-
-> You are a **Staff Engineer architect**.
->
-> **Mission**: Lock down system architecture BEFORE phase planning when complex (≥3 modules / new framework / new data model / scaling-critical / large migration). Adapted from gstack `/plan-eng-review`.
->
-> **Default-suspect mode**: assume the change is broken / risky / incomplete until proven otherwise. Cite `file:line` for every finding; do not generalize.
->
-> **Review checklist**:
-> 1. Identify the smallest architecture change that satisfies all requirements
->
-> 2. Diagram component boundaries (data flow / call direction / ownership)
->
-> 3. List interfaces / contracts between components (function signatures, API shapes)
->
-> 4. Failure modes: what happens when each component is slow / down / inconsistent?
->
-> 5. Migration / rollback path — can we ship in slices, or all-at-once?
->
-> 6. Choose mechanisms with the lowest blast radius and lowest unique vocabulary
->
-> 7. Document tradeoffs of the rejected alternatives (so reviewers see the road not taken)
->
-> **Output format**: structured report with severity-classified findings (approved / approved-with-changes / blocked). One finding per line: `[severity] file:line — problem (one sentence); fix: suggested change`. If no findings, say so explicitly. No preamble, no end-of-report summary.
-
-(Role prompt is self-contained — works even when the upstream `plan-eng-review` user-skill / plugin isn't installed.)
-
-(Sister `~/.claude/commands/plan-architecture.md` is also generated by `harnessed setup` so `/plan-architecture` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed plan-architecture --apply` CLI claims are removed; that subcommand was never implemented.)
+Use the Bash tool to run:
+
+```bash
+echo "$ARGUMENTS" | harnessed run plan-architecture --task-stdin
+```
+
+If `$ARGUMENTS` is empty, run `harnessed run plan-architecture` (no stdin pipe).
+
+After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
+
+<!-- harnessed-generated:v3.4.4 -->
 
 ## References
 
 - D-04 Stage ② Plan 二层 (架构 / 计划)
 - D-12 gstack 治理关卡 (复杂架构强制)
-- ~/.claude/CLAUDE.md "⚠️ 复杂架构前: /plan-eng-review"
 - workflows/capabilities.yaml — plan-eng-review (Bucket 7)
 - workflows/defaults.yaml — ralph_max_iterations.plan-architecture.* values (W2.2 backfill)

package/workflows/plan/architecture/workflow.yaml

@@ -1,7 +1,7 @@
 # workflows/plan/architecture/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.4
 #
-# Stage ②.a 架构层 sub-workflow — gstack /plan-eng-review (复杂架构强制,
-# sister ~/.claude/CLAUDE.md "⚠️ 复杂架构前 plan-eng-review")。
+# Stage ②.a 架构层 sub-workflow — gstack /plan-eng-review (mandatory before
+# complex-architecture phases per bundled plan-stage cadence).
 #
 # Sister refs:
 #   - workflows/capabilities.yaml — plan-eng-review (Bucket 7 gstack 33 optional registry)

package/workflows/plan/auto/SKILL.md

@@ -21,7 +21,7 @@ trigger_phrases:
 ## Overview
 
 4-stage cadence Stage ② master orchestrator delegating to 2 sequential sub-workflows
-(per ~/.claude/CLAUDE.md "Plan 阶段" 节 + D-06 planning-with-files cross-cutting tool):
+(bundled Plan-stage cadence + D-06 planning-with-files cross-cutting tool):
 
 | order | sub | gate ref | mode | when fires |
 | ----- | --- | -------- | ---- | ---------- |
@@ -52,20 +52,24 @@ Sister `workflows/capabilities.yaml`:
 
 - Slash command: `/plan <text>` (bare per ADR 0030 namespace policy D-02 LOCK after `harnessed setup`)
 
-<!-- v3.4.3-dual-path-invocation -->
 ## How to invoke
 
-**Preferred path** (master orchestrator): dispatch to the per-sub-workflow slash commands in the order this stage prescribes. Each sub command lives at `~/.claude/commands/<sub-name>.md` with its own dual-path fallback.
+Use the Bash tool to run:
 
-**Fallback path** (when no slash command from the sub-list resolves): run each missing sub-workflow inline using its own role prompt from `~/.claude/skills/<sub-name>/SKILL.md`. Do NOT skip stages silently — each sub either runs or is logged as "skipped: <reason>".
+```bash
+echo "$ARGUMENTS" | harnessed run plan --task-stdin
+```
 
-(Sister `~/.claude/commands/plan.md` is also generated by `harnessed setup` so `/plan` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed plan --apply` CLI claims are removed; that subcommand was never implemented.)
+If `$ARGUMENTS` is empty, run `harnessed run plan` (no stdin pipe).
+
+After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
+
+<!-- harnessed-generated:v3.4.4 -->
 
 ## References
 
 - D-01 master orchestrator delegation pattern
 - D-02 bare slash cmd convention (ADR 0030 namespace policy LOCK)
 - D-06 planning-with-files cross-cutting tool (NOT 独立 sub-workflow)
-- ~/.claude/CLAUDE.md "Plan 阶段" 节 verbatim
 - workflows/judgments/stage-routing.yaml — plan-{architecture,phase}-delegate triggers
 - workflows/plan/{architecture,phase}/workflow.yaml — 2 sub-workflow Phase 3.4 SHIPPED

package/workflows/plan/auto/workflow.yaml

@@ -1,11 +1,10 @@
 # workflows/plan/auto/workflow.yaml — Phase v3.0-3.5 W1 T3.5.W1.2
 #
 # Stage ② Plan master orchestrator — 串行 invoke 2 sub (architecture conditional → phase always)
-# per ~/.claude/CLAUDE.md "Plan 阶段" 节 + RESEARCH-workflows § Area 2。
+# per bundled Plan-stage cadence + RESEARCH-workflows § Area 2。
 # planning-with-files /plan 是 D-06 cross-cutting tool (NOT 独立 sub-workflow per user clarification 2)。
 #
 # Sister refs:
-#   - ~/.claude/CLAUDE.md "Plan 阶段 (GSD + planning-with-files, 可选 gstack 架构审查)" 节
 #   - workflows/judgments/stage-routing.yaml — plan-{architecture,phase}-delegate triggers
 #   - workflows/plan/{architecture,phase}/workflow.yaml — 2 sub-workflow Phase 3.4 SHIPPED
 #   - workflows/capabilities.yaml — planning-with-files + plan-eng-review + gsd-plan-phase

package/workflows/plan/phase/SKILL.md

@@ -3,7 +3,7 @@ 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 ② 铁律:
+  progress.md (bundled Plan-stage cadence: 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
@@ -34,8 +34,8 @@ claude-code-plugin /plan + Pattern A sub-workflow ship)。
 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)
+  requires the `planning-with-files` Claude Code plugin to be installed via the
+  Claude Code plugin marketplace; outputs: task_plan.md + progress.md + findings.md)
 
 ## Stage ② 铁律 — dual capability
 
@@ -54,44 +54,23 @@ reframe)。
 - `progress.md` — phase 进度跟踪 + cross-session 恢复
 - (`findings.md` 由 discuss-* sub-workflow 产出, 此处不重复)
 
-<!-- v3.4.3-dual-path-invocation -->
 ## How to invoke
 
-**Preferred path** (when the upstream specialist is installed): use the SlashCommand tool to run `{{ capabilities.gsd-plan-phase.cmd }}` — the upstream specialist takes over.
-
-**Fallback path** (when the upstream isn't installed or returns no result): use the Task tool to spawn a general-purpose subagent with this prompt:
-
-> You are a **Phase planner**.
->
-> **Mission**: Break a phase into ordered, dependency-aware tasks with explicit file paths and acceptance criteria, then persist via planning-with-files plugin. Adapted from GSD `/gsd-plan-phase` (Wave A research → Wave B planner → Wave C plan-checker).
->
-> **Default-suspect mode**: assume the change is broken / risky / incomplete until proven otherwise. Cite `file:line` for every finding; do not generalize.
->
-> **Review checklist**:
-> 1. Each task names the exact files it touches (NOT just 'auth module')
->
-> 2. Each task has acceptance criteria a third party can verify
->
-> 3. Dependencies are explicit (task N requires task M output)
->
-> 4. Tasks are ≤1 day each; split if larger
->
-> 5. Identify the verification step (test / lint / typecheck) for each task
->
-> 6. Persist as `task_plan.md` + `progress.md` via planning-with-files `/plan`
->
-> 7. Final pass: a fresh agent should be able to execute from these files alone
->
-> **Output format**: structured report with severity-classified findings (ready-to-execute / needs-revision / blocked). One finding per line: `[severity] file:line — problem (one sentence); fix: suggested change`. If no findings, say so explicitly. No preamble, no end-of-report summary.
-
-(Role prompt is self-contained — works even when the upstream `gsd-plan-phase` user-skill / plugin isn't installed.)
-
-(Sister `~/.claude/commands/plan-phase.md` is also generated by `harnessed setup` so `/plan-phase` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed plan-phase --apply` CLI claims are removed; that subcommand was never implemented.)
+Use the Bash tool to run:
+
+```bash
+echo "$ARGUMENTS" | harnessed run plan-phase --task-stdin
+```
+
+If `$ARGUMENTS` is empty, run `harnessed run plan-phase` (no stdin pipe).
+
+After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
+
+<!-- harnessed-generated:v3.4.4 -->
 
 ## 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

@@ -1,9 +1,9 @@
 # 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)。
+# Wave C plan-checker + planning-with-files /plan 持久化 task_plan.md
+# (bundled Plan-stage cadence: 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

package/workflows/plan-feature/SKILL.md

@@ -54,9 +54,9 @@ to brainstorm or planning (D-04 PUSH 任 1 phase 转换前 read = vetoed → 全
 
 ### Phase 5 planning-with-files plugin 真接 (Q-AUDIT-5a LOCKED Option A)
 
-05-persist invokes the **Claude Code plugin** slash command `/plan` via plugin
-cache at `~/.claude/plugins/cache/planning-with-files/planning-with-files/2.34.0/`
-(verified 2026-05-20). The plugin generates 3 markdown files in
+05-persist invokes the **Claude Code plugin** slash command `/plan`. Requires
+the `planning-with-files` Claude Code plugin to be installed via the Claude Code
+plugin marketplace. The plugin generates 3 markdown files in
 `.planning/<phase-id>/`:
 
 - `task_plan.md` — 主计划 (task 列表 + 文件路径 + 依赖顺序 + 验收标准)
@@ -84,7 +84,7 @@ harnessed plan-feature --task "<text>" --apply
 ## Forward-looking note
 
 The `trigger_phrases:` frontmatter is active after `harnessed setup` copies this
-SKILL.md to `~/.claude/skills/plan-feature/` — Claude Code then loads the slash
+SKILL.md to `<claude-home>/skills/plan-feature/` — Claude Code then loads the slash
 command `/plan-feature` automatically (Gap B fix — v1.0.2).
 
 ## References

package/workflows/research/SKILL.md

@@ -16,7 +16,7 @@ phases content (01-fan-out + 02-synth) verbatim reused from v2 SHIPPED unchanged
 
 | # | Phase | Upstream | Capability | Model | Description |
 |---|-------|----------|-----------|-------|-------------|
-| 01 | `01-fan-out` | web-search | (route-by-subtask) | sonnet | 3 source fan-out (Tavily MCP / Exa MCP / ctx7 CLI per ~/.claude/rules/web-search.md + context7.md routing) |
+| 01 | `01-fan-out` | web-search | (route-by-subtask) | sonnet | 3 source fan-out (Tavily MCP / Exa MCP / ctx7 CLI per bundled web-search + context7 routing) |
 | 02 | `02-synth` | gsd | `gsd-discuss-phase` | opus | GSD discuss-phase aggregate + dedup + reconcile |
 
 ## Capability refs
@@ -30,17 +30,16 @@ Sister `workflows/capabilities.yaml` entries:
 ## Invocation
 - Slash command: `/research <topic>` (after `harnessed setup`)
 
-## Routing rules (sister ~/.claude/rules/web-search.md)
+## Routing rules (bundled web-search routing — `workflows/judgments/web-search-routing.yaml`)
 - 描述式查询 ("找一篇对比 X 和 Y 的博客") → Exa MCP
 - 学术 / 论文 → Exa MCP
-- 库 / API 文档 → ctx7 CLI (per ~/.claude/rules/context7.md)
+- 库 / API 文档 → ctx7 CLI
 - 关键词 / 时效内容 → Tavily MCP (默认)
 - 抓整站 / 站点结构 → Tavily crawl/map
 
-<!-- v3.4.3-dual-path-invocation -->
 ## How to invoke
 
-**Preferred path** (master orchestrator): dispatch to the per-sub-workflow slash commands in the order this stage prescribes. Each sub command lives at `~/.claude/commands/<sub-name>.md` with its own dual-path fallback.
+**Preferred path** (master orchestrator): dispatch to the per-sub-workflow slash commands in the order this stage prescribes. Each sub command lives at `<claude-home>/commands/<sub-name>.md` (installed by `harnessed setup`) with its own dual-path fallback.
 
 **Fallback path** (when the upstream isn't installed or returns no result): use the Task tool to spawn a general-purpose subagent with this prompt:
 
@@ -65,4 +64,18 @@ Sister `workflows/capabilities.yaml` entries:
 
 (Role prompt is self-contained — works even when the upstream `specialist` user-skill / plugin isn't installed.)
 
-(Sister `~/.claude/commands/research.md` is also generated by `harnessed setup` so `/research` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed research --apply` CLI claims are removed; that subcommand was never implemented.)
+(`harnessed setup` also installs a `research` Claude Code slash command at `<claude-home>/commands/research.md` so `/research` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed research --apply` CLI claims are removed; that subcommand was never implemented.)
+
+## How to invoke
+
+Use the Bash tool to run:
+
+```bash
+echo "$ARGUMENTS" | harnessed run research --task-stdin
+```
+
+If `$ARGUMENTS` is empty, run `harnessed run research` (no stdin pipe).
+
+After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
+
+<!-- harnessed-generated:v3.4.4 -->

package/workflows/research/workflow.yaml

@@ -2,8 +2,8 @@
 # (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。
+# + ctx7 CLI (库 API 文档) fan-out + GSD discuss synth aggregate; bundled web-search +
+# context7 routing rules (workflows/judgments/web-search-routing.yaml) 机器化 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)
@@ -26,8 +26,8 @@ schema_version: harnessed.workflow.v3
 workflow: research
 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。
+  学术) + ctx7 CLI (库 API 文档) fan-out + GSD discuss synth aggregate; bundled
+  web-search + context7 routing rules 机器化 per R20.7 + D-08。
 
 disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
 tools_available: [tavily-mcp, exa-mcp, ctx7, gsd-discuss-phase]

package/workflows/retro/SKILL.md

@@ -2,8 +2,8 @@
 name: retro
 description: |
   Standalone post-④ Verify retrospective workflow — gstack /retro 经验教训 / 决策 / lessons
-  系统总结 (项目 / 里程碑结束可选, sister ~/.claude/CLAUDE.md "项目 / 里程碑结束: 可选跑
-  /retro 总结" verbatim) + planning-with-files RETROSPECTIVE.md 持久化 (sister Phase
+  系统总结 (项目 / 里程碑结束可选, bundled milestone-close retrospective cadence)
+  + 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
@@ -47,44 +47,25 @@ Sister `workflows/capabilities.yaml` entries:
 - ✅ **触发**: 项目结束 / 里程碑结束 / 用户明示 "复盘 / retro / lessons learned"
 - ❌ **跳过**: 日常 PR / 单 phase 完成 (常规 verify-progress 已够用)
 
-<!-- v3.4.3-dual-path-invocation -->
 ## How to invoke
 
-**Preferred path** (when the upstream specialist is installed): use the SlashCommand tool to run `{{ capabilities.retro-gstack.cmd }}` — the upstream specialist takes over.
-
-**Fallback path** (when the upstream isn't installed or returns no result): use the Task tool to spawn a general-purpose subagent with this prompt:
-
-> You are a **Retrospective facilitator**.
->
-> **Mission**: Run a Lessons / Decisions / Surprises retrospective for the closed milestone, then persist to `RETROSPECTIVE.md`. Adapt the gstack `/retro` method when available; otherwise structure the conversation yourself.
->
-> **Default-suspect mode**: assume the change is broken / risky / incomplete until proven otherwise. Cite `file:line` for every finding; do not generalize.
->
-> **Review checklist**:
-> 1. What did we set out to do, vs. what actually shipped?
->
-> 2. Top 3 surprises (positive or negative) — root cause each
->
-> 3. Decisions that paid off; decisions we would reverse
->
-> 4. Process changes for next milestone (concrete, not vague)
->
-> 5. What deserves a permanent rule entry (CLAUDE.md / docs/adr/)?
->
-> 6. Persist verbatim to `.planning/RETROSPECTIVE.md` — append, do not overwrite
->
-> **Output format**: structured report with severity-classified findings (lesson / decision / surprise / process-change). One finding per line: `[severity] file:line — problem (one sentence); fix: suggested change`. If no findings, say so explicitly. No preamble, no end-of-report summary.
-
-(Role prompt is self-contained — works even when the upstream `retro-gstack` user-skill / plugin isn't installed.)
-
-(Sister `~/.claude/commands/retro.md` is also generated by `harnessed setup` so `/retro` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed retro --apply` CLI claims are removed; that subcommand was never implemented.)
+Use the Bash tool to run:
+
+```bash
+echo "$ARGUMENTS" | harnessed run retro --task-stdin
+```
+
+If `$ARGUMENTS` is empty, run `harnessed run retro` (no stdin pipe).
+
+After completion, the Bash output prints a `Next:` hint on stderr suggesting the next stage. Decide whether to invoke based on conversation context — the hint is informational, not prescriptive.
+
+<!-- harnessed-generated:v3.4.4 -->
 
 ## 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

@@ -1,11 +1,10 @@
 # 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)。
+# bundled milestone-close retrospective cadence).
 # 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)

package/workflows/role-prompts.yaml

@@ -1,7 +1,8 @@
 # <packageRoot>/workflows/role-prompts.yaml — harnessed v3.4.3 role-prompt registry.
 #
 # Per-sub-workflow metadata consumed by `src/cli/lib/generateCommands.ts` to
-# emit `~/.claude/commands/<slash-name>.md` files at `harnessed setup` time.
+# emit `<claude-home>/commands/<slash-name>.md` files at `harnessed setup`
+# time (Claude Code slash command install path).
 #
 # Each entry describes:
 #   primary_cap:    Which capability key the "preferred path" invokes (the
@@ -13,7 +14,7 @@
 #                   upstream gstack expert prompts where available (cited inline).
 #                   Self-contained — works even when upstream user-skill missing.
 #   severity:       Severity scale label used in the report format.
-#   description:    YAML frontmatter `description` for ~/.claude/commands/<x>.md.
+#   description:    YAML frontmatter `description` for <claude-home>/commands/<x>.md.
 #
 # Karpathy simplicity: 1 small yaml beats 23 hardcoded strings in TS.
 
@@ -45,7 +46,7 @@ prompts:
     specialist: "Stage 1 discuss dispatcher"
     responsibility: |
       Independently evaluate three clarification layers (strategic / phase /
-      subtask) per ~/.claude/CLAUDE.md "澄清/审查触发判据" and run only the
+      subtask) per the bundled 3-tier clarification gate and run only the
       layers whose gate fires. Each layer's command is `/discuss-strategic`,
       `/discuss-phase`, `/discuss-subtask`.
     checklist: []