What problem does it solve? Moving reusable code out of an app into its own published Kotlin Multiplatform library involves repo scaffolding, package renames, Maven Central publishing setup, consumer migration, and a workable dev loop — each with non-obvious gotchas that cost hours when discovered the hard way. ## Core Features & Use Cases - End-to-end extraction workflow: Four phases covering seam scoping, standalone repo scaffolding, Maven Central publishing (releases and snapshots), and consumer app migration. - Publishing pipeline setup: vanniktech maven-publish configuration, GitHub Actions release and snapshot workflows, signing key handling, and Central Portal account guidance. - Composite-build dev flow: Gated includeBuild with explicit dependency substitution so the app can develop against a local library checkout, plus Renovate-driven version bumps. - Use Case: You vendored a pager/gesture module inside your production KMP app and want to open-source it as io.github.you:my-lib on Maven Central while keeping a fast inner dev loop against your app. ## Quick Start Ask the assistant to extract the vendored module from my app into a standalone KMP library published to Maven Central and swap the app to consume the artifact.