plan-design-review

Review design plans to surface missing or ambiguous UX decisions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mmunro3318/3d-render-pipeline --skill plan-design-review-mmunro3318
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-design-review
Source: https://github.com/mmunro3318/3d-render-pipeline/tree/main/.claude/skills/gstack/plan-design-review
Command: npx skills add https://github.com/mmunro3318/3d-render-pipeline --skill plan-design-review-mmunro3318

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-design-review helps teams identify and fix missing or ambiguous design decisions early in the project lifecycle.

Core Features & Use Cases

  • Systematic critique of design plans to surface gaps in user flows, interactions, and accessibility.
  • Concrete, trade-off oriented recommendations that tie decisions to design principles and business goals.
  • Communication-ready artifacts for stakeholders outlining required changes and rationale.

Quick Start

Review the PLAN to surface ambiguities and capture recommended decisions for design coherence.

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 UX design plan to find missing interactions and accessibility gaps?

To review a UX design plan, you systematically critique strategy documents and briefs to surface ambiguities in user flows, interactions, and accessibility early in the project lifecycle. This process provides concrete recommendations tied to design principles for actionable next steps.

What is the best way to identify ambiguous design decisions before implementation?

The best way to identify ambiguous design decisions before implementation is through rigorous articulation of plan-level artifacts where UX implications are addressed. This approach applies trade-off oriented recommendations that align decisions with business goals to ensure design coherence.

When do I need a systematic critique of my design brief and information architecture?

You need a systematic critique of your design brief and information architecture when preparing plan-level artifacts where UX implications must be addressed before implementation. It helps teams fix missing design decisions early and generates communication-ready rationale for stakeholders.

Does design plan review work for strategy documents and early project lifecycle artifacts?

Yes, design plan review works directly on strategy documents and early project lifecycle artifacts. It rigorously evaluates these plan-level inputs to align UX planning with design principles and outputs required changes with clear rationale for stakeholders.

How do I generate communication-ready artifacts outlining required UX changes?

You generate communication-ready artifacts by reviewing the design plan to surface ambiguities and capturing recommended decisions for design coherence. This process outputs stakeholder-facing documents outlining required changes and the rationale tied to design principles.