autopilot

Decomposes vague instructions into phased plans and executes them autonomously with subagents.

197|85|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/yan-labs/yan-skills --skill autopilot-yan-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autopilot
Source: https://github.com/yan-labs/yan-skills/tree/main/autopilot
Command: npx skills add https://github.com/yan-labs/yan-skills --skill autopilot-yan-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Broad, unstructured requests like "fix the bug" or "ship this feature" force an AI agent to improvise, skip verification, and declare half-done work complete. This Skill turns a single vague instruction into a structured XML phase plan with objective pass/fail gates, then drives unattended execution through investigation, implementation, deployment, E2E testing, and independent code review. ## Core Features & Use Cases - Automatic task classification and planning: Classifies input into bug-fix, feature, refactor, test, research, deploy, or quality types, then assembles a phase plan from templates with mandatory verification stages. - Maker-checker subagent orchestration: Dispatches implementation and verification to separate subagents with conflict-scope isolation, model routing, and concurrency limits so no agent grades its own work. - State-file recovery and failure handling: Tracks progress in progress.md with failure classification, adaptive retry rules, and hard-stop conditions so loops resume across iterations instead of spinning. - Use Case: Tell the agent "fix the login bug and deploy it" — autopilot claims the issue, investigates the root cause, implements the fix, deploys to test, runs E2E verification with an independent checker, reviews the code, redeploys, and closes the issue with evidence. ## Quick Start Tell the agent to take this task and run it end to end on autopilot without asking for confirmation.

Frequently Asked Questions about autopilot

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

FAQPage Schema
How do I run a coding task fully autonomously with an AI agent?

Invoke autopilot with a broad instruction like "fix this bug and deploy". It classifies the task, builds an XML phase plan with objective gates, then dispatches subagents through investigation, implementation, deployment, E2E testing, and review without asking for confirmation.

How does autopilot prevent an agent from claiming incomplete work is done?

Every phase requires an objective pass/fail signal such as a zero exit code, green CI run, or browser-verified behavior. The loop cannot exit until all mandatory phases show completion markers with evidence in the progress.md state file.

Does autopilot work with both Claude Code and Codex?

Yes. It detects the host platform and adapts: Claude Code uses /loop for iteration, while Codex uses state-only execution with scheduled recovery and /goal only when a persistent goal is explicitly requested.

What happens when a phase fails during autonomous execution?

Failures are classified into types like missing-context, wrong-approach, or environment-issue before any retry. Retries must change strategy; three repeats of the same failure signature stop blind retrying and trigger re-investigation.

Why does autopilot use separate subagents for implementation and review?

The maker-checker split prevents an agent from grading its own work. Verification subagents receive only the diff, deployment URL, and acceptance criteria, never the implementer's reasoning, so their judgment stays independent.

When should I not use autopilot for a task?

Avoid it for tasks lacking any verifiable completion signal or blocked solely by inaccessible external systems. It also requires a safe bounded next action; if investigation proves none exists, it stops and reports rather than spinning.