design-review
Design Review (the review lane)
Most design work is improving something that already exists, not starting from a blank page. This is the review-only lane: it takes an existing artefact — a screenshot, a live URL, a prototype, or existing code/markup — and runs it through the same reviewers and reconciliation the full pipeline uses, but without discovery, strategy, design, or build.
It's the counterpart to the build lane. The build lane asks "what are we designing?" and creates. The review lane asks "what are we evaluating?" and critiques.
When to Use
Route here, instead of the build pipeline, when the user already has something:
- "Review / audit / critique this [screen / page / app / flow / component]"
- "What's wrong with this?" / "How can I improve this?" / "Is this accessible?"
- They share a screenshot, a URL, or point at existing code/markup
- They want a usability, accessibility, or craft assessment of work that already exists
If the user wants to build something new, use the normal pipeline (design-discovery → …). If it's genuinely unclear which they want, ask one question: "Do you want me to review something you already have, or design something new?"