Autopilot
Builds an app, site, bot, or feature end-to-end from a dictated idea, requirements...
Install
npx skills add nick-vels/skills --skill autopilot -g -a claude-code -y- Repository
- nick-vels/skills582
- Category
- Engineering
- Updated
- 7d ago
- License
- MIT
- Context cost
- Mediumabout 2,440 tokens
- Runs scripts
- Yes, review before use
What it does
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.
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 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.
