Full autonomous execution from idea to working code. Use when user says "autopilot", "autonomous", "build me", "create me", "make me", "full auto" — orchestrates spec → plan → code → QA → validation across the engineering layer agents.
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
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.
dev-plan instead@bolt-executordev-plan --reviewMost 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.
Turn the user's idea into a detailed spec.
dev-deep-interview for Socratic clarification before expanding@echo-analyst (Opus) extracts requirements, @apex-architect (Opus) creates technical specificationworkspace/projects/specs/[C]autopilot-spec-{name}.mdCreate an implementation plan from the spec.
@compass-planner (Opus): Create plan (direct mode, no interview)@raven-critic (Opus): Validate planworkspace/projects/plans/[C]autopilot-plan-{name}.mdImplement the plan.
@bolt-executor (Sonnet): Standard tasks@apex-architect for design before re-delegatingCycle until all tests pass.
Multi-perspective review in parallel.
@apex-architect: Functional completeness@vault-security: Vulnerability check (when imported in EPIC 3)@lens-reviewer: Quality review@oath-verifier: Final evidence-based completion check against acceptance criteriaGood:
Bad:
@hawk-debugger or @bolt-executor.dev-plan.