Spec to UX Tasks

Read a product spec and extract all UX work items into a structured ux-tasks.md file in the same spec folder.

Why this skill exists

Product specs describe functional requirements for engineering, but UX teams need a clear task list of what they must design, decide, or validate. This skill bridges that gap by scanning each spec section and generating prioritised UX tasks with context, acceptance criteria, and open questions.

Input

The user provides:

1. Spec source (required) — one of: a. A spec file path (e.g., docs/specs/NNN-feature-name/feature-name.md) b. A feature name (e.g., "feature X") — resolve to the spec folder using an epic-to-spec-map.yaml index (or similar convention) c. A wiki/doc URL — pull the spec via your doc-to-markdown converter

2. Meeting transcript (optional) — a meeting URL or transcript ID from your meeting tool. If provided, fetch the transcript via the relevant MCP tool and cross-reference it with the spec to capture UX points discussed in the meeting that may not yet be in the spec.