plan-design-review

Identify and fill missing design decisions in a PLAN before execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan gaps and missing design decisions slow down implementation. This Skill guides you to surface and add essential design choices before coding, ensuring a coherent, testable plan.

Core Features & Use Cases

  • Identify gaps in UX, information architecture, governance, and design-system decisions within a PLAN.
  • Propose concrete design decisions and rationale, then append them to the PLAN for alignment with stakeholders.
  • Validate completeness by cross-checking requirements, constraints, and success metrics across domains.

Quick Start

Review the PLAN and add the missing design decisions to the plan before implementation.

Frequently Asked Questions about plan-design-review

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

FAQPage Schema
How do I identify missing design decisions in a UX plan before implementation?

To identify missing design decisions in a UX plan, cross-check requirements, constraints, and success metrics across UX, information architecture, governance, and design-system domains to surface gaps and document suggested resolutions with rationale.

What is a design plan review and when do I need it?

A design plan review is a pre-build critique that surfaces and fills missing design choices to ensure a coherent, testable plan. You need it when plan gaps and missing UX or governance decisions risk slowing down your implementation phase.

How do I ensure stakeholder alignment on design-system decisions before coding?

Ensure stakeholder alignment on design-system decisions by proposing concrete choices with traceable rationale and appending them directly to the plan, validating completeness across all project domains before execution begins.

Can I use a plan review to mitigate risk across information architecture and governance domains?

Yes, you can use a plan review to mitigate risk by validating completeness and filling gaps across information architecture and governance domains, ensuring all design decisions are documented with concrete next steps before build.

What is the best way to document design decisions and rationale for a project plan?

The best way to document design decisions and rationale is to append concrete choices with traceable justifications directly to the plan, augmenting it with suggested resolutions for identified gaps across all relevant design domains.

Why does missing information architecture in a plan slow down implementation?

Missing information architecture in a plan slows down implementation because incomplete design choices create ambiguity, preventing coherent execution and requiring disruptive, ad-hoc design decisions during the build phase.