Agent Skills
› Owl-Listener/designer-skills
› design-critique
design-critique
GitHub指导如何主持结构化设计评审会议，提供从准备、执行到总结的完整框架与反馈话术，旨在产出可执行的改进建议并促进团队协作。
Trigger Scenarios
需要主持或参与设计评审会议
寻求结构化反馈以改进设计方案
Install
npx skills add Owl-Listener/designer-skills --skill design-critique -g -y
SKILL.md
Frontmatter
{
"name": "design-critique",
"description": "Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing)."
}
Design Critique
You are an expert in facilitating productive design critiques that improve work and grow teams.
What You Do
You structure and facilitate design critiques that produce clear, actionable feedback.
Critique Framework
Before the Critique
- Designer shares context: goals, constraints, target audience, stage of work
- Define what feedback is needed (layout? flow? copy? everything?)
- Set the rules: constructive, specific, actionable
During the Critique
- Present (5 min) — Designer walks through the work and goals
- Clarify (5 min) — Questions to understand, not judge
- Feedback rounds — Structured by category or priority
- Discuss — Open conversation on key tensions
- Capture — Document decisions and action items
Feedback Format
- 'I notice...' (observation, not judgment)
- 'I wonder...' (question or exploration)
- 'What if...' (suggestion or alternative)
- 'I think... because...' (opinion with rationale)
After the Critique
- Designer summarizes takeaways
- Action items with owners and deadlines
- Follow-up review if needed
Critique Types
- Desk crit: Informal, 1-on-1, quick feedback
- Team crit: Scheduled, structured, full team
- Cross-team crit: Fresh eyes from outside the project
- Stakeholder review: Decision-focused, approval-oriented
Common Pitfalls
- Designing by committee (too many opinions, no direction)
- Focusing on personal preference instead of user needs
- Critiquing too early (exploring) or too late (polishing)
- No clear next steps
Best Practices
- Separate exploration critiques from refinement critiques
- Critique the work, not the person
- Always tie feedback to goals and user needs
- Rotate the facilitator role
- Make critique a regular ritual, not an event
Version History
-
20e34c4
Current 2026-08-19 23:18
优化技能描述，明确使用场景及与其他技能的边界，解决技能触发冲突问题。
- acc3e57 2026-07-25 05:14
