Prompt library
Ask critique questions that improve the work
Stage-gating the feedback type prevents the two classic critique failures: pixel-polishing a concept and re-opening strategy during polish. The strong-answer-versus-rationalization guide turns questions into calibration for the whole room, and the closing ritual converts talk into decisions.
DesignBrainstorm
Last reviewed July 17, 2026
The prompt
Generate critique questions for a design review.
The work being reviewed: {{work}}
Its stage: {{stage}}
Produce:
1. Stage check first: the feedback type this stage needs (direction feedback for early work, detail feedback for late work), and the 2 question types that are OFF LIMITS at this stage (pixel critique on a concept; strategy relitigation on a polish pass).
2. Ten questions in four lenses, labeled:
- Intent: what problem does this choice solve? (aimed at the biggest visible decisions)
- User: who might this exclude or confuse, and at which moment?
- Alternatives: what did you try and reject here, and why?
- Consequences: what does this pattern commit us to elsewhere in the product?
3. For each question: what a strong answer sounds like versus a rationalization, so the room can tell.
4. The 2 questions the presenting designer should ask the ROOM, because critique is bidirectional.
5. The closing ritual: how the session ends with owned decisions (keep, change, explore), not a pile of opinions.
Ban preference statements dressed as questions ("have you considered making it pop?").Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{work}} | What is being critiqued | the v2 dashboard concept |
| {{stage}} | How far along | early concept, second review |