Autopilot Workflows - Use AI

What is Autopilot?

Autopilot is the most powerful skill in Claude Code, allowing you to describe a brief idea and let AI automatically complete the entire workflow: from requirements analysis, design, planning, implementation to testing and validation.

Instead of guiding each step, you simply say 'autopilot build me a todo app' and Claude handles everything automatically.

Autopilot Phases

Phase 0: Expansion

Your brief idea is expanded into a detailed spec. Analyst agent analyzes requirements, Architect agent creates technical design.

Expansion Phase

1# Your input:2"autopilot create a blog with posts and comments"34# Phase 0 output (.omc/autopilot/spec.md):5## Requirements6- User authentication7- CRUD operations for posts8- Nested comments system9- Markdown support10...

Phase 1: Planning

From the spec, Architect creates a detailed implementation plan with specific tasks. Critic agent reviews and validates the plan.

Planning Phase

1# Plan output (.omc/plans/autopilot-impl.md):2## Wave 1: Database Setup3- Task 1: Create Prisma schema4- Task 2: Setup database migrations56## Wave 2: API Layer7- Task 3: Posts CRUD endpoints8- Task 4: Comments endpoints9...

Phase 2: Execution

Tasks are executed in parallel when possible. Simple tasks use Haiku, complex tasks use Opus. Ralph skill ensures each task completes before continuing.

Execution Phase

1# Execution progress:2✓ Task 1: Create Prisma schema (Haiku)3✓ Task 2: Database migrations (Haiku)4⟳ Task 3: Posts CRUD (Sonnet) - in progress5⟳ Task 4: Comments endpoints (Sonnet) - in progress6○ Task 5: Frontend pages (Opus) - waiting

Phase 3: QA

UltraQA mode runs build, lint, tests and automatically fixes failures. Repeats up to 5 times until everything passes.

QA Phase

1# QA cycle:2Cycle 1:3  ✓ Build passed4  ✗ 3 lint errors → fixing...5  ✗ 2 test failures → fixing...67Cycle 2:8  ✓ Build passed9  ✓ Lint passed10  ✓ All tests pass

Phase 4: Validation

Multi-perspective review in parallel: Architect checks completeness, Security reviewer finds vulnerabilities, Code reviewer evaluates quality.

Using Autopilot

Autopilot Usage

1# Basic usage2/autopilot create a REST API for inventory management34# With more details5/autopilot build a dashboard with:6- user authentication7- charts for sales data8- export to CSV9- dark mode support1011# Keyword trigger (without slash)12"autopilot create a CLI tool for file organization"

When to Use Autopilot

New projects requiring multiple files and related features.
Complex features requiring planning, implementation, and testing.
When you want hands-off and let AI handle everything.

When NOT to Use

Simple bug fixes - use directly or /ralph instead.
Questions or explanations - just ask normally.
Small changes in one file - overkill for autopilot.

Info

Autopilot can run for extended periods (10-30 minutes for large projects). Use /cancel to stop and resume later.

Cancel and Resume

1# Cancel current autopilot2/cancel34# Resume (run autopilot again with same task)5/autopilot6# Claude will detect previous state and offer to resume

Key Takeaways

Điểm Chính

Autopilot handles entire projects from idea to working codeAutopilot xử lý toàn bộ dự án từ ý tưởng đến code hoạt động
5 phases: Expansion, Planning, Execution, QA, Validation5 giai đoạn: Expansion, Planning, Execution, QA, Validation
Best for complex multi-file features and new projectsTốt nhất cho tính năng phức tạp nhiều file và dự án mới
Use /cancel to stop, run /autopilot again to resumeDùng /cancel để dừng, chạy /autopilot lại để tiếp tục

Practice

Test your understanding of this chapter

Quiz

What happens in Phase 0 (Expansion) of Autopilot?

Điều gì xảy ra trong Phase 0 (Expansion) của Autopilot?

True or False

Autopilot should be used for simple one-line bug fixes.

Autopilot nên được dùng cho bug fix đơn giản một dòng.

Code Challenge

Complete the command to cancel a running autopilot

Hoàn thành lệnh để hủy autopilot đang chạy

Quiz

How many QA cycles does Autopilot run at maximum?

Autopilot chạy tối đa bao nhiêu QA cycles?