autopilot

<Purpose> Autopilot takes a brief product idea and autonomously handles the full lifecycle: requirements analysis, technical design, planning, parallel implementation, QA cycling, and multi-perspective validation. It produces working, verified code from a 2-3 line description. </Purpose> <Use_When> - User wants end-to-end autonomous execution from an idea to working code - User says "autopilot", "auto pilot", "autonomous", "build me", "create me", "make me", "full auto", "handle it all", or "I want a/an..." - Task requires multiple phases: planning, coding, testing, and validation - User wants hands-off execution and is willing to let the system run to completion </Use_When> <Do_Not_Use_When> - User wants to explore options or brainstorm -- use `plan` skill instead - User says "just explain", "draft only", or "what would you suggest" -- respond conversationally - User wants a single focused code change -- use `ralph` or delegate to an executor agent - User wants to review or critique an existing plan -- use `plan --review` - Task is a quick fix or small bug -- use direct executor delegation </Do_Not_Use_When> <Why_This_Exists> Most non-trivial software tasks require coordinated phases: understanding requirements, designing a solution, implementing in parallel, testing, and validating quality. Autopilot orchestrates all of these phases automatically so the user can describe what they want and receive working code without managing each step. </Why_This_Exists> <Execution_Po...