What problem does it solve? After running a design-polish, design-review, or design-audit pass, teams often end up with a long list of findings spanning different effort levels and execution paths. This Skill converts those findings into a structured, prioritized plan so fixes can be executed in the right order without conflicts or duplicated work. ## Core Features & Use Cases - Finding Classification: Parses findings from design-polish, design-review, or design-audit artifacts and classifies each by effort, type, and execution path (direct fix, design-fix, feature work, or design system gap). - Sequenced Tracker Generation: Groups items by file and component, orders them by dependency and impact, and writes a tracker file at docs/tmp/design-fixes-{target}.md. - Idempotent Replanning: Rerunning with the same artifact skips duplicates and preserves existing item statuses using stable content-derived item IDs. - Use Case: After a design audit of a dashboard page produces 15 findings, use this Skill to generate a tracker that batches mechanical spacing fixes first and schedules the page restructure last. ## Quick Start Plan the design fixes from the most recent design-review artifact in docs/tmp and create a tracker file. Note: this Skill is deprecated for new work; prefer ui-expert, design-expert, and focused ui-/design- skills unless planning from legacy design artifacts.
