verify-simplify

# verify-simplify workflow (v3) ## Overview 1-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 末尾 code-simplifier" onto harnessed runtime (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 config loads from `workflows/verify/simplify/workflow.yaml`; engine 4-level gate resolver evaluates `phase.is_final_step == true` via expr-eval — true 则 invoke `/code-simplifier` (移除重复 / 多余逻辑), false 则 skip。verify 链末尾步骤, sister verify-work v2 phase 08-code-simplifier verbatim 位置。 ## Capability refs Sister `workflows/capabilities.yaml` entries: - `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` ## Routing rules - ✅ **触发**: verify chain 末尾步骤 (所有其他 verify sub 已 ship, 准备 code 简化收尾) - ❌ **跳过**: verify chain 中间步骤 (避免过早简化干扰后续 review) ## How to invoke !`harnessed checkpoint intent verify-simplify` > The banner above (when present) means this invocation is REGISTERED with the engine (an intent marker) — not yet compliant: the steps below (prompt → spa...