Audit and Refactor a Design System

Use this play at the start of a new work cycle — after a retrospective, after a phase completes, or when planning what to build next. Produces a prioritized task list for the next iteration. **Step 1 — Read the living brief:** Read `LIVING_BRIEF.md` in full. Pay particular attention to: - Open questions (unresolved decisions) - Current state gaps (stubbed components, missing token categories) - The most recent retrospective entry in the decision log **Step 2 — Assess the system's current maturity:** Classify the system's current state across five dimensions: | Dimension | Not started | Partial | Complete | |---|---|---|---| | Token foundation (primitive + semantic) | | | | | Component coverage (key components implemented) | | | | | Accessibility compliance | | | | | Dark mode (if required) | | | | | Documentation (DESIGN.md current, living brief current) | | | | **Step 3 — Identify the highest-priority work:** Based on the maturity assessment and the living brief's open questions, identify the top 3–5 items for the next iteration. Prioritize using these rules: 1. **Blocking gaps** — missing foundations that block other work (no token file = can't implement components) 2. **Accessibility violations** — any blocking issues from the accessibility audit 3. **Coverage gaps** — components that are stubbed but needed for the product 4. **Open questions** — decisions that have been deferred but now have enough information to resolve 5. **Improvements** — enhancements to things that exist but aren't complete **Step 4 — Produce the iteration plan:** Output a structured plan: ``` ## Iteration goal [One sentence describing the primary outcome of this iteration] ## Tasks (prioritized) 1. [Task] — [why it's first] — [relevant play to use] 2. [Task] — [why it's here] — [relevant play to use] ... ## Open questions to resolve this iteration - [Question] — [approach to resolving it] ## Success criteria [How you will know this iteration is complete] ``` **Step 5 — Update the living brief:** Append to the decision log: ``` [2026-05-13] — Iteration planned — [iteration goal in one sentence] ```