# Analyze Design

> Find gaps in design docs. Use when reviewing requirements, specs, or PRDs before implementation. Identifies missing edge cases, unclear business rules, and scenarios the design should address but doesn't. Use when this capability is needed.

- Skill: `tomevault-io/analyze-design` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/analyze-design`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/analyze-design/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/analyze-design

---


# Analyze Design

Input: Design doc path
Output: Prioritized list of gaps, missing scenarios, edge cases

## Process

1. Read the design doc completely
2. Understand what system is being designed and its business context
3. Identify what's missing or unclear:
   - Edge cases not addressed
   - Error scenarios without handling
   - Business rules that are ambiguous
   - Assumptions needing validation
   - User flows with gaps

## Output Format

Group findings by priority:

### Critical (blocks user or causes data issues)

- [Gap]: [Why it matters]

### High (bad UX or business logic holes)

- [Gap]: [Why it matters]

### Medium (should address before shipping)

- [Gap]: [Why it matters]

### Low (nice to clarify)

- [Gap]: [Why it matters]

## What to Look For

**Business Logic Gaps**

- What happens when X fails?
- What if user does Y before Z?
- How does this interact with existing feature A?
- What are the boundaries/limits?

**Data & State**

- Invalid or missing input handling
- Partial failures mid-process
- State transitions that aren't covered

**User Experience**

- Confusing flows
- Confusing namings
- Edge states
- Wrong/unnecessary feature
- Good feature, wrong approach

## Not In Scope

- Implementation suggestions
- Code structure opinions
- Technical feasibility
- Rewriting the design

## Example Gap

Bad: "Missing error handling"
Good: "No defined behavior when payment succeeds but order creation fails. User could be charged without receiving order confirmation."

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/fahadmajed) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->