What problem does it solve? Before writing UI code, developers need to decide which files a change touches, which existing patterns to follow, and which tests will break. Doing this ad hoc produces inconsistent plans and missed test impact. This Skill turns a UI task description into a concrete, reviewable implementation plan. ## Core Features & Use Cases - Context-Aware Planning: Loads a prior task-analysis artifact, repo learnings, and resolved decision memos so the plan reflects settled decisions instead of re-deriving them. - Test Impact Analysis: Runs an affected-test finder and delegates test-file reading to a sub-agent, summarizing which unit and E2E tests break and what new coverage is needed. - Plan Publication: Writes the plan to a timestamped markdown file, persists the planned file list for downstream scope checks, and renders an HTML plan artifact from a fixed template. - Use Case: Before implementing a new dashboard widget, run the planner to get the exact files to create and modify, the design-system pattern to follow, the tests that will break, and a list of open questions to resolve before coding starts. ## Quick Start Ask the assistant to plan a UI feature before implementing it, for example: plan this feature — add a filter bar to the deck list view.
