verify-designlisted

# verify-design workflow (v3) ## Overview 1-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 可选 /design-review" onto harnessed runtime (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 config loads from `workflows/verify/design/workflow.yaml`; engine 4-level gate resolver evaluates `phase.has_design_changes == true` via expr-eval — true 则 invoke gstack `/design-review` (设计系统一致性 + AI 审美问题识别), false 则 skip。 ## Capability refs Sister `workflows/capabilities.yaml` entries: - `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` ## Routing rules (bundled web-design routing — `workflows/judgments/web-design-routing.yaml`) - 默认主方案 → `ui-ux-pro-max` (数据驱动、标准化、可解释) - 创意补充 / 不要 AI 味 → `frontend-design` - 用户明示「独特 / 不要 AI 感」→ frontend-design 主导, 否则 ui-ux-pro-max 优先 ## How to invoke Use the Bash tool to run: