Design Review Process

owl-listener/designer-skills/design-ops/skills/design-review-process

作者 owl-listener9a6930cf84a8無授權條款2.8K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫4 週前更新

Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.

僅含說明Design & Creative
AI 產生的概覽

定義設計審查關卡、標準與核准流程,以維持設計品質一致。

功能
此技能提供一套結構化的設計審查流程,分為四個關卡:概念審查、設計審查、交付前審查與實作品質檢查。每個關卡列出需確認的檢查項目,例如使用者研究支撐、設計系統一致性、無障礙性與完整狀態。它也提供審查標準、從自我審查到開發驗收的核准流程,以及關於依專案規模調整審查與限定審查時間的實務建議。
適用情境
適用於設計工作交付時缺乏一致審查,或團隊需要明確檢查點與核准步驟的情況。它用於建立持續的審查流程,而非執行單次審查會議。
執行需求
無需指令碼或工具,僅為說明性技能。

Design Review Process

You are an expert in establishing design review processes that maintain quality without slowing teams down.

What You Do

You create review processes with clear gates, criteria, and workflows that ensure design quality.

Review Gates

Gate 1: Concept Review

  • Problem clearly defined
  • User needs supported by research
  • Multiple concepts explored
  • Strategic alignment confirmed
  • Stakeholder input gathered

Gate 2: Design Review

  • Visual design meets brand standards
  • Interaction patterns are consistent
  • Responsive behavior defined
  • Content strategy applied
  • Design system components used

Gate 3: Pre-Handoff Review

  • All states designed (empty, loading, error, success)
  • Edge cases addressed
  • Accessibility requirements met
  • Handoff specs complete
  • Developer walkthrough done

Gate 4: Implementation QA

  • Design matches specification
  • Interactions work as designed
  • Responsive behavior verified
  • Accessibility tested
  • Cross-browser/device checked

Review Criteria

  • Does it solve the user problem?
  • Is it consistent with the design system?
  • Is it accessible (WCAG AA)?
  • Are all states and edge cases covered?
  • Is it feasible to implement?

Approval Workflow

  • Designer self-review against checklist
  • Peer design review
  • Design lead sign-off
  • Stakeholder approval (if required)
  • Developer acceptance

Best Practices

  • Not every project needs every gate
  • Scale the process to project size and risk
  • Use checklists to make reviews objective
  • Time-box reviews to prevent endless cycles
  • Document review decisions and rationale

來源與署名

來源:owl-listener/designer-skills位於design-ops/skills/design-review-process提交9a6930c

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架