/vt-c-pd-inbox-scan¶
Scan project inbox for new items requiring design workflow attention
Plugin: core-standards
Usage: /vt-c-pd-inbox-scan [--project PATH]
/vt-c-pd-inbox-scan¶
Scan the project inbox for new information that may trigger design iteration.
Usage¶
/vt-c-pd-inbox-scan # Scan current project inbox
/vt-c-pd-inbox-scan --project PATH # Scan specific project path
What It Does¶
- Loads current design state from
.design-state.yaml - Scans the 00-Inbox/ folder for files newer than last scan
- Classifies new items by type (usability test, stakeholder feedback, etc.)
- Updates the design state file with pending items
- Reports findings and recommends next action
Item Classification¶
| Type | Urgency | Typical Pattern |
|---|---|---|
| usability_test | HIGH | *usability*, *test-result* |
| stakeholder_feedback | MEDIUM | *stakeholder*, *feedback* |
| tech_constraint | HIGH | *technical*, *feasibility* |
| user_research | MEDIUM | *interview*, *transcript* |
| scope_change | HIGH | *requirement*, *change-request* |
| market_intel | LOW | *competitor*, *market* |
Next Steps¶
After scanning:
- HIGH urgency items: Run /vt-c-pd-analyze-changes immediately
- MEDIUM urgency items: Process before next phase transition
- LOW urgency items: Batch for next iteration
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-inbox-scan skill