handoff-next

Name: handoff-next
Availability: InStock
Author: KOHLEX

Generate handoff and kickoff prompt files for the next AutoPilot session.

Updated Jun 4, 2026

Search Tags:#automation #workflow #handoff #claude-code #pull-request #git-worktree #kickoff

Ready to run

npx skills add https://github.com/Kohlex/autopilot-plugin --skill handoff-next

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handoff-next
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/handoff-next
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill handoff-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session handoffs require multi-faceted coordination across branches, templates, and PR flows. This skill automates and standardizes that process by generating HANDOFF-V<N+1>.md, KICKOFF-PROMPT-V<N+1>.md, a spawn guide, and a ready-to-launch block that the operator can paste to start the next session.

Core Features & Use Cases

Generate HANDOFF-V<N+1>.md and KICKOFF-PROMPT-V<N+1>.md artifacts based on the current handoff.
Produce a READY-TO-LAUNCH block containing step-by-step instructions for the operator to spin up the next session.
Integrate with branch orchestration and kickoff packaging workflows to ensure consistency across sessions.

Quick Start

Run the four-step handoff sequence to prepare the next AutoPilot session launch.

Frequently Asked Questions about handoff-next

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

FAQPage Schema

How do I automate end-of-session handoffs for Claude Code workflows?▼

Automate end-of-session handoffs by generating standardized HANDOFF-V<N+1>.md and KICKOFF-PROMPT-V<N+1>.md artifacts. This process creates a ready-to-paste block containing spawn instructions to seamlessly launch the next AutoPilot session.

What is the best way to prepare a kickoff prompt for a new git worktree session?▼

Prepare a kickoff prompt by running a multi-step workflow that produces a KICKOFF-PROMPT-V<N+1>.md file. This template-driven artifact ensures consistency and integrates directly with git worktree and pull-request orchestration.

Does this handoff automation work with existing pull-request and branch orchestration?▼

Yes, the handoff automation integrates with branch orchestration and pull-request workflows. It coordinates across branches and PR flows to ensure the generated handoff package aligns with your existing git worktree setup.

How do I generate a ready-to-launch block for an operator to start the next session?▼

Generate a ready-to-launch block by executing the four-step handoff sequence. The workflow outputs a print-ready block with step-by-step operator instructions for spinning up the next AutoPilot session.

Can I standardize handoff templates across multiple development sessions?▼

Yes, you can standardize handoff templates across sessions using template-driven artifacts. The enforced multi-step workflow, from Step 0 to Step 7, guarantees consistency in session transfers and kickoff packaging.