spawn-next-session

Generate the next AutoPilot kickoff package from the latest HANDOFF.md.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Kohlex/autopilot-plugin --skill spawn-next-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spawn-next-session
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/spawn-next-session
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill spawn-next-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads the just-merged HANDOFF doc after /ship lands the current work, and automatically generates a complete kickoff package for the next AutoPilot session, reducing manual coordination and delays.

Core Features & Use Cases

  • Read the latest HANDOFF.md to extract product, feature, mission state, and the next-version number.
  • Generate three artifacts (HANDOFF-V<N+1>.md, KICKOFF-PROMPT-V<N+1>.md, SPAWN-INSTRUCTIONS.md) into .planning/<product>/kickoff-packages/V<N+1>-kickoff and prepare them for review.
  • Create a follow-up git branch, commit the new files, push to origin, and open an auto-mergeable PR; support standalone invocation as well.
  • Use cases include handoff between sessions, prep for the next kickoff, and automated session spawning via Claude Code.

Quick Start

Run /spawn-next-session to seed the next kickoff package based on the latest HANDOFF.

Frequently Asked Questions about spawn-next-session

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

FAQPage Schema
How do I automate kickoff package generation for my next development session?

Automate kickoff package generation by running /spawn-next-session to read the latest HANDOFF.md and automatically produce HANDOFF-V<N+1>.md, KICKOFF-PROMPT-V<N+1>.md, and SPAWN-INSTRUCTIONS.md in the correct kickoff directory.

How does session handoff work when transitioning between automated development cycles?

Session handoff works by reading the just-merged HANDOFF doc after a ship lands, extracting product and mission state, then generating the complete next-version kickoff package and opening an auto-mergeable PR on a follow-up branch.

Can I use git-worktree and PR-automation to prepare kickoff packages without manual coordination?

Yes, you can use git-worktree and PR-automation to prepare kickoff packages; the process creates a follow-up branch, commits the generated files, pushes to origin, and opens an auto-mergeable PR without manual coordination.

What is the best way to version and store AutoPilot kickoff artifacts across multiple product lines?

The best way to version kickoff artifacts is placing them in .planning/<product>/kickoff-packages/V<N+1>-kickoff directories, applying consistent naming conventions and incremental version rules across all AutoPilot product lines.

Do I need a merged HANDOFF.md file before running the next session kickoff automation?

Yes, you need a merged HANDOFF.md file before running the automation because the Skill reads the latest HANDOFF to extract the current product, feature, mission state, and next-version number required to generate the kickoff package.

What happens if the kickoff package generation fails during the automated session spawning process?

If kickoff package generation fails during automated session spawning, the Skill handles the failure cases without blocking the main workflow, allowing your current operations to continue while resolving the kickoff preparation issue separately.