handover

Generate a handover assessment and harnessability score for external repositories.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill handover-aabdulghany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/handover
Command: npx skills add https://github.com/AAbdulghany/fms --skill handover-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboard an external repo into ApexYard management by producing a structured handover assessment and harnessability scoring across 5 codebase dimensions.

Core Features & Use Cases

  • Generates a comprehensive handover assessment document
  • Computes a harnessability score and matches governance with SDLC workflows
  • Provides topology-driven guidance for multi-repo adoption

Quick Start

Provide the project name or URL to generate a structured handover assessment and harnessability score.

Frequently Asked Questions about handover

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

FAQPage Schema
How do I onboard an inherited codebase with a structured handover assessment?

A handover assessment analyzes an external repository's tech surface and topography to produce a structured onboarding document. It evaluates codebase adoption readiness by computing a harnessability score across 5 dimensions, helping teams understand inherited code before applying SDLC governance.

How do I generate a harnessability score for an external repository?

To generate a harnessability score, provide the project name or git URL. The system reads the target repository, analyzes its tech surface and topography, and computes the score across 5 codebase dimensions, writing the results to projects/<name>/handover-assessment.md and related output artifacts.

Can I assess a local repository path or do I need a git URL for codebase onboarding?

You can assess codebase onboarding using either a local repository path or a git URL. The system reads the target repository from either source, analyzes the technical topology, and generates the handover assessment document and harnessability scoring.

What is the best way to evaluate an external codebase for SDLC governance adoption?

The best way to evaluate an external codebase for SDLC governance is to generate a topology-driven handover assessment. This approach matches the codebase's technical surface with recommended SDLC workflows and provides a harnessability score to determine multi-repo adoption readiness.

What outputs do I get when onboarding a new repository into management?

When onboarding a repository, you receive a handover assessment document, a harnessability score, and recommended workflows. These artifacts are written to projects/<name>/handover-assessment.md and related output files for governance tracking.