print-launch-block

Generate a copy-paste spawn block for AutoPilot/Kohlex session kickoffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ad-hoc spawn instructions by emitting a single, copy-paste block that standardizes how operators start the next AutoPilot/Kohlex session, ensuring consistency across handoff and ad-hoc uses.

Core Features & Use Cases

  • Deterministic, copy-paste spawn block for next-session setup
  • Cross-scenario compatibility with /handoff-next, /ship Step 14, and ad-hoc invocations
  • Self-check and substitution validation to prevent missing placeholders

Quick Start

Invoke /print-launch-block to emit the standardized spawn recipe for the next session.

Frequently Asked Questions about print-launch-block

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

FAQPage Schema
How do I standardize session kickoff instructions for automation handoff?

Standardize session kickoff instructions by emitting a deterministic, copy-paste spawn block that validates substitutions and checks for required artifacts before presenting the recipe to operators.

What is a spawn block in automated session handoff workflows?

A spawn block in automated session handoff workflows is a standardized, copy-paste instruction set that ensures operators start the next AutoPilot or Kohlex session with consistent configurations and validated substitutions.

How do I generate a copy-paste spawn block for my next automation session?

Generate a copy-paste spawn block by invoking the print-launch-block command, which self-verifies the emitted text and validates all placeholder substitutions to prevent missing kickoff artifacts.

Can I use the launch block generator for ad-hoc session invocations outside of /handoff-next?

Yes, the launch block generator supports ad-hoc session invocations alongside /handoff-next and /ship Step 14, applying consistent kickoff formats across all scenarios without requiring specific dependencies.

Why does my session spawn block fail validation during handoff?

Session spawn block validation fails during handoff when required kickoff artifacts are missing or placeholder substitutions remain unchecked, which the self-verification process detects before emitting the block.

Do I need VS Code worktree setup to generate a session launch block?

No external worktree setup is required to generate a session launch block, as the skill operates without dependencies and self-verifies the emitted output internally before presenting it.