autopilot-loop

Coordinates multi-session loops across waves with validation and escalation handling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate the autonomous multi-session loop that coordinates /ship, spawn-next-session, and claude-initiated sessions, ensuring seamless progression across waves without manual intervention.

Core Features & Use Cases

  • Coordinates session transitions and verifies the next session boots cleanly.
  • Enforces doctrinal STOP conditions, surfaces human decisions via HUMAN-DECISION.md, and logs decisions for next-wave planning.
  • Spawns the kickoff package for the next session and keeps the loop running through subsequent waves.

Quick Start

Start the autopilot loop to coordinate the next inter-session transitions for the current product.

Frequently Asked Questions about autopilot-loop

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

FAQPage Schema
How do I orchestrate an autonomous build-loop across multiple development sessions?

An autonomous multi-session loop manages session workflows by coordinating /ship, spawn-next-session, and Claude-initiated sessions. It enforces doctrinal STOP conditions and surfaces human decisions via HUMAN-DECISION.md to ensure safe progression across waves.

How do I handle escalation and enforce STOP conditions during autonomous session workflows?

Autonomous session workflows enforce doctrinal STOP conditions by halting the loop during failures or completion requirements. The orchestrator surfaces necessary human decisions via HUMAN-DECISION.md and logs them for next-wave planning before safely exiting.

What is the best way to spawn the next session continuously across wave-based development?

Spawning the next session continuously requires generating a kickoff package for the subsequent session. The orchestration loop verifies the new session boots cleanly and keeps the build process running through subsequent development waves.

Can I use autonomous session orchestration for workflows requiring continuous validation and governance?

Autonomous session orchestration applies directly to wave-based development requiring continuous validation, governance, and escalation handling. It coordinates loop steps systematically while enforcing doctrinal STOP conditions to maintain safe operational autonomy.

Why does my multi-session build loop fail to progress cleanly to the next wave?

Multi-session build loops fail to progress when doctrinal STOP conditions are triggered or unhandled human decisions block execution. The orchestrator logs these decisions in HUMAN-DECISION.md to ensure safe exit on completion or failure before spawning the next wave.