autopilot

Runs one bounded spec, build, check, and audit loop for a single feature or fix.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill autopilot-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autopilot
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/autopilot
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill autopilot-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually driving a feature through spec writing, branching, implementation, verification, and auditing requires constant supervision at every step. This Skill executes one bounded end-to-end pass on explicit request, producing a review packet instead of forcing you to babysit each stage. ## Core Features & Use Cases - Bounded Autonomous Loop: Picks or resumes a feature, writes or critiques the spec, creates the branch, implements in small verified steps, and stops with a review packet. - Checkpoint Commits: Creates a conventional checkpoint commit after each passing step on the feature or fix branch, keeping progress recoverable. - Targeted Audit and Repair: Audits only the changed code, repairs confirmed P0/P1 findings within scope, and records findings in a durable ledger. - Hard Safety Stops: Never merges, pushes, deploys, deletes data, or performs destructive actions without explicit approval. - Use Case: You run /autopilot 3 to target the third build-plan item; it writes the spec, implements each step with passing checks, audits the diff, and hands you a review packet ready for /complete. ## Quick Start Ask the agent to run /autopilot on a specific build-plan item, for example by saying run autopilot on the directory listing feature.

Frequently Asked Questions about autopilot

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

FAQPage Schema
How do I run an autonomous feature implementation loop?▼

Invoke /autopilot explicitly, optionally with a build-plan number or feature name. It writes or resumes the spec, implements steps with verification, creates checkpoint commits, audits the diff, and stops with a review packet.

What is the difference between autopilot and the normal implement workflow?▼

The normal /feature, /implement, /check, and /complete commands pause for review at each stage. Autopilot runs one bounded loop without per-step pauses, but still stops before /complete and never merges or pushes.

Can autopilot merge, push, or deploy code?▼

No. Autopilot only creates checkpoint commits on the feature or fix branch. Merging, pushing, deploying, publishing, deleting data, and other destructive actions are hard stops requiring explicit approval through other commands.

What happens when autopilot finds a high-severity audit issue?▼

Confirmed P0 and P1 findings are repaired if the fix stays within the approved feature scope, then checks are rerun and the finding is updated in findings.md. If a safe repair is not possible, the run stops and reports the blocker.

When does autopilot stop before finishing a feature?▼

It stops when the repo is not a git repo, the working tree has unrelated dirty changes, the target conflicts with an active feature, a product decision is missing from the docs, or the same fix fails twice.