autopilot
Full autonomous execution from idea to working code
>_
Quick Installnpxskills add yeachan-heo/oh-my-claudecode--skill autopilotInstructions
Loading…
Tags & Topics
agentic-codingai-agentsclaudeclaude-codeoh-my-opencodeopencode
Full autonomous execution from idea to working code
npxskills add yeachan-heo/oh-my-claudecode--skill autopilotLoading…
<Use_When>
<Do_Not_Use_When>
plan skill insteadralph or delegate to an executor agentplan --review<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_Policy>
/oh-my-claudecode:cancel at any time; progress is preserved for resume
</Execution_Policy>Phase 1 - Planning: Create an implementation plan from the spec
.omc/plans/autopilot-impl.mdPhase 2 - Execution: Implement the plan using Ralph + Ultrawork
Phase 3 - QA: Cycle until all tests pass (UltraQA mode)
Phase 4 - Validation: Multi-perspective review in parallel
Phase 5 - Cleanup: Delete all state files on successful completion
.omc/state/autopilot-state.json, ralph-state.json, ultrawork-state.json, ultraqa-state.json/oh-my-claudecode:cancel for clean exit
</Steps>
<Tool_Usage>
Task(subagent_type="oh-my-claudecode:architect", ...) for Phase 4 architecture validationTask(subagent_type="oh-my-claudecode:security-reviewer", ...) for Phase 4 security reviewTask(subagent_type="oh-my-claudecode:code-reviewer", ...) for Phase 4 quality review<Escalation_And_Stop_Conditions>
/deep-interview for Socratic clarification, or pause and ask the user for clarification before proceeding
</Escalation_And_Stop_Conditions><Final_Checklist>
.omc-workspace marker at the parent directory so multiple sessions across sub-repos share one .omc/. Resolution order: OMC_STATE_DIR > .omc-workspace > git > cwd. See docs/REFERENCE.md.Optional settings in .claude/omc.jsonc (project) or ~/.config/claude-omc/config.jsonc (user):
{
"autopilot": {
"maxIterations": 10,
"maxQaCycles": 5,
"maxValidationRounds": 3,
"pauseAfterExpansion": false,
"pauseAfterPlanning": false,
"skipQa": false,
"skipValidation": false,
"execution": "solo"
}
}
To run autopilot implementation through the tmux CLI team runtime and prefer Cursor executor workers:
{
"autopilot": {
"execution": "team",
"team": { "agentTypes": ["cursor"] }
}
}
With that config, the execution stage must launch executor-style work through:
omc team 1:cursor "<implementation task>"
or the Claude Code slash compatibility surface:
/omc-teams 1:cursor "<implementation task>"
Limitations:
cursor-agent CLI to be installed and authenticated. If cursor-agent is unavailable, report that setup requirement instead of silently falling back to Claude-only execution.If autopilot was cancelled or failed, run /oh-my-claudecode:autopilot again to resume from where it stopped.
Stuck in a phase? Check TODO list for blocked tasks, review .omc/autopilot-state.json, or cancel and resume.
QA cycles exhausted? The same error 3 times indicates a fundamental issue. Review the error pattern; manual intervention may be needed.
Validation keeps failing? Review the specific issues. Requirements may have been too vague -- cancel and provide more detail.
When autopilot is invoked with a vague input, Phase 0 can redirect to /deep-interview for Socratic clarification:
User: "autopilot build me something cool"
Autopilot: "Your request is open-ended. Would you like to run a deep interview first?"
[Yes, interview first (Recommended)] [No, expand directly]
If a deep-interview spec already exists at .omc/specs/deep-interview-*.md, autopilot uses it directly as Phase 0 output (the spec has already been mathematically validated for clarity).
The recommended full pipeline chains three quality gates:
/deep-interview "vague idea"
→ Socratic Q&A → spec (ambiguity ≤ 20%)
→ /ralplan --direct → consensus plan (Planner/Architect/Critic approved)
→ /autopilot → skips Phase 0+1, starts at Phase 2 (Execution)
When autopilot detects a ralplan consensus plan (.omc/plans/ralplan-*.md or .omc/plans/consensus-*.md), it skips both Phase 0 (Expansion) and Phase 1 (Planning) because the plan has already been:
Autopilot starts directly at Phase 2 (Execution via Ralph + Ultrawork). </Advanced>
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).