plan-design-review

Audit design plans and surface missing decisions with recommendations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans often lack explicit design decisions, leaving teams guessing on intent and increasing the risk of rework during implementation. This skill audits a design plan to surface gaps and propose concrete improvements before any UI work starts.

Core Features & Use Cases

  • Surface missing design decisions (scope, empty states, accessibility, responsive behavior, edge cases) and propose concrete changes.
  • Provide rationale for each recommended decision and link to design principles.
  • Serve as a critical partner in plan reviews for UI/UX projects, design systems, and governance documents, ensuring alignment before engineering starts.

Quick Start

Analyze the plan and return a prioritized list of missing decisions with actionable recommendations.

Frequently Asked Questions about plan-design-review

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

FAQPage Schema
How do I find missing design decisions in a UI/UX plan?

A design plan review identifies missing decisions regarding scope, empty states, accessibility, and edge cases. It audits the document to surface gaps and outputs a structured list with concrete recommendations and a completeness rating scale.

What is a design plan review and how does it work?

A design plan review evaluates UI/UX documents to identify undefined scope and edge cases. It analyzes the plan to output a prioritized list of missing decisions, actionable recommendations, rationale, and a rating scale for completeness.

How do I check if my design system covers edge cases and accessibility?

Checking if a design system covers edge cases and accessibility requires auditing the plan for explicit decisions on these elements. The review identifies gaps and proposes concrete changes aligned with design principles to ensure completeness.

Can I use this to review responsive behavior in governance documents?

Yes, you can review responsive behavior in governance documents by analyzing the plan for explicit design decisions. The process identifies missing definitions for responsiveness and outputs actionable recommendations to fill those gaps.

What is the best way to prevent design rework during implementation?

The best way to prevent design rework is to audit the plan for missing decisions before UI work starts. Identifying gaps in scope, empty states, and edge cases provides actionable recommendations to ensure alignment.

Why does my UI/UX project plan lack clear design intent?

A UI/UX project plan lacks clear design intent when it omits explicit design decisions for scope and edge cases. Conducting a plan review surfaces these gaps and provides rationale for recommended changes to ensure teams understand expected behavior.