simplify

# Simplify — parallel review, sequential apply Spawns three focused review subagents in parallel, each returning a list of suggested edits. The main agent then applies them sequentially, resolving conflicts deterministically using the Principles below. The skill is **non-interactive**: it never stops to ask the user. When the Principles don't pick a clear winner, the finding is logged as "not applied" rather than surfaced as a question — the user reads the final report and re-engages if they want one of the rejected proposals. **Why review-then-apply and not apply-in-parallel:** if three subagents Edit the same files concurrently, they race. Late writers either fail loudly (Edit's `old_string` mismatch) or — worse — see "my change is already there" and silently skip, so most findings get dropped. Parallelizing the slow part (analysis) while serializing writes gives both speed and correctness. If `$ARGUMENTS` contains a focus hint (e.g. "memory efficiency"), pass it through to all three subagents so they weight that dimension. ## Principles every reviewer must follow These are cross-cutting — they apply to every finding regardless of reviewer category. The main agent passes them into each reviewer's prompt. 1. **Preserve behavior.** Any change to return values, exceptions, edge-case handling, or observable side effects is a *behavior change*, not a simplification. If a refactor alters output for any input — even malformed or "invalid" input the original happened to accep...