ki-handoffs

Govern handoff doctrine for Knowledge Islands with cold agent readiness tests.

Updated May 29, 2026
One-click install
npx skills add https://github.com/knowledgeislands/ki-agentic-harness --skill ki-handoffs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ki-handoffs
Source: https://github.com/knowledgeislands/ki-agentic-harness/tree/main/skills/ki-handoffs
Command: npx skills add https://github.com/knowledgeislands/ki-agentic-harness --skill ki-handoffs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill governs the handoff doctrine for Knowledge Islands, ensuring that expensive reasoning is separated from cheap execution, allowing work planned at the top tier to be handed off to a cheaper tier or a cold agent without re-reasoning.

Core Features & Use Cases

  • Reasoning-Layer Split: Defines the separation between reasoning and execution, ensuring that expensive reasoning is done once and its output is used for execution.
  • Handoff Quality Bar: Sets the standards for handoff specifications, including decision locking, tier assignment, and readiness testing.
  • Tier Assignment: Assigns the cheapest safe tier for each unit of work based on its specification.
  • Readiness Test: Ensures that a cold agent at the assigned tier can execute the first phase from the spec alone.
  • Use Case: For a project plan, this Skill ensures that the plan is ready for handoff to a cheaper tier or a cold agent, reducing the need for re-reasoning and improving efficiency.

Quick Start

Run the 'audit' mode to check if the project plan is ready for handoff.

Frequently Asked Questions about ki-handoffs

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

FAQPage Schema
What is a reasoning-execution split in knowledge handoff?

A reasoning-execution split separates expensive reasoning from cheap execution, ensuring work planned at the top tier is handed off to a cheaper tier or a cold agent without re-reasoning.

How do I verify project plan readiness for handoff to a cold agent?

You verify project plan readiness for handoff by running the audit mode, which applies a cold agent test to ensure the assigned tier can execute the first phase from the specification alone.

How does tier assignment work for units of work in a handoff specification?

Tier assignment works by evaluating the handoff specification and assigning the cheapest safe tier for each unit of work, ensuring execution does not require re-reasoning.

What is the handoff quality bar for decision locking and tier assignment?

The handoff quality bar sets standards for handoff specifications by enforcing decision locking, validating tier assignment, and verifying readiness testing before execution.

When do I need a handoff doctrine for Knowledge Islands?

You need a handoff doctrine for Knowledge Islands when you must prevent re-reasoning across tiers, ensuring expensive planning is locked and safely executed by cheaper downstream agents.