handoff

Evaluate phase gates and validate inv_context.json for CAPPY handoffs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/theLightArchitect/cappy-toolkit --skill handoff-thelightarchitect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/theLightArchitect/cappy-toolkit/tree/main/skills/handoff
Command: npx skills add https://github.com/theLightArchitect/cappy-toolkit --skill handoff-thelightarchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates inter-phase handoffs for CAPPY by evaluating phase gates, controlling the investigation loop after Phase 4, and ensuring HITL checkpoints are prepared and audited.

Core Features & Use Cases

  • Gate evaluation and loop control: decides whether to continue the investigation, converge on a result, or escalate.
  • Context extraction and health checks: reads phase results and validates inv_context.json to maintain a consistent state.
  • HITL checkpoint preparation: formats the review summary and artifact data for Main Claude to present to Kevin.

Quick Start

Instruct CAPPY to perform the phase handoff after receiving Phase 4 results to prepare the next-phase readiness checkpoint.

Frequently Asked Questions about handoff

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

FAQPage Schema
What is human-in-the-loop checkpoint preparation in workflow orchestration?

Human-in-the-loop (HITL) checkpoint preparation formats phase review summaries and artifact data for human evaluation. It reads phase results, validates context health, and enforces safety checks before presenting the checkpoint to the reviewer.

How do I validate context health before a phase transition?

Validate context health by reading phase results and checking the inv_context.json file. The system evaluates this data to maintain a consistent state and ensures all safety checks pass before allowing the workflow to proceed to the next phase.

How do I orchestrate phase transitions and control the investigation loop?

Orchestrate phase transitions by evaluating phase gates after receiving results, such as after Phase 4. The system controls the investigation loop by deciding whether to continue investigating, converge on a result, or escalate based on validated context.

Does phase handoff require specific dependencies or components?

Phase handoff does not require external dependencies or components. It operates as a standalone workflow orchestration step that reads existing phase results and validates the inv_context.json file to manage internal state and audit trails.

When should I trigger a workflow handoff for human review?

Trigger a workflow handoff for human review when a phase reaches a gate, such as after Phase 4 results. This initiates the preparation of a HITL summary, allowing the reviewer to assess the audit trail and determine the next action.