What problem does it solve? Non-trivial coding tasks often fail because requirements are vague, planning is skipped, and code ships without review or QA. Autopilot enforces a strict autonomous loop that takes a raw idea or issue through clarification, consensus planning, durable implementation, code review, and adversarial QA before declaring completion. ## Core Features & Use Cases - Strict Phase Pipeline: Runs deep-interview, ralplan, ultragoal, code-review, and ultraqa in order, with automatic return-to-planning when review or QA gates are not clean. - Durable State Management: Persists phase, iteration, review verdicts, and handoff artifacts via the omx state CLI so work can be resumed with "continue" after interruption. - Consensus Gating: Requires sequential Architect and Critic approvals before implementation begins, preventing unreviewed plans from reaching execution. - Use Case: A user says "$autopilot implement GitHub issue #42" and the loop clarifies requirements, produces an approved plan, implements and verifies the change, then iterates through code review and QA until both gates are clean. ## Quick Start Ask the assistant to run autopilot on your task, for example by saying "use autopilot to build the password reset feature from issue #42".