agentic-docs-github-migrationlisted

# Agentic Documentation and GitHub Migration Migrate one established solo-maintained repository from scattered planning and documentation into verified documentation authorities plus GitHub Issues/PRs/milestones. This is a finite-use workflow. A repository is migrated once; afterwards it is governed by the ordinary phase and review skills. That shape is why the skill is explicitly invoked rather than implicitly triggered — there is no such thing as routine migration work, so an implicit trigger could only ever be a false positive. Worked examples and provenance: `examples.md`. ## Activation guard Require one of the two exact modes: ```text $agentic-docs-github-migration profile $agentic-docs-github-migration execute /absolute/path/project-profile.yaml ``` If the request is not explicit or the target is a new project, stop this workflow. Route new-project setup to `agentic-project-bootstrap`. ### Solo-maintainer constraint Operate only on a solo-maintained repository. If the repository has multiple active maintainers, team-owned protections, or organizational compliance requirements, report that this workflow does not cover that case and do not extrapolate. The constraint exists because every checkpoint in this skill assumes a single ratifying human; with several maintainers, "the human approved the profile" stops being a well-defined claim. This constraint is expressed in two places that must change together: the prose above, and the `project.maintainer_model` check