autopilot

Execute PLAN, BUILD, and REVIEW coding workflows with human approval gates.

2|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/iadr-dev/colab --skill autopilot-iadr-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autopilot
Source: https://github.com/iadr-dev/colab/tree/main/skills/autopilot
Command: npx skills add https://github.com/iadr-dev/colab --skill autopilot-iadr-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents slow, error-prone coding sessions by orchestrating a full implementation loop that includes planning, building, and verification, while still letting you approve the plan before work starts.

Core Features & Use Cases

  • Chain orchestration: Runs PLAN → BUILD → REVIEW in order, keeping tasks structured.
  • Human-in-the-loop gating: Pauses after the plan so you can confirm or reject before implementation proceeds.
  • Iterative correction: If REVIEW finds failing items, it reruns BUILD and re-checks until the review passes.
  • Use case: Turn a feature request like “add OAuth refresh handling” into a complete, tested implementation plan and validated changes, then decide whether to ship.

Quick Start

Run /ohc-autopilot and describe what you want to build, then type go when the plan is shown.

Frequently Asked Questions about autopilot

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

FAQPage Schema
How do I automate an end-to-end coding workflow with a human approval pause?

Test-driven build and review cycles verify implementation quality by checking changes against specifications during the REVIEW phase. If review finds failing items, it automatically reruns BUILD and re-checks until the review passes.

How do I implement a feature request with iterative planning and test-driven development?

Iterative planning and test-driven development work by chaining PLAN, BUILD, and REVIEW phases together. The workflow writes plans into .ohc/plans/ and coordinates sub-workflows and gates, prompting you for final shipping only when review succeeds.

Can I skip the human approval gate during automated code review and build orchestration?

Yes, workflow gating includes an optional autopilot no-gate mode that skips the human approval pause. This lets the PLAN, BUILD, and REVIEW chain execute continuously without waiting for manual confirmation.

What is workflow gating in software feature implementation and when do I need it?

Workflow gating is a pause mechanism in automated coding orchestration that stops execution after the planning phase for human confirmation. You need it when feature implementation requires iterative test-driven builds and quality compliance checks with human oversight.

Does automated code orchestration support iterative correction when review finds failing items?

Yes, if REVIEW finds failing items, the orchestration automatically reruns the BUILD phase and re-checks the output. This iterative correction loop continues until the review passes and all changes pass verification.