autopilot
Skill4 starsChanged todayMITView on GitHub
[oh-my-agy] Canonical autonomous orchestrator for hands-off delivery with durable state, consensus planning, and evidence-backed completion. Use when the user invokes $autopilot or asks for end-to-end autonomous delivery from an idea, issue, or requirements seed.
81 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- GongYuanCaiJi/jobsalvotheir own version, first seen Nov 16, 2026
- BoredHF/albertskillstheir own version, first seen Nov 16, 2026
- noelceta/content-enginetheir own version, first seen Nov 16, 2026
- kele-dev/Claude-Orchestrator-Skilltheir own version, first seen Nov 16, 2026
- mkritter3/codex-paired-superpowerstheir own version, first seen Nov 15, 2026
- stericishere/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use review-bugbot, rename-chat and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
0mlkrizzz655335vSkillreview-bugbot
缺陷导向代码审查。用 Bugbot 子代理找 bug。
Also in 3 projects that use this
0mlkrizzz655335vSkillrename-chat
重命名当前聊天。按聊天内容改标题。"disable-model-invocation: true
Also in 3 projects that use this
Tsumugii24Skillsplit-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
Also in 4 projects that use this
PandelisZSkillupdate-cli-config
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
Also in 3 projects that use this
32103210Skillmigrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.
Also in 3 projects that use this
32103210Skillupdate-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
Also in 3 projects that use this
- +1 more from 32103210
- +1 more from 0mlkrizzz655335v
Other versions81 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Yeachan-Heo/oh-my-codex★ 34k37% same
Wrote their own version · 80
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- SethGammon/Citadel★ 927same name
- H-mmer/pentest-agents★ 815same name
- Harry-kp/vortix★ 757same name
- nick-vels/skills★ 599same name
- yan-labs/yan-skills★ 307same name
- kentcdodds/kcd-skills★ 64same name
- Kanevry/session-orchestrator★ 53same name
- jantichy/claude★ 52same name
70 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- rules/AGENTS.mdAGENTS.md
- ai-slop-cleanerSkill
- analyzeSkill
- askSkill
- cancelSkill
- code-reviewSkill
- deep-interviewSkill
- deep-researchSkill
- doctorSkill
- hudSkill
- loftSkill
- modernizeSkill
- performance-goalSkill
- prSkill
- ralplanSkill
- releaseSkill
- skillSkill
- teamSkill
- threat-modelSkill
- ultragoalSkill
- ultraqaSkill
- visual-ralphSkill
- wikiSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 2 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 72 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Run or resume these stages in order:
- Very specific: line 33
When review or QA proves the requirements or plan wrong, keep Autopilot active, set its phase back to ralplan, attach the findings, and …
- Very specific: line 70
review/QA loopback: keep active:true, set current_phase:"ralplan", increment iteration, and persist return_to_ralplan_reason with the …
- Very specific: line 71
completion: write active:false, current_phase:"complete", completed_at.
- Very specific: line 72
cancellation: run $cancel. It preserves handoff artifacts for inspection or resume.
- Very specific: line 73
blocked on the user: write active:false, current_phase:"blocked", record the question in state.blocker, then ask.
- Very specific: line 77
When the user says continue, resume, or keep going, read .omagy/state/autopilot-state.json and continue from current_phase:
- Distinctive: line 85
Never discard valid handoff artifacts or restart discovery just because the conversation resumed.
“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Autopilot
<Purpose>
Autopilot is the canonical orchestrator for hands-off delivery. Its defining default chain is mandatory:$deep-interview -> $ralplan -> $ultragoalThe chain is not a list of optional hints, and Autopilot is not an alias for direct execution. Autopilot supervises each child stage in one recoverable session, carries durable artifacts forward, and continues through implementation verification until the requested outcome is complete or a genuine blocker is recorded.
</Purpose>
<Use_When>
- The user explicitly invokes
$autopilot. - The user asks for end-to-end autonomous delivery from an idea, issue, or requirements seed.
- The work needs requirements clarification, consensus planning, durable execution, and evidence-backed completion as one supervised workflow. </Use_When>
<Default_Chain> Run or resume these stages in order:
deep-interviewclarifies intent, scope, non-goals, constraints, acceptance criteria, and unresolved decisions, and produces a durable spec at.omagy/specs/deep-interview-<slug>.md. It is a real stage. Do not replace it with a one-question check or skip it just because the task looks actionable.ralplanturns the clarified requirements into an execution-ready consensus plan through Planner -> Architect -> Critic subagent review.ultragoalexecutes the approved plan through durable goals, ledger receipts, focused verification, cleanup, review, and terminal evidence.
$team, $code-review, and $ultraqa may run inside the supervised execution when the active Ultragoal plan or verification boundary requires them. They do not replace or weaken the three-stage chain.
When review or QA proves the requirements or plan wrong, keep Autopilot active, set its phase back to ralplan, attach the findings, and continue through ultragoal again. Implementation-only review fixes may stay inside Ultragoal's blocker/review loop.
</Default_Chain>
<Execution_Policy>
- A new run MUST begin at
deep-interviewand MUST keep the phase orderdeep-interview -> ralplan -> ultragoal. - Child stages are supervised phases, not peer workflow activations. Keep
mode:"autopilot"active and updatecurrent_phase. Do not create standalone child state files for the stages Autopilot supervises (child skills write their artifacts but not their own*-state.jsonwhile Autopilot owns the run). - Continue automatically through safe, reversible stage transitions. Stop only for an explicit user cancellation, a human-only dependency, or a verified terminal result.
- Deep-interview rounds use
ask_question. That is expected user interaction and does not count as a stop. - Authority-decreasing operations always stay available:
$cancel, exact-mode state clear, and disabling the plugin hooks. </Execution_Policy>
<State_Management>
Autopilot owns .omagy/state/autopilot-state.json. Start a new run by writing it with write_file (or write_to_file):
{
"mode": "autopilot",
"active": true,
"current_phase": "deep-interview",
"iteration": 1,
"started_at": "<ISO>",
"updated_at": "<ISO>",
"state": {
"task": "<user request>",
"phase_cycle": ["deep-interview", "ralplan", "ultragoal"],
"handoff_artifacts": { "deep_interview": null, "ralplan": null, "ultragoal": null, "code_review": null, "ultraqa": null },
"return_to_ralplan_reason": null
}
}Refresh updated_at on every write. The oh-my-agy Stop hook uses it to tell real progress from a stall. It re-enters the loop at most twice without a state change. When kicking off a new Autopilot run (and the oh-my-agy/hud sidecar is enabled), surface [oh-my-agy HUD](sidecar://oh-my-agy/hud/) once so the user can monitor phase transitions in the Auxiliary Pane.
Stage transitions:
deep-interview -> ralplan: requires the spec path inhandoff_artifacts.deep_interviewand a non-empty completion rationale.ralplan -> ultragoal: requires durable planning artifacts, sequential Architect then Critic approvals, and aralplan_execution_handoffwithsource:"autopilot"bound to this run's iteration. The explicit$autopilotrequest authorizes this supervised transition.ultragoal -> complete: requires every goal in.omagy/ultragoal/goals.jsoncomplete, ledger receipts, and fresh verification evidence matching the requested outcome.- review/QA loopback: keep
active:true, setcurrent_phase:"ralplan", incrementiteration, and persistreturn_to_ralplan_reasonwith the findings. - completion: write
active:false,current_phase:"complete",completed_at. - cancellation: run
$cancel. It preserves handoff artifacts for inspection or resume. - blocked on the user: write
active:false,current_phase:"blocked", record the question instate.blocker, then ask. </State_Management>
<Continuation_And_Resume>
When the user says continue, resume, or keep going, read .omagy/state/autopilot-state.json and continue from current_phase:
deep-interview: resume clarification from the saved context snapshot and transcript.ralplan: resume consensus planning from the spec and any loopback findings.ultragoal: resume durable execution from.omagy/ultragoal/goals.jsonand the ledger.blocked: re-read the recorded blocker, apply the user's answer, setactive:trueand the prior phase, and continue.complete: report the terminal evidence. Do not restart.cancelledorfailed: report the preserved artifacts. Start a new run only on a new explicit$autopilotrequest.
Never discard valid handoff artifacts or restart discovery just because the conversation resumed. </Continuation_And_Resume>
<Final_Checklist>
- The run started at
deep-interviewand produced a durable spec. - Ralplan produced an execution-ready plan with sequential Architect -> Critic approval evidence.
- Ultragoal completed every goal with ledger receipts.
$code-review(independent lanes) and verification evidence cover the requested behavior, failure paths, and recovery paths.- Autopilot state is terminal (
active:false) and all artifacts are coherent. </Final_Checklist>
<Examples>
<Good>
User: `$autopilot implement issue #42`
Flow: write autopilot state at `deep-interview`, interview with `ask_question` until the spec is ready, run supervised `ralplan` with architect and critic subagents, run supervised `ultragoal`, verify, run `$code-review`, and mark the state complete.
</Good>
<Good>
User: `continue`
Context: autopilot state has `current_phase:"ralplan"`.
Flow: resume planning from the existing spec. Do not start a separate standalone Ralplan run.
</Good>
<Bad>
Flow: treat `$deep-interview`, `$ralplan`, and `$ultragoal` as optional suggestions and jump directly to implementation.
Why bad: it hollows out Autopilot's defining orchestration contract.
</Bad>
</Examples>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

