← Search

Autopilot: end-to-end vibecoding orchestrator — brief to working project in one dialogue
AI agents 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 326c6ea
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: nothing to install…

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

Dictated-build pipeline with modes (full/semi/interview/manual), a numbered requirements manifest, gated phases, and hard secrets redaction — user-facing labels in Russian

Version:

Quick answer

Autopilot is a self-contained orchestrator skill that takes a dictated app, site, bot or feature from words to a working project in one dialogue. The brief first becomes a numbered requirements manifest, then runs through nine gated phases — with four modes (full, semi by default, interview, manual) — while the orchestrator coordinates the work instead of writing project code itself. The chat and dashboard label each stage with a single Russian word, by design.

At a glance

What it isA dictated-build pipeline: your brief becomes a numbered requirements manifest, then nine gated phases (preflight, manifest, briefing, spec, plan, subagents, review, final) carry it to a working project. It ships an instruments dashboard (state.js and dashboard.html) and keeps the run's record in a committed .autopilot/ project folder.
Who it's forPeople who want to dictate what to build and follow the run on a dashboard rather than approve every stage by hand — and who are comfortable with a heavy methodology where a long build means a long run.
What you give itYour brief, dictated or written, plus your choices along the way: a mode (full, semi, interview or manual), depth and finish settings. Requirements are only ever removed by you, and irreversible actions come back to you as questions.
What you getA working project produced through the gated phases, a live instruments dashboard for the run, and the .autopilot/ folder committed as the project's memory of how it was built.
Works withInstalled from this listing with the copy-paste install prompt into Muse. Five rules hold throughout: secrets are never requested, echoed or written (a redaction gate at ingest, and .env in .gitignore before the first commit), and facts about you are never invented.
CostFree
TimeA few minutes to install. Each run lasts as long as the build itself — the listing is explicit that this is a heavy methodology, so expect a long run for a long build.

Example — dictating a small site

An example of a typical use, following the phases the skill documents — not a reported result.

  • You dictate the site you want; Autopilot turns the brief into a numbered requirements manifest so nothing can quietly vanish, and you pick the semi mode.
  • The run moves through its gated phases — briefing, spec, plan, subagents, review — while you watch progress on the instruments dashboard, each stage labelled with its Russian stage word.
  • At the end, the .autopilot/ folder is committed as the record of the run, and the project is presented for blind acceptance.
⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 326c6ea

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/nick-vels/skills/326c6ea3b5aa278e2874aeacacf9ad82ad103422/skills/autopilot/SKILL.md Pinned version: install the code at commit 326c6ea3b5aa278e2874aeacacf9ad82ad103422 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file AND the whole phases/ folder from the repository into a temporary folder 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.

🧪 Example
You ask
/autopilot semi — Just build it: a one-page site for my snow-removal business, with services, prices and a contact form.
You get
Your words are now a numbered manifest — every requirement has a status, none left open. Plan: a ticket per piece of work, one commit per ticket. … building … Done: the finished site, checked blind against your own brief (not against my paraphrase of it). The full record — brief, manifest, spec, tickets — lives in .autopilot/. Report and my assumptions are listed here in chat; prices you didn't give me stayed as visible placeholders, never invented.
Illustrative example based on this skill’s own documentation — not a real user’s result.
🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 326c6ea · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
326c6ea · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.