handover

Generate ApexYard handover assessments with harnessability scoring across five dimensions.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill handover-me2resh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/handover
Command: npx skills add https://github.com/me2resh/apexyard --skill handover-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

Frequently Asked Questions about handover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I onboard an external repository into SDLC governance?

Repository onboarding evaluates type safety, module boundaries, framework opinionation, test coverage signal, and lint baseline. These five dimensions determine whether blocking enforcement or advisory-only mode should run during governance adoption.

How do I generate a handover assessment for an inherited codebase?

Generating a handover assessment requires inspecting the inherited codebase via cloning or local path ingestion. The process deterministically outputs a handover-assessment.md file and optional topology architecture stubs to guide adoption planning.

Does repository onboarding support CI enablement and topology scaffolding?

Yes, repository onboarding supports CI enablement by synthesizing CI templates from detected stack evidence. It applies harness-template bundles to seed handbooks, AgDR drafts, and topology architecture stubs where applicable.

What is the best way to assess codebase harnessability before applying governance workflows?

Assessing codebase harnessability involves scoring type safety, module boundaries, framework opinionation, test coverage, and lint baseline. This evaluation recommends whether ApexYard roles and workflows should apply blocking enforcement or switch to advisory-only.

How does repository inspection work when cloning is not available for onboarding?

When cloning is not available, repository inspection falls back to LSP-aware deep-dive analysis. This method enables MCP reindex to extract the tech surface area needed to produce the handover assessment.