Implement a UX Change
Deliver a described UX change the disciplined way: capture the before state from the real markup, make the smallest coherent change at the real sites in the product's own conventions, and prove the after state with the existing behaviors still working — under an enforced independent review.
How it runs
| # | Step | Who runs it | What happens |
|---|---|---|---|
| 1 | Understand and capture the before state | Developer | Restate the change as the user experiences it, find the real surfaces, and quote the current markup and wiring. |
| 2 | Implement the smallest coherent change | Web Developer | Deliver the request at the real sites, in the product's own conventions, keeping existing behaviors wired. |
| 3 | Validate the changed flow | Developer | Walk the new experience and build a concrete before/after grounded in the real files. |
| 4 | Evaluate the deliverable | Reviewer | Independently grade the observable deliverable and route it to finish, repair, or user escalation. |
| 5 | Repair the deliverable | Web Developer | Fix only the concrete gaps from the latest independent review. |
| 6 | Finish | Developer | All deterministic and reviewer criteria passed. |
| 7 | Escalate unresolved concerns | Developer | The bounded repair loop ended without a defensible pass. |
Say something like "make this ux change" or "move the button" or "improve this flow" or "update the ui" in chat to start it.