/vt-c-pd-route-decision¶
Execute design iteration routing decision based on impact analysis
Plugin: core-standards
Usage: /vt-c-pd-route-decision [--option N | --continue]
/vt-c-pd-route-decision¶
Execute the routing decision and transition to the appropriate design phase.
Usage¶
/vt-c-pd-route-decision # Interactive decision prompt
/vt-c-pd-route-decision --option 1 # Execute specific option from analysis
/vt-c-pd-route-decision --continue # Continue current phase, defer items
Prerequisites¶
Run /vt-c-pd-analyze-changes first to generate impact analysis and options.
What It Does¶
- Presents decision options based on impact analysis
- Captures user's selection
- Updates
.design-state.yamlwith new state - Increments iteration counter
- Logs decision in iteration history
- Resets quality gates for affected phases
- Launches the target phase skill
Decision Options (Typical)¶
- Return to earlier phase (recommended based on analysis)
- Updates state to target phase
- Marks artifacts for revision
-
Cascades through subsequent phases
-
Alternative phase (partial fix)
- Address subset of issues
-
Defers remaining items
-
Split into parallel tracks
- Quick fixes in one track
-
Larger changes in separate iteration
-
Continue current phase
- Defer all items to backlog
- Document as known limitations
-
Proceed to next phase
-
Manual override
- Specify custom routing
State Updates¶
- Increments iteration counter
- Resets quality gates for target phase and beyond
- Version bumps affected artifacts
- Clears processed inbox items
- Logs decision in history
After Routing¶
Automatically launches the target phase:
- /vt-c-pd-1-research - If user research invalidated
- /vt-c-pd-2-prd - If scope/requirements changed
- /vt-c-pd-3-prototype - If UI/UX issues found
- Continue current phase if deferring
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
│
┌─────────────────┘
▼
Target Phase (pd-1, pd-2, pd-3, etc.)
Routes To¶
pd-route-decision skill