design-review

Reviews design artifacts and defines buildable slices in a persistent backlog.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill design-review-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/design-review
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill design-review-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo builders lack the specialist review a real team provides, so designs reach build with hidden data gaps, uncovered process steps, and vaguely defined work. This Skill runs an iterative review loop between the design artifact and the build decision, refining screens, defining slices, and maintaining a backlog until enough slices reach Ready state to start building. ## Core Features & Use Cases - Multi-lens review: Applies PM, tech lead, and data lenses to every screen, with an optional four-agent parallel mode (UX, data, process, scope specialists) in Claude Code. - Slice definition and gating: Defines units of work with plain-language and technical descriptions, anchors, done criteria, quality contracts, and a strict Ready checklist. - Persistent backlog: Maintains docs/backlog.md with slice statuses, a data questions log, review rounds, and a decisions changelog readable by anyone outside the conversation. - Use Case: After a design sprint produces HTML screens, run a review round to classify findings, trigger research spikes, check process coverage against the to-be map, and promote the first coherent set of slices to Ready so build can begin. ## Quick Start Run a design review round on the screens in docs/design and update the backlog with any slices that are ready to build.

Frequently Asked Questions about design-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know when a design slice is ready to build?

A slice reaches Ready when it has plain-language and technical descriptions, clear design and process anchors, verifiable done criteria, a quality contract, a self-verification checklist, resolved dependencies, and no open spikes. The solo confirms it is clear enough to hand to a builder.

How does the multi-agent design review work in Claude Code?

Four specialist agents (UX, data, process, scope) run in parallel, each receiving only the artifacts it needs. The orchestrator then performs cross-signal analysis, prioritizing elements flagged independently by more than one agent.

Does design review work in Cursor as well as Claude Code?

Yes. In Cursor the same review steps run sequentially with a single model, and the browser preview verification pass is skipped. The multi-agent orchestrator and preview inspection are Claude Code only.

What happens if there is no to-be process map before review?

The review stops before evaluating slices. The process map is the contract that determines whether the design covers the right steps, so discovery must produce it first; every slice must anchor to a process step.

When should build start during design review?

Build starts when a coherent set of Ready slices forms a meaningful first vertical slice through the system, not when the entire design is finished. Review continues in parallel on the remaining slices.