360 Secure SkillHub
360 安全技能中心

design-review-process

提供设计评审流程框架,包括概念、设计、交付前和实施后四类评审门禁,评审标准、审批工作流与最佳实践,帮助团队在保证质量的同时避免流程拖慢交付。

Owl-Listener
热度 23.76
最近更新 2026-10-19 04:18:18
分类:协作依赖:纯提示词应用场景:工作流 / 任务管理

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add owl-listener/designer-skills/design-review-process
Metadata
name
design-review-process
description
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.

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