Autopilot: end-to-end vibecoding orchestrator — brief to working project in one dialogue

Prerequisites: nothing to install — the skill is a build methodology your agent follows; each phase's rules live in the repo's phases/ folder, so install the whole folder, not just the entry file Install "Autopilot: end-to-end vibecoding orchestrator — brief to working project in one dialogue" for me. It gives my agent @nick-vels's self-contained orchestrator: dictate an app, site, bot or feature and get a working project in one dialogue — numbered requirements manifest, nine gated phases, four modes (full/semi/interview/manual), depth and finish dials, hard secrets redaction, an instruments dashboard, committed run memory, and blind acceptance at the end. MIT-licensed. Repository: https://github.com/nick-vels/skills/blob/main/skills/autopilot/SKILL.md 1. Fetch the SKILL.md file AND the whole phases/ folder from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "autopilot". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. dictate the brief — e.g. "/autopilot full build me a habit tracker" — the user-facing stages show in Russian by design). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.