What problem does it solve? It prevents ad-hoc optimization attempts that skip baseline analysis, lack measurable goals, or ship unverified changes by enforcing a disciplined, phase-gated optimization workflow. ## Core Features & Use Cases - Phased Workflow: Ten phases from context collection and baseline analysis through goal definition, solution design, implementation, environment refresh, effect verification, and summary archiving. - Confirmation Gate: Requires presenting a diff preview and obtaining explicit user approval before any code changes are made. - Quantified Verification: Compares before/after metrics in a structured table, runs regression tests, and archives a summary document to docs/optimize/ with a conventional-commit message. - Use Case: When retrieval latency is too high, trigger the skill to record baseline P95 latency, compare candidate solutions, confirm the diff, implement parallelized retrieval, and verify the latency improvement against the baseline. ## Quick Start Start a message with "optimize:" followed by the feature you want to improve, such as "optimize: reduce the search API response time".