plan-design-review

Review design plans and add missing design decisions before implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designer and product teams often ship plans without explicit design decisions, resulting in ambiguous scope and misaligned expectations. This skill identifies those gaps and adds missing design decisions to the PLAN before implementation.

Core Features & Use Cases

  • Rigorous gap analysis of design plans to surface missing decisions such as empty states, error handling, accessibility, responsive behavior, and edge-case handling.
  • Structured critique of plan decisions with rationale and concrete fixes, ensuring a cohesive user journey and design system alignment.
  • Interactive reviewer workflow that outputs a revised plan with explicit decisions and next steps ready for implementation.

Quick Start

Review a PLAN document and I will output a revised plan with design decisions added.

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 design plan for missing UI decisions before implementation?

To review a design plan for missing UI decisions, analyze the document against rigorous design principles covering UI hierarchy, empty states, accessibility, responsiveness, and edge-case handling. This gap analysis surfaces missing decisions and outputs a revised plan with explicit rationale and concrete next steps.

What is a design critique and how does it improve a product plan?

A design critique is a structured evaluation of a product plan that identifies ambiguous scope and missing decisions like error handling or responsive behavior. It improves the plan by adding explicit design decisions with rationale, ensuring a cohesive user journey and design system alignment before implementation begins.

Can I use design system principles to check for empty states and accessibility in my plan?

Yes, you can apply design system principles to check your plan for empty states and accessibility. The critique process rigorously evaluates these specific areas alongside UI hierarchy and responsiveness, adding explicit decisions and fixes to the revised plan to align with established design standards.

Does rigorous plan design review work for edge-case handling and responsive behavior?

Yes, rigorous plan design review works effectively for edge-case handling and responsive behavior. The critique process specifically targets these dimensions to surface missing decisions, delivering a revised plan with structured fixes and concrete next steps that ensure cohesive interactions across all viewport sizes.

What's the best way to fix ambiguous scope in a UI design plan?

The best way to fix ambiguous scope in a UI design plan is to perform a structured critique that identifies missing design decisions. By applying rigorous design principles across UI hierarchy and error handling, the review outputs a revised plan with explicit decisions and rationale ready for implementation.