Omh Autopilot logo

Omh Autopilot

Community
witt3rd
omh-autopilot

pipeline: interview→plan→execute→QA→verify (idea→code)

Overview

Publisherwitt3rd
Repositoryoh-my-hermes
Skill nameomh-autopilot
Stars
371
Forks
33
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by witt3rd on GitHub. Read the source before you install it.

Installation

Install the Omh Autopilot AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/witt3rd/oh-my-hermes/tree/master/plugins/omh/skills/omh-autopilot
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/witt3rd/oh-my-hermes.git /tmp/oh-my-hermes
mkdir -p .claude/skills
cp -r /tmp/oh-my-hermes/plugins/omh/skills/omh-autopilot .claude/skills/omh-autopilot
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Omh Autopilot in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Omh Autopilot on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Omh Autopilot is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OMH Autopilot — End-to-End Autonomous Pipeline

When to Use

  • End-to-end feature implementation from idea to verified, reviewed code
  • The user says: "autopilot", "build me", "handle it all", "e2e this"

When NOT to Use

  • Single-file changes or trivial tasks (just do them)
  • You want to stay in one continuous session (autopilot is multi-session)
  • You only need planning (omh-ralplan) or execution (omh-ralph)

Prerequisites

  • The omh plugin must be installed (~/.hermes/plugins/omh/)

Architecture: One Phase Step Per Invocation

Each autopilot invocation reads state, does ONE unit of work, exits. The caller re-invokes. This preserves fresh context at every level — including during the ralph loop.

Invocation 1:   Phase 0 — requirements (or skip)
Invocation 2:   Phase 1 — planning (or skip)
Invocations 3-N: Phase 2 — ralph iterations (one per call)
Invocation N+1: Phase 3 — QA cycle         [FRESH SESSION]
Invocation M:   Phase 4 — validation round  [FRESH SESSION]
Final:          Phase 5 — cleanup → complete

See references/caller-examples.md for how to drive the loop.

Procedure

Step 0: Resolve Instance and Acquire Lock

Autopilot drives a goal through spec → plan → ralph → QA → validation. Two autopilot sessions on the same goal would race on autopilot, ralph, and ralph-tasks state simultaneously. Use per-instance state

  • advisory lock.
  1. Resolve instance_id in this order:
    • If a confirmed spec exists at .omh/specs/{name}-spec.md, use instance_id = "{name}".
    • Else if a plan exists at .omh/plans/ralplan-{slug}.md, use instance_id = "{slug}".
    • Else derive from the goal: instance_id = kebab(goal)[:60].
  2. Acquire the autopilot lock:
    lock = omh_state(action="lock", mode="autopilot",
                     lock_key="{instance_id}",
                     session_id="{HERMES_SESSION_ID or uuid}",
                     holder_note="autopilot driving {goal_or_plan}")
    On acquired=false, report held_by, offer wait/cancel/different goal. Stale-pid auto-release applies.
  3. Pass instance_id to every omh_state call in this invocation (autopilot, ralph, ralph-tasks).
  4. When dispatching to ralph in Phase 2, pass the same instance_id in the delegation context so the ralph subagent acquires mode="ralph" lock on the same slug.
  5. Release the autopilot lock at every exit point (paused, blocked, complete, exception):
    omh_state(action="unlock", mode="autopilot",
              lock_key="{instance_id}",
              session_id="{HERMES_SESSION_ID or uuid}")

Singleton fallback (legacy). Omitting instance_id writes .omh/state/autopilot-state.json and skips locking. Acceptable only when running one autopilot at a time.

On Every Invocation: Dispatch

state = omh_state(action="read", mode="autopilot", instance_id="{instance_id}")
  • Not found: Fresh start → Smart Detection (below)
  • Found: Check context_checkpoint flag → if true, clear it and exit (phase boundary)
  • Check staleness: state.stale = true → warn, offer fresh start
  • Check pause: if pause_after_phase matches current completed phase → set phase="paused", exit
  • Dispatch to current phase handler

Smart Detection (Fresh Start)

When no autopilot state exists, detect artifacts:

  1. Confirmed spec in .omh/specs/*-spec.md → create state at Phase 1
  2. Consensus plan in .omh/plans/ralplan-*.md → create state at Phase 2
  3. Ralph complete (omh_state(action="check", mode="ralph", instance_id="{instance_id}") → phase="complete") → create state at Phase 3
  4. Nothing → create state at Phase 0

Check for active ralph: omh_state(action="check", mode="ralph", instance_id="{instance_id}") → if active, warn about existing session.

omh_state(action="write", mode="autopilot", instance_id="{instance_id}", data={
    "phase": "requirements", "goal": "...", "ralph_iteration": 0,
    "qa_cycle": 0, "max_qa_cycles": 5, "validation_round": 0,
    "max_validation_rounds": 3, "validation_verdicts": {},
    "skip_qa": false, "skip_validation": false, "pause_after_phase": null
})

Phase 0: Requirements

Goal: Ensure a confirmed spec exists.

  1. Check .omh/specs/*-spec.md with status: confirmed → found? Set spec_file, advance to Phase 1, exit
  2. Not found — assess input:
    • Concrete (file paths, function names, specific tech): generate inline spec, advance
    • Vague: Load omh-deep-interview and follow it. This phase is interactive.
  3. Update state: phase: "planning", spec_file: "<path>". Exit.

For fully autonomous runs: run omh-deep-interview separately first.

Phase 1: Planning

Goal: Ensure a consensus plan exists.

  1. Check .omh/plans/ralplan-*.md → found? Set plan_file, advance to Phase 2, exit
  2. Not found: Load omh-ralplan, follow its procedure with the spec as input
  3. Update state: phase: "execution", plan_file, ralph_iteration: 0, context_checkpoint: true. Exit.

Phase 2: Execution (Ralph Iterations)

Each invocation performs exactly ONE ralph iteration:

  1. Run one ralph iteration via delegate_task with the omh-ralph skill context:
    delegate_task(goal="[omh-role:executor] Follow the omh-ralph skill procedure:
      read state, pick the next incomplete task, execute it, verify, update state, exit.",
      context="<current ralph state + plan file contents>")
  2. After ralph completes its step, check ralph status:
    ralph = omh_state(action="check", mode="ralph", instance_id="{instance_id}")
    • active=true → increment ralph_iteration, exit (caller re-invokes)
    • phase="complete" → advance: phase: "qa", context_checkpoint: true, exit
    • phase="blocked" → set autopilot phase: "blocked", report, exit

Phase 3: QA Cycling

Each invocation performs ONE QA cycle. Starts in fresh session (context_checkpoint).

If skip_qa: true → advance to Phase 4, exit.

  1. Gather evidence using the project's actual build/test/lint commands (check for Makefile, package.json, Cargo.toml, pyproject.toml, etc. to determine the right commands):
    evidence = omh_gather_evidence(commands=["<build>", "<test>", "<lint>"])
  2. If evidence.all_pass → advance: phase: "validation", context_checkpoint: true, exit
  3. If failures:
    • Increment qa_cycle. Check 3-strike on qa_error_history. If triggered → phase="blocked", exit
    • If qa_cycle > max_qa_cycles (default 5) → phase="blocked", exit
    • Delegate diagnosis to architect subagent (read-only)
    • Delegate fix to executor subagent
    • Update state, exit (next invocation re-runs QA)

Phase 4: Multi-Reviewer Validation

Each invocation performs ONE validation round. Starts in fresh session.

If skip_validation: true → advance to Phase 5, exit.

  1. Gather evidence using the project's actual build/test commands:
    evidence = omh_gather_evidence(commands=["<build>", "<test>"])
  2. Delegate 3 parallel reviews (exactly 3 = Hermes concurrent limit):
    delegate_task(tasks=[
        {goal: "[omh-role:architect] Architectural review:\n{spec + plan}", context: "{evidence}"},
        {goal: "[omh-role:security-reviewer] Security review:\n{changed files list}", context: "{evidence}"},
        {goal: "[omh-role:code-reviewer] Code quality review:\n{changed files list}", context: "{evidence}"}
    ])
  3. Record verdicts in validation_verdicts
  4. All APPROVE → advance to Phase 5, exit
  5. Any REQUEST_CHANGES → delegate fix to executor, increment validation_round, exit
  6. If validation_round > max_validation_rounds (default 3) → phase="blocked", exit

Phase 5: Cleanup

  1. Set phase: "complete" (safety — if interrupted, re-invocation retries cleanup)
  2. Delete state files:
    omh_state(action="clear", mode="autopilot", instance_id="{instance_id}")
    omh_state(action="clear", mode="ralph", instance_id="{instance_id}")
    omh_state(action="clear", mode="ralph-tasks", instance_id="{instance_id}")
  3. Preserve: .omh/logs/, .omh/plans/, .omh/specs/
  4. Report completion summary: goal, phases completed, ralph iterations, QA cycles, validation rounds

State Management

All state via omh_state tool. Atomic writes and staleness handled automatically.

Sentinel Convention

omh_state(action="check", mode="autopilot", instance_id="{instance_id}")
→ {exists, active, phase, stale}

Pitfalls

  • Don't loop ralph in a single session. Each ralph iteration is a separate invocation. Context exhaustion is real.
  • Don't reimplement ralph. Load the skill, follow its procedure.
  • Phase boundaries = fresh sessions. Respect context_checkpoint.
  • Don't skip QA. Ralph verifies per-task. QA catches integration issues.
  • Phase 0 is interactive if no spec exists. Pre-create specs for automated runs.
  • 3 subagent limit. Phase 4 uses all 3 slots for parallel review.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Omh Autopilot AI skill do?

pipeline: interview→plan→execute→QA→verify (idea→code)

Why use Omh Autopilot on TypingMind?

Because you install it once and use it with any model. Omh Autopilot is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Omh Autopilot in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/witt3rd/oh-my-hermes/tree/master/plugins/omh/skills/omh-autopilot. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Omh Autopilot?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Omh Autopilot?

As many as you like. As long as a model supports skills, you can use Omh Autopilot with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Omh Autopilot AI skill free?

Yes. It is published on GitHub by witt3rd under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇