autopilot

Builds the full product autonomously from discovery artifacts with simulator-driven gates and refinement cycles.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill autopilot-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autopilot
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/autopilot
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill autopilot-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Participating in every build gate is slow for solo builders who already have a complete discovery brief. Autopilot removes the solo from the build loop entirely — the framework builds every slice, plays every gate with a simulator, and only surfaces the product at phase test. ## Core Features & Use Cases - Pre-Flight Gap Check: Reads the discovery brief, to-be process map, tech context, and backlog, then surfaces every unresolved judgment call before any code is written. - Autonomous Slice Build: Builds all slices in backlog order, generates and runs pytest suites when CI/CD is configured, commits each slice, and logs every simulator gate decision to a decision file. - Refinement Cycles: Classifies post-build feedback as implementation issues (fixed via delta builds) or structural issues (routed back to guided mode), tracking refinement counts in metrics. - Use Case: A solo founder finishes discovery and a design sprint on Monday, invokes autopilot, and returns at phase test to review a fully built, committed product — then runs two refinement cycles to polish implementation details. ## Quick Start Invoke autopilot by name after discovery is complete, for example: run autopilot to build the full product from my discovery brief and backlog.

Frequently Asked Questions about autopilot

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

FAQPage Schema
How do I build a product autonomously with AI after discovery?

Invoke autopilot by name once your discovery brief, to-be process map, tech context, and sliced backlog exist. It runs a pre-flight gap check, locks a brief, then builds and commits every slice without further input until phase test.

What prerequisites does autopilot mode require before starting?

Four artifacts must exist: docs/discovery-brief.md, a to-be process map, docs/tech-context.md, and docs/backlog.md with slices. If any are missing, autopilot stops and names exactly what is needed before it can activate.

Can autopilot fix design or process flow problems after the build?

No. Refinement only handles implementation issues like wrong behavior or broken data flows. Structural issues that trace back to design or the process map require exiting to guided mode and re-entering through design review.

Does autopilot run tests during the autonomous build?

Yes, when CI/CD with GitHub Actions is in the tech context. It generates a pytest file per slice from the done criteria, runs the suite, fixes regressions before continuing, and commits the test file with the slice.

When should I not use autopilot mode?

Avoid it when discovery is thin or the to-be map has vague steps and missing edge cases, because simulator judgment calls accumulate and output drifts. It also never activates in guided, piloted, or bare mode unless explicitly invoked.