verify-design

name: verify-design description: | Stage ④.f verify sub-workflow — 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 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)。

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

Orchestrated CC-natively. Do NOT pipe to harnessed run verify-design — that is the CI/headless path (an in-process SDK spawn that blocks the session, bypasses Agent Teams, and hangs when invoked from inside a Claude Code session).

Run the /verify-design slash command instead (generated by harnessed setup at ~/.claude/commands/verify-design.md). It drives the stage natively: harnessed gates → which subs fire, harnessed prompt <sub> → each spawn-ready prompt, then a CC-native subagent (Task / Agent tool) per fired sub, recording each outcome with harnessed checkpoint. The full state-machine steps live in ~/.claude/commands/verify-design.md; if that file is absent, follow that same gates → prompt → spawn → checkpoint sequence yourself.

References

• 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