plan-design-review

Analyze UI design plans and output questions, recommendations, and TODOs.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/TimHL5/carousel --skill plan-design-review-timhl5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-design-review
Source: https://github.com/TimHL5/carousel/tree/main/.claude/skills/gstack/plan-design-review
Command: npx skills add https://github.com/TimHL5/carousel --skill plan-design-review-timhl5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews plan documents to ensure design decisions are explicit, actionable, and testable before implementation, reducing ambiguity and rework.

Core Features & Use Cases

  • Surface gaps in design decisions and rationale that could derail delivery.
  • Propose precise questions in a standardized AskUserQuestion format to elicit decisions.
  • Generate TODOs, risk flags, and decision records to guide implementation and handoffs.

Quick Start

Provide a complete critique of the plan and output a structured design-review report that can be used to tighten the plan.

Frequently Asked Questions about plan-design-review

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

FAQPage Schema
How do I review a UI design plan before implementation?

To review a UI design plan, analyze the document to surface gaps and missing decisions, outputting clear questions, TODOs, and risk flags to ensure explicit user journeys, empty states, and accessibility before implementation.

What is design plan critique and why is it needed?

Design plan critique is the process of evaluating design decisions to ensure they are explicit, actionable, and testable. It is needed to reduce ambiguity and rework by surfacing rationale gaps before implementation begins.

How do I check if my design plan covers accessibility and empty states?

Checking accessibility and empty states involves analyzing the UI plan to verify these considerations are explicitly defined, generating structured ASK-style questions and TODOs for any missing design decisions or responsive behavior gaps.

Can I generate actionable TODOs and risk flags from a design document?

Yes, you can generate actionable TODOs and risk flags by analyzing the design plan to identify missing decisions, outputting a structured design-review report with precise questions and decision records to guide implementation and handoffs.

Does this design review process work without external dependencies?

Yes, the design review process works without external dependencies, analyzing UI plans independently to output clear questions, recommendations, and TODOs in a consistent ASK-style format for explicit decision tracking.

What is the best way to align a UI plan with a DESIGN.md file?

The best way to align a UI plan with a DESIGN.md file is to analyze the plan for explicit decisions, ensuring its user journeys, interactions, and system constraints match the documented design system requirements before implementation.