What problem does it solve? Large Android migrations (Views to Compose, Dagger to Hilt, RxJava to Coroutines) fail when attempted as one giant PR, when they freeze the codebase, or when there is no rollback path. This Skill produces a phased migration plan that lets the team keep shipping while the migration runs in parallel. ## Core Features & Use Cases - Phased planning: Generates a 3-5 phase plan (Foundation, Bridge, Scale out, Remove bridge, Cleanup) where each phase is mergeable, reversible, and independently assignable. - Coexistence strategies: Provides concrete interop mechanisms per migration type, such as ComposeView inside XML, Flow.asLiveData() bridging, and Hilt running alongside Dagger. - Safety nets and communication: Defines feature flags, telemetry tagging, baseline tests, rollback per phase, and team rules that stop new code from using the old pattern. - Use Case: When a developer says "we need to kill RxJava" or "migrate to Compose", the Skill outputs a migration document with a definition of done, phase breakdown, risk assessment, and team rules. ## Quick Start Ask the assistant to plan a phased migration from Dagger to Hilt for this Android project without freezing ongoing feature work.
