handoff

Validate route, provider availability, branch state, and upstream contract for handoff planning.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/LaPaGaYo/nexus --skill handoff-lapagayo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/canonical/handoff
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill handoff-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Officially governs handoffs by ensuring routes, provider lanes, and contracts line up before execution, reducing drift and failed builds.

Core Features & Use Cases

  • Validates the four critical dimensions of a handoff: route, provider availability, branch state, and upstream contract.
  • Generates governance artifacts like governed-handoff.md and status records to capture decisions and recoveries.
  • Integrates with /plan and /build workflows to enable deterministic handoffs and recoverable failures.

Quick Start

Execute a handoff after planning to lock in the route and provider lane for the next build.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I validate routing and provider availability before a build?

Pre-approve routing and provider availability by validating the four critical handoff dimensions: route, provider availability, branch state, and upstream contract before build execution to prevent drift.

What is governed handoff planning in software deployment?

Governed handoff planning is the process of validating route, provider, branch state, and upstream contracts before deployment approval. It generates governance artifacts like governed-handoff.md to capture decisions and ensure traceability.

How do I recover deployment approvals when state drifts during a build?

Recover drifted deployment approvals by generating current handoff state and recovery prompts. The system stores governance artifacts and status records to track decisions and restore deterministic handoffs.

Can I integrate handoff validation with existing plan and build workflows?

Yes, you can integrate handoff validation with /plan and /build workflows. It enables deterministic handoffs by locking in the route and provider lane for the next build and supporting recoverable failures.

Why do my builds fail due to upstream contract mismatches during deployment?

Builds fail from upstream contract mismatches when handoffs lack explicit governance. Validating the upstream contract before approval ensures all dependencies align, reducing drift and execution failures.