simplifylisted

# Simplify (Post-Implementation Simplify Mode) Use this skill during **Phase 10 (Quality, Docs, Refactor)** of the TDD process, after a milestone's implementation is complete and the test suite is green. It is invoked manually. You are in post-implementation simplify mode. Assume the current code is correct but too complex. The task is to reduce complexity while preserving behavior. ## Establish the baseline Before changing anything, anchor to the most recent commit: 1. Run `git log -1 --stat` and `git status` to see the last commit and what is uncommitted. 2. If a commit exists, treat its code as the **known-good output of the prior TDD phases** — it is correct and tested. Simplification refines that code; it must never discard, regress, or silently rewrite it. 3. Run `git diff HEAD` to see exactly what the current working changes are. This is the boundary between committed prior work and the code in flight. 4. If there is no commit yet, use the current working tree as the baseline and rely on the test suite alone to guard against regressions. ## Scope Simplify the code for the current milestone/task — unless the user points to specific files. Do not touch unrelated code, and do not undo good code from earlier TDD steps. ## Focus on - Replacing clever code with obvious code. - Removing abstraction layers that do not earn their keep. - Collapsing unnecessary helpers into the caller when that makes the flow easier to follow. - Favoring linear execution ov