Design Critique
Run structured design critiques with observation-based feedback and captured action items instead of vague opinions.
Overview
Design Critique is an agent skill most often used in Build (also Validate prototype review and Ship review) that structures design critiques into timed rounds with actionable feedback formats and captured action items.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill design-critiqueWhat is this skill?
- Five-phase session flow: Present, Clarify, feedback rounds, Discuss, Capture
- Feedback language: I notice / I wonder / What if / I think…because
- Pre-critique prep: goals, constraints, audience, and scoped feedback needs
- Critique types: desk, team, cross-team, and stakeholder review
- Post-critique: owner-assigned action items and optional follow-up review
- Five timed critique segments in the default framework (Present through Capture)
- Four feedback sentence starters: I notice, I wonder, What if, I think…because
Adoption & trust: 584 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have design work in review but feedback turns subjective, scattered, or harsh without clear next steps.
Who is it for?
Solo builders or tiny teams scheduling a focused crit on UI, flows, or copy with defined goals and feedback scope.
Skip if: Replacing user research or heuristic audits when you have no design artifact to walk through yet.
When should I use this skill?
You are about to review design work with others and need rules, timing, and phrasing that keep feedback constructive.
What do I get? / Deliverables
You leave with documented observations, prioritized action items with owners, and a follow-up plan when the skill’s After the Critique steps are applied.
- Critique session structure with categorized feedback
- Action items with owners and deadlines
- Optional follow-up review plan
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf on build/frontend because critiques most often happen on in-progress UI and flows before ship. Frontend is where layout, copy, and interaction decisions are reviewed with the team.
Where it fits
Walk a clickable prototype through Present and Clarify before committing to full UI build.
Run a team crit on navigation and copy with feedback scoped to flow and hierarchy only.
Hold a stakeholder review that ends in captured decisions instead of open-ended debate.
How it compares
Use as a facilitation playbook for live critique sessions, not as a Nielsen-style expert audit checklist.
Common Questions / FAQ
Who is design-critique for?
Designers, founders, and indie builders who need structured group or 1-on-1 feedback on in-progress product design.
When should I use design-critique?
During validate when prototyping needs directional feedback, during build while refining UI and flows, and before ship when stakeholders need a decision-oriented review.
Is design-critique safe to install?
It is procedural facilitation guidance with no required shell or network access; review the Security Audits panel on this page before installing any skill in your agent.
SKILL.md
READMESKILL.md - Design Critique
# 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 1. **Present** (5 min) — Designer walks through the work and goals 2. **Clarify** (5 min) — Questions to understand, not judge 3. **Feedback rounds** — Structured by category or priority 4. **Discuss** — Open conversation on key tensions 5. **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