spawn-session

Parse kickoff instructions and launch Claude Code sessions with derived flags.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the launch of Claude Code sessions by reading kickoff package instructions and deriving the required flags (worktree path, branch, session name, and prompt file).

Core Features & Use Cases

  • Wraps the underlying spawn-claude-session launcher to auto-derive flags from SPAWN-INSTRUCTIONS.md.
  • Supports multiple invocation forms and enforces a safety confirmation before spawning.
  • Use Case: Kick off a new Claude session for a given kickoff package without memorizing complex parameters.

Quick Start

Run /spawn-session to locate the latest kickoff package and initiate a Claude Code session with automatic flag derivation.

Frequently Asked Questions about spawn-session

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

FAQPage Schema
How do I automate Claude Code session kickoff without memorizing CLI parameters?

To automate Claude Code session kickoff, this Skill reads SPAWN-INSTRUCTIONS.md files to auto-derive required flags like worktree paths, branch names, and prompt files. It wraps the underlying launcher to initiate sessions with a single command.

What is the best way to launch multiple Claude sessions across different packages?

The best way to launch multiple Claude sessions across packages is using an automated kickoff workflow. This Skill parses kickoff instructions for each package and enforces a user-confirmation step before spawning the underlying session launcher.

How does automatic flag derivation work when spawning a new Claude Code session?

Automatic flag derivation works by parsing the SPAWN-INSTRUCTIONS.md file within your kickoff package. The Skill extracts the necessary worktree path, branch, session name, and prompt file parameters to configure the spawner automatically.

Do I need to manually confirm before every automated session spawn?

Yes, you need to manually confirm before every automated session spawn. The Skill enforces a safety confirmation step prior to invoking the spawner, ensuring you maintain oversight over automated kickoff workflows across multiple products.

Can I use spawn-session to set environment variables for the underlying launcher?

Yes, you can use spawn-session to configure the underlying launcher environment. It automatically sets the AUTOPILOT_AUTO_SPAWN variable for the launcher during the kickoff process, enabling automated session generation.

What limitations exist when auto-deriving session flags from kickoff instructions?

A limitation when auto-deriving session flags is that the Skill requires a valid SPAWN-INSTRUCTIONS.md file to locate the latest kickoff package. Without these structured instructions, it cannot derive the worktree path or prompt file parameters.