plan-repo-extractlisted

# Plan a repo extraction Use this skill to **extract** a cohesive component out of its repository into an **independent repository** — carefully lifting out the self-contained component while leaving the rest undisturbed. The agent's default working scope is the repo; this skill operates at the **repo boundary**: it looks inward to find cohesion, judges whether that cohesion is worth standing on its own, and — only then — plans the carve. Governing intuition: **most components should stay in-repo.** A separate repository buys independent versioning and consumption at the cost of a cut dependency, a hardened API, split history, and its own build/CI/release. The assessment must earn the split; "keep in-repo" is a common, correct verdict. **Input**: the repository component to assess for carve-out — if unnamed, discover the candidate in Phase 1; if the goal is only an internal module split, hand off to `plan-split`. **Boundary**: evaluates and plans — produces a go/no-go assessment and, for a GO, a carve-out plan; does not run git surgery, create repos, publish, or move code. ## Workflow ### Phase 0: Anchor the scope The working scope is this repository; the target is a **new, independent repository**. Confirm the candidate component (named by the user, or to be discovered in Phase 1). If the intent is only a cleaner internal module *within the same package*, this is the wrong skill — hand off to `plan-split`. ### Phase 1: Locate the cohesion Find the candidate component