plan-design-review

Audit design plans for gaps, explicit decisions, and production-ready UI criteria.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Kakarottoooo/onegent --skill plan-design-review-kakarottoooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-design-review
Source: https://github.com/Kakarottoooo/onegent/tree/main/.agents/skills/gstack/plan-design-review
Command: npx skills add https://github.com/Kakarottoooo/onegent --skill plan-design-review-kakarottoooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a rigorous, CEO-and-Eng-style critique of design plans to ensure decisions are explicit, complete, and production-ready before engineering begins.

Core Features & Use Cases

  • Evaluates plan design across readability, consistency, accessibility, empty states, error handling, responsive behavior, typography, and color usage.
  • Proposes missing decisions and improvements to reduce risk and clarify trade-offs for designers, PMs, and engineers.
  • Use cases include pre-implementation design reviews, design-system alignment, and cross-functional critique sessions.

Quick Start

Load the current plan at /plan-design-review and request a comprehensive design critique.

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 edge cases and accessibility before engineering?

To review a design plan for accessibility and edge cases, audit the plan to ensure explicit decisions are documented for empty states, error handling, and responsive behavior. This validates that acceptance criteria and constraints are complete prior to development.

What is a UX critique and how does it improve production-ready UI?

A UX critique evaluates design plans to identify gaps and raise the bar for production-ready UI. It ensures decisions are explicit and traceable, validating that typography, color usage, and interactions meet design-system standards.

How do I ensure design tokens map correctly to components in a plan review?

To ensure design tokens map correctly to components during a plan review, validate that the plan describes outcomes, constraints, and acceptance criteria with traceable rationale. This confirms token-to-component alignment before engineering begins.

Can I use this design review process for cross-functional critique sessions with PMs and engineers?

Yes, you can use this design review process for cross-functional critique sessions with PMs and engineers. It proposes missing decisions and improvements to reduce risk, clarify trade-offs, and align design-system decisions across teams.

What should a design plan include to pass a comprehensive design review?

To pass a comprehensive design review, a design plan must include clear criteria on decision completeness, edge-case handling, and traceable rationale. It needs explicit outcomes, constraints, acceptance criteria, and mappings for responsiveness and interactions.

Why does my design plan fail production readiness checks before development?

Your design plan fails production readiness checks when it lacks explicit decisions for empty states, accessibility, and responsive behavior. A rigorous critique identifies these gaps and missing trade-offs to ensure production-ready UI.