Featured play

Audit and Refactor a Design System

4/5

design-system-retrospective

Step 4 · Run a Design System Retrospective

Run a Design System Retrospective

play · design-system-retrospective
Use this play at regular intervals (end of a sprint, end of a phase, before a major release) to identify drift, undocumented decisions, and decisions that need revisiting. Updates the living brief. **Step 1 — Read the living brief:** Read `LIVING_BRIEF.md` in full. Note any open questions that have been de facto resolved by implementation but not recorded. **Step 2 — Read the current system state:** Read the token files and component files identified in the living brief's Current State section. You are looking for: - Values or patterns that exist in code but are not reflected in the living brief's Key Decisions - Components that have been added or changed without updating the Current State list - Decisions that were made with `[to be determined]` markers but have since been implemented **Step 3 — Evaluate alignment:** Answer these questions: 1. What has drifted from the recorded decisions? (Code says one thing; brief says another) 2. What has been added without documentation? (New components, new tokens, new patterns) 3. What decisions made early should be revisited? (Early constraints that no longer apply, or that have proven wrong in practice) 4. Does DESIGN.md need to be updated? (If any token values, component patterns, or Do's and Don'ts have changed) **Step 4 — Produce the retrospective report:** Output a structured report: ``` ## Drift found [List each discrepancy: what the brief says vs. what the code does] ## Undocumented additions [Components, tokens, or patterns that exist but aren't in the brief] ## Decisions to revisit [Early decisions that may need to change, with rationale] ## DESIGN.md update needed? [Yes / No — and if yes, what specifically needs to change] ``` **Step 5 — Update the living brief:** Based on the retrospective: - Update Key Decisions for any that have changed - Update Current State to reflect actual implemented state - Move any de-facto-resolved open questions to the decision log - Add a retrospective entry to the decision log: ``` [2026-05-13] — Retrospective — [one-sentence summary of most significant finding] ``` ---
Step 4 of 5 · Run a Design System Retrospective
paste intoClaude CodeCursor