kestrel-mcp-handoff

Snapshot git state, active RFC, and baseline health into HANDOFF.md for agent handoffs.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Srain021/KesTREL --skill kestrel-mcp-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kestrel-mcp-handoff
Source: https://github.com/Srain021/KesTREL/tree/main/.cursor/skills-cursor/kestrel-mcp/handoff
Command: npx skills add https://github.com/Srain021/KesTREL --skill kestrel-mcp-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables agent-to-agent or session-to-session continuity by snapshotting the current development session state and using HANDOFF.md for resume.

Core Features & Use Cases

  • Snapshot the current git state, active RFC, and baseline health into HANDOFF.md to enable seamless handoffs.
  • Resume from HANDOFF.md by validating state and restoring the next steps.
  • Centralize context and next steps for the incoming agent to pick up where the previous left off.

Quick Start

Trigger a handoff to snapshot the current session state for later resume.

Frequently Asked Questions about kestrel-mcp-handoff

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

FAQPage Schema
How do I create a session handoff snapshot for an RFC-driven git workflow?

To create a session handoff snapshot, trigger the skill to capture your current git state, active RFC, and baseline health into a HANDOFF.md file for resume. This enforces a repeatable process with restore instructions for the incoming agent.

What is a development session handoff and when do I need one?

A development session handoff is a snapshot of your current git state, active RFC, and baseline health saved to HANDOFF.md. You need it when transferring context between agents or sessions to ensure continuity and prevent losing progress.

How do I resume an agent session from HANDOFF.md?

To resume an agent session from HANDOFF.md, the skill validates the snapshot state and restores the next steps. This ensures the incoming agent picks up exactly where the previous one left off.

Can I use this handoff snapshot for non-RFC development workflows?

The handoff snapshot applies primarily to RFC-driven workflows, capturing git state, active RFC, and baseline health. While it enforces a repeatable restore process, its context structure is optimized for RFC-based development.

Does the session handoff capture git state and baseline health automatically?

Yes, the session handoff captures your current git state, active RFC, and baseline health into HANDOFF.md. This snapshot enforces a repeatable process with restore instructions and next steps for continuity.