What problem does it solve?
The handover skill converts an inherited or external codebase into governed ApexYard projects by assessing harnessability, identifying the tech surface area, and producing the documents and scaffolding checklist needed to run the normal SDLC.
Core Features & Use Cases
- External repo onboarding: Reads a target repository (from a local path or by cloning a provided Git URL) and produces a structured handover assessment for adoption planning.
- Harnessability scoring across 5 dimensions: Evaluates type safety, module boundaries, framework opinionation, test coverage signal, and lint baseline to determine whether Rex’s blocking enforcement should run or switch to advisory-only.
- Role/workflow/hook recommendations: Synthesizes which ApexYard roles, workflows, hooks, and CI templates should kick in based on detected stack and repo evidence.
- Optional topology instantiation: Applies a selected harness-template bundle (e.g., typescript-nextjs) to seed handbooks, AgDR drafts, and CI where applicable.
Quick Start
Request a handover assessment for a GitHub repo by running: /handover legacy-billing-api https://github.com/some-org/legacy-billing-api