autopilot

Name: autopilot
Availability: InStock
Author: KOHLEX

Detect the current autopilot phase and dispatch downstream lifecycle skills.

Updated Jun 4, 2026

Search Tags:#automation #orchestrate #autopilot #doctrine #phase-detection #workflow-dispatch #downstream-skills

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route a product through its lifecycle by detecting the current autopilot phase and dispatching the appropriate downstream skills.

Core Features & Use Cases

Phase-aware routing to downstream skills based on filesystem phase detection (bootstrap, architecture lock, and build waves).
Single-session orchestration that drives a product to its next checkpoint and stops, preventing multi-session drift.
Cross-repo, doctrine-compliant dispatch with safeguards and human-decision gates when needed.

Quick Start

Run /autopilot <product> to bootstrap Phase 0 or resume through Phase 0.5 and Phase 1, letting the wrapper dispatch to downstream skills to drive the product forward.

Frequently Asked Questions about autopilot

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

FAQPage Schema

How do I automate product lifecycle orchestration from bootstrap to handoff?▼

Single-session orchestration prevents multi-session drift by driving a product to its next checkpoint and stopping. It coordinates platform-init, architecture-design, and build phases while enforcing doctrinal constraints and recording phase state.

Can I resume a workflow from a previous phase detection state?▼

Run the command with your product name to bootstrap Phase 0 or resume through Phase 0.5 and Phase 1. The wrapper dispatches to downstream skills to drive the product forward.

Does product orchestration work across multiple repositories?▼

Human-decision gates are included when needed, ensuring controlled progression across repository boundaries during the architecture-lock and autonomous build waves.

What are the limitations of single-shot workflow execution?▼

The orchestration enforces doctrinal constraints at each gate, meaning any unresolved repository state or missing downstream skills will halt progression until resolved.

When do I need human-decision gates during autonomous build orchestration?▼

The gates trigger during phase transitions to prevent uncontrolled automated actions, ensuring that critical architecture-lock and handoff decisions receive manual review.