ux-plan-tasks
UX Plan Tasks
This skill exists to stop: implementation plans that omit meaningful UX evidence or add ceremonial checks to every component.
🤖 0. HOW TO USE
Only ARCHITECT needs dedicated UX planning tasks. BUILD keeps relevant UX acceptance and verification in existing tasks, without invoking the full task sequence below. Input is the current plan plus supplied requirements, user context, and prior findings; named artifact files are optional. Output a scoped task patch, with evidence and dependencies, in the existing plan or .jimmy/work/<feature>/ux-tasks.md.
Reuse completed research and accepted scope. Select tasks by unresolved risk in the affected user flow; a phase already supported by adequate evidence needs no duplicate test. Each chosen task names the journey/states, method, completion evidence, and any blocking dependency. A walkthrough is expert evidence, never a claim of actual user research.
Adds UX-specific tasks to an existing development plan. Only activates in ARCHITECT mode — BUILD mode plans are lightweight and don't need separate UX tasks.
Mode: ARCHITECT (full)
Review the plan and select relevant UX tasks at appropriate points. The sequence below is a menu; add all phases only when each resolves an actual uncertainty.