# Autopilot

Builds an app, site, bot, or feature end-to-end from a dictated idea, requirements...

- Repository: https://github.com/nick-vels/skills (582 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-28
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add nick-vels/skills --skill autopilot -g -a claude-code -y`
Codex: `npx skills add nick-vels/skills --skill autopilot -g -a codex -y`
Cursor: `npx skills add nick-vels/skills --skill autopilot -g -a cursor -y`
Gemini CLI: `npx skills add nick-vels/skills --skill autopilot -g -a gemini-cli -y`

## Description

Builds an app, site, bot, or feature end-to-end from a dictated idea, requirements, briefing, spec, tickets, subagents, review, acceptance, with a live dashboard, for users who expect a finished result without reviewing specs or code. Starts only on /autopilot; a bare /autopilot resumes an interrupted run.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Autopilot

Autopilot flies a dictated idea from words to a working project **in one dialogue**, without making the user approve each stage. Every rule it needs lives in `phases/` and `prompts/`; no other skill has to be installed.

**The order is the product.** Code is written in the second-to-last phase. Everything before it decides *what* to build; everything after it proves the right thing got built.

**The brief is the contract, not the design.** *Nothing may quietly vanish*: the user's words become a numbered manifest before anything else, and every phase is gated on it, what breaks naive vibecoding is a requirement that stopped existing around the third rewrite. And *the brief is a silhouette*: it describes the happy path and nothing underneath, so working out the empty states, failures and limits is legitimate work. How far to take it is the user's [depth](phases/0-modes.md) dial; depth that **detaches** from the brief is never allowed.

## Reading this skill

This file is the orchestrator: order, gates, the rules that never lose. Each phase's rules are in its own file, **read when that phase starts and not before**, one file at a time, never ahead: a file opened early stays in the one context that is never refreshed for the rest of the run.

The rest: https://github.com/nick-vels/skills/blob/HEAD/skills/autopilot/SKILL.md