--- name: repository-adoption description: Assess and adopt an existing repository into Repository Stewardship using repoctl adopt. Use when connecting an existing, non-templated repository without moving its domain content. --- # repository-adoption Thin wrapper around `repoctl adopt`. The canonical procedure is `docs/adoption-runbook.md`; this skill only collects missing decisions, calls the CLI with machine output, and explains findings. It must not duplicate the runbook logic. ## Procedure 1. Run `repoctl adopt --repo --mode assess --output json` (read-only). 2. Present the classification, detected content roots, and any `questions` that need owner confirmation. 3. Run `repoctl adopt --repo --mode plan --owner --output json` once open questions are resolved. This is still read-only and returns an `AdoptionPlan` with a `planHash`. `plan` refuses without a confirmed owner, and refuses while `assess` left an error-severity finding; an owner who accepts one lists it under `acknowledgedFindings` (with a `reason`) in the `--answers` file. 4. Show the full plan (files created, patched managed blocks, preserved paths, forbidden changes) before asking for approval. 5. Only after explicit approval, run `repoctl adopt --repo --mode apply --plan --approve `. 6. Run `repoctl adopt --repo --mode verify --output json` and report the `AdoptionReport`, including any `unresolvedFindings`. The only implemented strategy is `overlay`. Normalization recipes are specified in the runbook but not implemented, and the CLI does not offer them: do not describe `--strategy normalize` or `--recipe` as available.