autopilot

Orchestrates autonomous feature shipping from brainstorm through spec, plan, implementation, and PR.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/pgoell/pgoell-claude-tools --skill autopilot-pgoell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autopilot
Source: https://github.com/pgoell/pgoell-claude-tools/tree/main/plugins/deprecated/skills/autopilot
Command: npx skills add https://github.com/pgoell/pgoell-claude-tools --skill autopilot-pgoell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping a feature end-to-end requires coordinating brainstorming, spec writing, planning, TDD implementation, documentation updates, PR creation, and CI monitoring, which is tedious to orchestrate manually. This Skill automates that entire flow in autonomous mode, driven by a per-project profile at .workbench/autopilot.md. Note: this Skill is deprecated and superseded by workbench:pilot. ## Core Features & Use Cases - Ten-step autonomous workflow: bootstraps from a project profile, brainstorms with self-answered Q&A, writes spec and plan, executes via TDD and subagents, audits required skill invocations, opens a PR, and loops on CI until green. - Project profile system: reads .workbench/autopilot.md for PR behavior modes (stop_at_green, automerge, request_review), hooks, required-skill overrides, and project-specific rules, with a documented precedence chain (profile, session context, git detection, ask user). - Runtime adapters: ships reference docs mapping the workflow to both Claude Code and Codex tool names, including subagent dispatch patterns and CI polling shapes. - Use Case: Point it at a repo with a .workbench/autopilot.md profile and a feature topic; it produces a brainstorm log, committed spec and plan, TDD-implemented code in logical Conventional Commits, and an open PR with green CI. ## Quick Start Run the autopilot skill on this repository to take my feature topic from brainstorm through a green-CI pull request using the profile in .workbench/autopilot.md.

Frequently Asked Questions about autopilot

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

FAQPage Schema
How do I set up autopilot for autonomous feature shipping?

Create a `.workbench/autopilot.md` file in your repo root; even an empty file opts in, though a `## PR behavior` section with `Mode: stop_at_green` is the recommended minimum. The skill stops with an error if the profile is missing.

What PR behavior modes does the autopilot profile support?

Three modes: `stop_at_green` (default, stops after CI passes), `automerge` (enables auto-merge, polls until merged, cleans up the branch), and `request_review` (marks the PR ready and posts a reviewer note).

Does autopilot work with Codex as well as Claude Code?

Yes. The skill uses Claude Code tool names by default, but `references/codex-adapter.md` maps each tool to Codex equivalents, including a sequential main-session fallback when Codex lacks a subagent primitive.

Can a project customize which skills autopilot invokes?

Yes. The profile's `## Required skills` table supports `replaces` rows that swap a universal skill for a project one, and `additional` rows that add mandatory skills. Removal of universal rows is not supported.

Why does autopilot stop before starting the workflow?

The most common cause is a missing `.workbench/autopilot.md` profile, which is a hard stop by design. It also stops when a required field (like a test command) cannot be resolved from the profile, session context, or filesystem detection.

Is the autopilot skill still maintained?

No. It is deprecated and superseded by `workbench:pilot`, which replaces both autopilot and copilot with one orchestrator and composable human gates. The archived copy is no longer maintained.