plan-design-review

Identify missing design decisions in PLAN documents before implementation.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill plan-design-review-chang-shih-yung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-design-review
Source: https://github.com/Chang-Shih-Yung/auto-learning/tree/main/.claude/skills/gstack/plan-design-review
Command: npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill plan-design-review-chang-shih-yung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews of PLANs often miss critical design decisions, leaving gaps that cause implementation drift. This Skill identifies missing decisions and adds them to the PLAN before work starts.

Core Features & Use Cases

  • Proactively identifies gaps in UI/UX decisions, information hierarchy, accessibility, and edge cases.
  • Generates concrete design decisions to embed in PLAN for designers and engineers to follow during implementation.

Quick Start

Generate missing design decisions in the PLAN and lock in intent before development.

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 development?

To identify missing design decisions in a UX plan, review the document for gaps in UI/UX choices, information hierarchy, accessibility, and edge-case coverage. This process surfaces actionable gaps to enforce design-to-implementation alignment and prevent drift.

What is design-to-implementation alignment and how does it prevent drift?

Design-to-implementation alignment is the process of enforcing explicit ownership, acceptance criteria, and traceable decisions within a plan. It prevents implementation drift by locking in concrete design decisions for engineers before development starts.

How do I add concrete design decisions to a plan for engineers?

You add concrete design decisions to a plan by analyzing UI/UX requirements and edge cases, then generating actionable design rules. These decisions are embedded directly into the PLAN for designers and engineers to follow during implementation.

Does a design critique cover accessibility and edge-case coverage?

Yes, a design critique covers accessibility and edge-case coverage by proactively identifying missing UI/UX decisions across these areas. It surfaces actionable gaps within the information architecture to strengthen the plan before development.

When do I need to review a plan for missing UI/UX decisions?

You need to review a plan for missing UI/UX decisions before development starts. This early design critique identifies gaps in information hierarchy and accessibility, ensuring traceable decisions and acceptance criteria are locked to prevent implementation drift.