harnessed 4.7.0 → 4.8.0

package/workflows/verify/design/SKILL.zh-Hans.md

@@ -0,0 +1,74 @@
+---
+name: verify-design
+description: |
+  Stage ④.f verify 子工作流 — gstack /design-review 设计系统一致性 + AI 审美问题识别
+  (has_design_changes 触发, 可选 conditional; bundled verify-stage optional /design-review step).
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (gstack-design-review + ui-ux-pro-max + frontend-design) + 1 phase (gate ref has_design_changes
+  conditional)。Triggered by harnessed CLI `harnessed verify-design --phase <num>` or slash
+  command `/verify-design` after `harnessed setup`.
+trigger_phrases:
+  - "verify design"
+  - "设计审查"
+  - "design review"
+  - "gstack design review"
+  - "跑 verify-design"
+---
+
+# verify-design 工作流 (v3)
+
+## 概览
+
+1-phase 子工作流，将 CLAUDE.md「Verify 阶段 — 可选 /design-review」映射到 harnessed
+运行时（Phase v3.0-3.4 W0.13c — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 +
+Pattern A sub-workflow ship）。
+
+| phase | id | upstream | model | capability | gate |
+| ----- | -- | -------- | ----- | ---------- | ---- |
+| 1 | `01-design-review` | gstack | sonnet | `{{ capabilities.gstack-design-review.cmd }}` | `judgments.stage-routing.verify-design-changes.fires` |
+
+Per-phase 配置从 `workflows/verify/design/workflow.yaml` 加载；引擎 4-level gate
+resolver 通过 expr-eval 计算 `phase.has_design_changes == true` — 为 true 则调用 gstack
+`/design-review`（设计系统一致性 + AI 审美问题识别），为 false 则跳过。
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` 条目：
+- `gstack-design-review` — Bucket 3 治理关卡 (impl: gstack, cmd: /design-review,
+  fires_when: has_design_changes)
+- `ui-ux-pro-max` — Bucket 2 special-purpose (impl: gstack, 默认主方案 数据驱动)
+- `frontend-design` — Bucket 2 special-purpose (impl: gstack, UI 创意 / 装饰补充)
+
+## Gate ref
+
+Sister `workflows/judgments/stage-routing.yaml`：
+- `verify-design-changes.fires` — `phase.stage == 'verify' and phase.has_design_changes == true`
+
+## 路由规则（bundled web-design routing — `workflows/judgments/web-design-routing.yaml`）
+
+- 默认主方案 → `ui-ux-pro-max`（数据驱动、标准化、可解释）
+- 创意补充 / 不要 AI 味 → `frontend-design`
+- 用户明示「独特 / 不要 AI 感」→ frontend-design 主导，否则 ui-ux-pro-max 优先
+
+## 调用方式
+
+使用 Bash 工具运行：
+
+```bash
+echo "$ARGUMENTS" | harnessed run verify-design --task-stdin
+```
+
+若 `$ARGUMENTS` 为空，运行 `harnessed run verify-design`（不带 stdin pipe）。
+
+执行完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段操作。是否继续调用，请根据对话上下文自行判断——该提示仅供参考，并非强制指令。
+
+<!-- harnessed-generated:v3.4.4 -->
+
+## 参考资料
+
+- D-04 Stage ④ Verify 7 sub 分解
+- D-12 gstack 治理关卡可选
+- workflows/judgments/web-design-routing.yaml — ui-ux-pro-max 默认 + frontend-design 补充
+- workflows/capabilities.yaml — gstack-design-review / ui-ux-pro-max / frontend-design
+- workflows/judgments/stage-routing.yaml — verify-design-changes trigger
+- workflows/verify-work/workflow.yaml v2 SHIPPED phase 07-design-review-conditional sister verbatim

package/workflows/verify/multispec/SKILL.zh-Hans.md

@@ -0,0 +1,88 @@
+---
+name: verify-multispec
+description: |
+  Stage ④.h verify 子工作流 — 4-specialist Agent Team Pattern C 多维度审查（关键发布 /
+  大重构 PR 升级，code-review + gstack-review + gstack-cso + gstack-qa 4 teammate 互相
+  SendMessage 质询，NOT fire-and-forget subagent fan-out；bundled Agent Teams Pattern C
+  routing）。Cleanup 必跑：shutdown_request + TeamDelete（bundled cleanup discipline）。
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (agent-teams 3 + 4 specialist capability) + 2 phase (01-team-create on critical-release
+  invoke / 02-team-cleanup mandatory shutdown)。
+  Triggered by slash command
+  `/verify-multispec` after `harnessed setup`.
+trigger_phrases:
+  - "verify multispec"
+  - "4-specialist Agent Team"
+  - "Pattern C 多维度审查"
+  - "critical release review"
+  - "跑 verify-multispec"
+---
+
+# verify-multispec 工作流 (v3)
+
+## 概览
+
+2-phase 子工作流，将 CLAUDE.md「Verify 阶段 — 关键发布 / 大重构 PR 升级 Agent Team
+Pattern C」映射到 harnessed 运行时（Phase v3.0-3.4 W0.13e — D-04 Stage ④ Verify 7 sub +
+D-11 Agent Teams + Pattern A sub-workflow ship）。
+
+| phase | id | upstream | model | capability | gate / on |
+| ----- | -- | -------- | ----- | ---------- | --------- |
+| 1 | `01-team-create` | claude-platform | opus | `{{ capabilities.agent-teams-create.cmd }}` | `parallelism: agent-teams-upgrade.fires`; `on: is_major_release OR is_large_refactor → invoke` |
+| 2 | `02-team-cleanup` | claude-platform | haiku | `{{ capabilities.agent-teams-shutdown.cmd }}` | mandatory 防呆清单 |
+
+Per-phase 配置从 `workflows/verify/multispec/workflow.yaml` 加载；phase 01 通过 TeamCreate 创建 4
+个 teammate（code-review + gstack-review + gstack-cso + gstack-qa），teammate 互相
+SendMessage 质询 findings 是否真问题（NOT fire-and-forget）；phase 02 必跑 shutdown_request
++ TeamDelete（bundled Agent Teams cleanup discipline）。
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` 条目：
+- `agent-teams-create` — Bucket 5 Agent Teams (impl: claude-platform, cmd: TeamCreate)
+- `agent-teams-send-message` — Bucket 5 Agent Teams (impl: claude-platform, cmd: SendMessage)
+- `agent-teams-shutdown` — Bucket 5 Agent Teams (impl: claude-platform, cmd: TeamDelete)
+- `code-review` — Bucket 1 mattpocock (teammate 1)
+- `gstack-review` — Bucket 3 治理关卡 (teammate 2 Paranoid Staff Engineer)
+- `gstack-cso` — Bucket 3 治理关卡 (teammate 3 安全审查)
+- `gstack-qa` — Bucket 3 治理关卡 (teammate 4 端到端 QA)
+
+## Parallelism + on gate refs
+
+Sister `workflows/judgments/parallelism-gate.yaml`：
+- `agent-teams-upgrade.fires` — 5 OR-chain（teammate_send_message_needed / subagent_context_overflow /
+  shared_task_list / opposing_hypothesis_debate / fullstack_three_way）
+
+Phase 级 `on` 子句（critical-release 升级触发）：
+- `if: phase.is_major_release == true or phase.is_large_refactor == true` → `action: invoke`
+- else → `action: skip`
+
+## 路由规则（bundled Agent Teams routing — `workflows/judgments/parallelism-gate.yaml`）
+
+- ✅ **触发**：关键发布 / 大重构 PR（≥3 specialist 需互相质询而非 fire-and-forget）
+- ❌ **跳过**：常规 PR / 单点任务（sister verify-code-review fan-out + verify-paranoid 已够用且省 token）
+- **Token 估算前置条件**：`team_cost < 2 × subagent_cost`（engine-level check；bundled cost guideline）
+- **Cleanup 必跑**：phase 02-team-cleanup `agent-teams-shutdown` 必跑（bundled cleanup discipline）
+
+## 调用方式
+
+使用 Bash 工具运行：
+
+```bash
+echo "$ARGUMENTS" | harnessed run verify-multispec --task-stdin
+```
+
+若 `$ARGUMENTS` 为空，运行 `harnessed run verify-multispec`（不带 stdin pipe）。
+
+执行完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段操作。是否继续调用，请根据对话上下文自行判断——该提示仅供参考，并非强制指令。
+
+<!-- harnessed-generated:v3.4.4 -->
+
+## 参考资料
+
+- D-04 Stage ④ Verify 7 sub 分解
+- D-11 Agent Teams 4-specialist Pattern C upgrade
+- workflows/capabilities.yaml — agent-teams-{create,send-message,shutdown} + 4 specialist
+- workflows/judgments/stage-routing.yaml — verify-multispec-critical-release trigger
+- workflows/judgments/parallelism-gate.yaml — agent-teams-upgrade.fires (5 OR-chain)
+- workflows/verify-work/workflow.yaml v2 SHIPPED phase 09-agent-team-multispecialist sister verbatim

package/workflows/verify/paranoid/SKILL.zh-Hans.md

@@ -0,0 +1,74 @@
+---
+name: verify-paranoid
+description: |
+  Stage ④.c verify 子工作流 — gstack /review Paranoid Staff Engineer 关键模块 PR 前强制
+  (bundled gstack governance gate — mandatory before critical-module PR)。Gate:
+  judgments.stage-routing.verify-paranoid-critical.fires (phase.is_critical_module == true) —
+  默认 critical fire only；非关键模块 skip。
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (gstack-review) + 1 phase (gate ref is_critical_module conditional)。
+  Triggered by slash command
+  `/verify-paranoid` after `harnessed setup`.
+trigger_phrases:
+  - "verify paranoid"
+  - "paranoid staff engineer review"
+  - "关键模块审查"
+  - "gstack review"
+  - "跑 verify-paranoid"
+---
+
+# verify-paranoid 工作流 (v3)
+
+## 概览
+
+1-phase 子工作流，将 CLAUDE.md「gstack 治理关卡 🔒 关键模块 PR 前强制 — `/review`」
+映射到 harnessed 运行时（Phase v3.0-3.4 W0.12 — D-04 Stage ④ Verify 7 sub + D-12 gstack
+治理关卡 + Pattern A sub-workflow ship）。
+
+| phase | id | upstream | model | capability | gate |
+| ----- | -- | -------- | ----- | ---------- | ---- |
+| 1 | `01-review` | gstack | opus | `{{ capabilities.gstack-review.cmd }}` | `judgments.stage-routing.verify-paranoid-critical.fires` |
+
+Per-phase 配置从 `workflows/verify/paranoid/workflow.yaml` 加载；引擎 4-level gate
+resolver 通过 expr-eval 计算 `phase.is_critical_module == true` — 为 true 则调用 gstack
+`/review`，为 false 则跳过（chain_isolation 3 铁律 R20.16 sister verify-work v2 phase 04）。
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` 条目：
+- `gstack-review` — Bucket 3 治理关卡 (impl: gstack, cmd: /review,
+  fires_when: phase.is_critical_module == true)
+
+## Gate ref
+
+Sister `workflows/judgments/stage-routing.yaml`：
+- `verify-paranoid-critical.fires` — `phase.stage == 'verify' and phase.is_critical_module == true`
+  （默认 critical fire only；普通 PR 应跳过 — gstack-review 是 Paranoid Staff Engineer 重武器）
+
+## 路由规则（sister CLAUDE.md「gstack 治理关卡」）
+
+- ✅ **触发**：关键模块 PR 前（auth / payment / data migration / core algorithm 等）
+- ❌ **跳过**：常规 PR / docs / config / 非核心 module
+
+## 调用方式
+
+使用 Bash 工具运行：
+
+```bash
+echo "$ARGUMENTS" | harnessed run verify-paranoid --task-stdin
+```
+
+若 `$ARGUMENTS` 为空，运行 `harnessed run verify-paranoid`（不带 stdin pipe）。
+
+执行完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段操作。是否继续调用，请根据对话上下文自行判断——该提示仅供参考，并非强制指令。
+
+<!-- harnessed-generated:v3.4.4 -->
+
+## 参考资料
+
+- D-04 Stage ④ Verify 7 sub 分解
+- D-12 gstack 治理关卡强制
+- workflows/capabilities.yaml — gstack-review
+- workflows/judgments/stage-routing.yaml — verify-paranoid-critical trigger
+- workflows/defaults.yaml — ralph_max_iterations.verify-paranoid.* values (W2.2 backfill)
+- workflows/verify-work/workflow.yaml v2 SHIPPED phase 04-gstack-review-conditional sister verbatim

package/workflows/verify/progress/SKILL.zh-Hans.md

@@ -0,0 +1,69 @@
+---
+name: verify-progress
+description: |
+  Stage ④.a verify 子工作流 — gsd-verify-work + gsd-progress 必跑串行（verify-work 起点）
+  + planning-with-files progress.md 持久化（bundled verify-stage cadence — mandatory serial:
+  gsd-verify-work UAT-driven acceptance + gsd-progress 状态同步，顺序不可调换）。
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (gsd-verify-work + gsd-progress + planning-with-files) + 3 phases (serial 01→02 + persist
+  progress.md sink)。Triggered by harnessed CLI `harnessed verify-progress --phase <num>` or
+  slash command `/verify-progress` after `harnessed setup`.
+trigger_phrases:
+  - "verify progress"
+  - "进度同步"
+  - "gsd verify work"
+  - "ROADMAP 状态同步"
+  - "跑 verify-progress"
+---
+
+# verify-progress 工作流 (v3)
+
+## 概览
+
+3-phase 子工作流，将 CLAUDE.md「Verify 阶段 — 必跑串行」起点映射到 harnessed 运行时
+（Phase v3.0-3.4 W0.10 — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 ref + Pattern A
+sub-workflow ship）。
+
+| phase | id | upstream | model | capability / invokes | mode / artifacts |
+| ----- | -- | -------- | ----- | -------------------- | ---------------- |
+| 1 | `01-gsd-verify-work` | gsd | sonnet | `{{ capabilities.gsd-verify-work.cmd }}` | serial — UAT-driven acceptance |
+| 2 | `02-gsd-progress` | gsd | haiku | `{{ capabilities.gsd-progress.cmd }}` | serial — ROADMAP/STATE/REQUIREMENTS 同步 |
+| 3 | `03-progress-update` | planning-with-files | haiku | `{{ capabilities.planning-with-files.cmd }}` + `invokes: /plan` | `artifacts_expected: [progress.md]` |
+
+Per-phase 配置从 `workflows/verify/progress/workflow.yaml` 加载；引擎通过 `@anthropic-ai/claude-agent-sdk` 0.3.142+ 以串行模式将每个 phase 作为子 agent 启动（顺序锁定 —
+gsd-verify-work UAT 必先于 gsd-progress 状态同步）。
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` 条目：
+- `gsd-verify-work` — Bucket 2 special-purpose (impl: gsd, cmd: /gsd-verify-work)
+- `gsd-progress` — Bucket 2 special-purpose (impl: gsd, cmd: /gsd-progress)
+- `planning-with-files` — Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan)
+
+## 路由规则（sister CLAUDE.md「Verify 阶段」）
+
+总 fire 当 `phase.stage == 'verify'`（sister `workflows/judgments/stage-routing.yaml`
+verify-progress-always trigger）。无 skip 条件 — verify-work 起点必跑。
+
+## 调用方式
+
+使用 Bash 工具运行：
+
+```bash
+echo "$ARGUMENTS" | harnessed run verify-progress --task-stdin
+```
+
+若 `$ARGUMENTS` 为空，运行 `harnessed run verify-progress`（不带 stdin pipe）。
+
+执行完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段操作。是否继续调用，请根据对话上下文自行判断——该提示仅供参考，并非强制指令。
+
+<!-- harnessed-generated:v3.4.4 -->
+
+## 参考资料
+
+- D-04 Stage ④ Verify 7 sub 分解
+- D-12 gstack 治理关卡 ref（verify-paranoid 后续 sub）
+- workflows/capabilities.yaml — gsd-verify-work / gsd-progress / planning-with-files
+- workflows/judgments/stage-routing.yaml — verify-progress-always trigger
+- workflows/defaults.yaml — ralph_max_iterations.verify-progress.* values (W2.2 backfill)
+- workflows/verify-work/workflow.yaml v2 SHIPPED phase 01-02 sister verbatim pattern

package/workflows/verify/qa/SKILL.zh-Hans.md

@@ -0,0 +1,76 @@
+---
+name: verify-qa
+description: |
+  Stage ④.d 验证子工作流 — gstack /qa 端到端 QA 验收 (has_ui_changes 触发, 可选 conditional;
+  捆绑 verify 阶段可选 /qa 步骤).
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (gstack-qa + playwright-cli + playwright-test + webapp-testing) + 1 phase (gate ref
+  has_ui_changes conditional)。
+  Triggered by slash command
+  `/verify-qa` after `harnessed setup`.
+trigger_phrases:
+  - "verify qa"
+  - "端到端 QA"
+  - "E2E 验收"
+  - "gstack qa"
+  - "跑 verify-qa"
+---
+
+# verify-qa workflow (v3)
+
+## 概览
+
+1-phase 子工作流，将 CLAUDE.md "Verify 阶段 — 可选 /qa" 映射到 harnessed 运行时
+(Phase v3.0-3.4 W0.13a — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 + Pattern A
+sub-workflow ship)。
+
+| phase | id | upstream | model | capability | gate |
+| ----- | -- | -------- | ----- | ---------- | ---- |
+| 1 | `01-qa` | gstack | sonnet | `{{ capabilities.gstack-qa.cmd }}` | `judgments.stage-routing.verify-qa-ui.fires` |
+
+Per-phase 配置从 `workflows/verify/qa/workflow.yaml` 加载；引擎 4-level gate resolver
+通过 expr-eval 计算 `phase.has_ui_changes == true` — true 则调用 gstack `/qa` (端到端
+QA 验收 + UI dogfood)，false 则跳过。
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` 条目：
+- `gstack-qa` — Bucket 3 治理关卡 (impl: gstack, cmd: /qa, fires_when: has_ui_changes)
+- `playwright-cli` — Bucket 2 special-purpose (impl: npm-cli, browser_probe)
+- `playwright-test` — Bucket 2 special-purpose (impl: npm-cli, e2e_test typescript)
+- `webapp-testing` — Bucket 2 special-purpose (impl: gstack, e2e_test python)
+
+## Gate ref
+
+Sister `workflows/judgments/stage-routing.yaml`：
+- `verify-qa-ui.fires` — `phase.stage == 'verify' and phase.has_ui_changes == true`
+
+## 路由规则（捆绑 web-testing 路由 — `workflows/judgments/web-testing-routing.yaml`）
+
+- 写测试 提交 repo / CI 跑 → `@playwright/test` (默认 frontend/e2e/*.spec.ts)
+- 探查 / 调试 / 一次性确认 → `playwright-cli` (token 最省)
+- setup 需 Python 后端 (Tortoise ORM / pandas) → `webapp-testing` skill
+- 性能 / a11y / 内存诊断 → 不在此子工作流，用 `chrome-devtools-mcp`
+
+## 调用方式
+
+使用 Bash 工具运行：
+
+```bash
+echo "$ARGUMENTS" | harnessed run verify-qa --task-stdin
+```
+
+若 `$ARGUMENTS` 为空，则运行 `harnessed run verify-qa`（不接管道输入）。
+
+完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段。是否调用取决于对话上下文 — 该提示仅供参考，非强制指令。
+
+<!-- harnessed-generated:v3.4.4 -->
+
+## 参考资料
+
+- D-04 Stage ④ Verify 7 sub 分解
+- D-12 gstack 治理关卡可选
+- workflows/judgments/web-testing-routing.yaml — 三层职责矩阵 (脑 / 手 / 筋骨)
+- workflows/capabilities.yaml — gstack-qa / playwright-cli / playwright-test / webapp-testing
+- workflows/judgments/stage-routing.yaml — verify-qa-ui trigger
+- workflows/verify-work/workflow.yaml v2 SHIPPED phase 05-qa-conditional sister verbatim

package/workflows/verify/security/SKILL.zh-Hans.md

@@ -0,0 +1,70 @@
+---
+name: verify-security
+description: |
+  Stage ④.e 验证子工作流 — gstack /cso 安全审查 OWASP/auth/secrets (has_auth_or_secrets
+  触发, 可选 conditional; 捆绑 verify 阶段可选 /cso 步骤).
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (gstack-cso) + 1 phase (gate ref has_auth_or_secrets conditional)。
+  Triggered by slash command
+  `/verify-security` after `harnessed setup`.
+trigger_phrases:
+  - "verify security"
+  - "安全审查"
+  - "OWASP audit"
+  - "gstack cso"
+  - "跑 verify-security"
+---
+
+# verify-security workflow (v3)
+
+## 概览
+
+1-phase 子工作流，将 CLAUDE.md "Verify 阶段 — 可选 /cso" 映射到 harnessed 运行时
+(Phase v3.0-3.4 W0.13b — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 + Pattern A
+sub-workflow ship)。
+
+| phase | id | upstream | model | capability | gate |
+| ----- | -- | -------- | ----- | ---------- | ---- |
+| 1 | `01-cso` | gstack | opus | `{{ capabilities.gstack-cso.cmd }}` | `judgments.stage-routing.verify-security-secrets.fires` |
+
+Per-phase 配置从 `workflows/verify/security/workflow.yaml` 加载；引擎 4-level gate
+resolver 通过 expr-eval 计算 `phase.has_auth_or_secrets == true` — true 则调用 gstack
+`/cso` (OWASP / auth / credentials / secrets 全面审查)，false 则跳过。
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` 条目：
+- `gstack-cso` — Bucket 3 治理关卡 (impl: gstack, cmd: /cso,
+  fires_when: phase.stage == 'verify' AND phase.has_auth_or_secrets == true)
+
+## Gate ref
+
+Sister `workflows/judgments/stage-routing.yaml`：
+- `verify-security-secrets.fires` — `phase.stage == 'verify' and phase.has_auth_or_secrets == true`
+
+## 路由规则
+
+- ✅ **触发**: auth flow / session / credentials / API keys / SQL injection 路径 / OWASP top 10 area
+- ❌ **跳过**: docs / 纯 UI styling / 内部 refactor / non-security PR
+
+## 调用方式
+
+使用 Bash 工具运行：
+
+```bash
+echo "$ARGUMENTS" | harnessed run verify-security --task-stdin
+```
+
+若 `$ARGUMENTS` 为空，则运行 `harnessed run verify-security`（不接管道输入）。
+
+完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段。是否调用取决于对话上下文 — 该提示仅供参考，非强制指令。
+
+<!-- harnessed-generated:v3.4.4 -->
+
+## 参考资料
+
+- D-04 Stage ④ Verify 7 sub 分解
+- D-12 gstack 治理关卡可选
+- workflows/capabilities.yaml — gstack-cso
+- workflows/judgments/stage-routing.yaml — verify-security-secrets trigger
+- workflows/verify-work/workflow.yaml v2 SHIPPED phase 06-cso-conditional sister verbatim

package/workflows/verify/simplify/SKILL.zh-Hans.md

@@ -0,0 +1,70 @@
+---
+name: verify-simplify
+description: |
+  Stage ④.g 验证子工作流 — code-simplifier 末尾串行 (移除重复 / 多余逻辑;
+  捆绑 verify 阶段节奏 — tail-step code-simplifier).
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (code-simplifier) + 1 phase (gate ref is_final_step 末尾串行)。
+  Triggered by slash command
+  `/verify-simplify` after `harnessed setup`.
+trigger_phrases:
+  - "verify simplify"
+  - "code simplify"
+  - "代码简化"
+  - "移除重复逻辑"
+  - "跑 verify-simplify"
+---
+
+# verify-simplify workflow (v3)
+
+## 概览
+
+1-phase 子工作流，将 CLAUDE.md "Verify 阶段 — 末尾 code-simplifier" 映射到 harnessed
+运行时 (Phase v3.0-3.4 W0.13d — D-04 Stage ④ Verify 7 sub + Pattern A sub-workflow ship)。
+
+| phase | id | upstream | model | capability | gate |
+| ----- | -- | -------- | ----- | ---------- | ---- |
+| 1 | `01-simplify` | mattpocock-skills | sonnet | `{{ capabilities.code-simplifier.cmd }}` | `judgments.stage-routing.verify-simplify-tail.fires` |
+
+Per-phase 配置从 `workflows/verify/simplify/workflow.yaml` 加载；引擎 4-level gate
+resolver 通过 expr-eval 计算 `phase.is_final_step == true` — true 则调用
+`/code-simplifier` (移除重复 / 多余逻辑)，false 则跳过。verify 链末尾步骤，
+sister verify-work v2 phase 08-code-simplifier verbatim 位置。
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` 条目：
+- `code-simplifier` — Bucket 1 mattpocock 高频招式 (impl: mattpocock-skills,
+  cmd: /code-simplifier, fires_when: stage=='verify' AND is_final_step)
+
+## Gate ref
+
+Sister `workflows/judgments/stage-routing.yaml`：
+- `verify-simplify-tail.fires` — `phase.stage == 'verify' and phase.is_final_step == true`
+
+## 路由规则
+
+- ✅ **触发**: verify chain 末尾步骤 (所有其他 verify sub 已 ship，准备 code 简化收尾)
+- ❌ **跳过**: verify chain 中间步骤 (避免过早简化干扰后续 review)
+
+## 调用方式
+
+使用 Bash 工具运行：
+
+```bash
+echo "$ARGUMENTS" | harnessed run verify-simplify --task-stdin
+```
+
+若 `$ARGUMENTS` 为空，则运行 `harnessed run verify-simplify`（不接管道输入）。
+
+完成后，Bash 输出会在 stderr 打印 `Next:` 提示，建议下一阶段。是否调用取决于对话上下文 — 该提示仅供参考，非强制指令。
+
+<!-- harnessed-generated:v3.4.4 -->
+
+## 参考资料
+
+- D-04 Stage ④ Verify 7 sub 分解
+- workflows/capabilities.yaml — code-simplifier
+- workflows/judgments/stage-routing.yaml — verify-simplify-tail trigger
+- workflows/defaults.yaml — ralph_max_iterations.verify-simplify.* values (W2.2 backfill)
+- workflows/verify-work/workflow.yaml v2 SHIPPED phase 08-code-simplifier sister verbatim