/vt-c-pd-analyze-changes

Analyze impact of new information on design workflow state

Plugin: core-standards
Usage: /vt-c-pd-analyze-changes [--item FILE]

---

/vt-c-pd-analyze-changes

Analyze pending inbox items and determine their impact on design artifacts.

Usage

/vt-c-pd-analyze-changes                  # Analyze all pending items
/vt-c-pd-analyze-changes --item FILE      # Analyze specific item

Prerequisites

Run /vt-c-pd-inbox-scan first to detect new items.

What It Does

1. Loads pending items from .design-state.yaml
2. Reads and analyzes each item's content
3. Determines severity (critical, major, minor)
4. Identifies affected areas (PRD, prototype, specs)
5. Applies impact matrix to recommend return phase
6. Generates aggregated impact report with options

Impact Assessment

Artifact	Impact Levels
PRD	HIGH (scope change), MEDIUM (feature detail), LOW (minor clarification)
Prototype	HIGH (major UI rework), MEDIUM (component changes), LOW (styling)
specs	HIGH (new features), MEDIUM (acceptance criteria), LOW (technical notes)

Severity Classification

• CRITICAL: Blocks release, safety/compliance, fundamental flaw
• MAJOR: Significant usability problem, missing feature, scope change
• MINOR: Polish item, minor confusion, nice-to-have

Output

Produces an impact report with: - Item-by-item analysis - Aggregated impact assessment - Recommended routing options - Trade-offs for each option

Next Step

After analysis, run /vt-c-pd-route-decision to execute the routing.

Part of Iterative Design Loop

New Input → /vt-c-pd-inbox-scan → [/vt-c-pd-analyze-changes] → /vt-c-pd-route-decision
                                     ▲
                                YOU ARE HERE

Routes To

pd-analyze-changes skill