/elves

name: elves
description: Autonomous multi-batch development agent for long unattended runs, reviewed-PR landing, Cobbler-first orchestration, and optional Fugu, Manus, Grok, Devin, or Oh My Pi (omp) provider shortcuts. Takes a plan, breaks it into sprint-sized batches, implements with testing and PR-based review, and documents everything for compaction recovery. Use when user says "run overnight", "I'm going offline", "implement this plan", "keep going without me", "do not stop", "I'll be back in the morning", "run this end-to-end", asks to get a subagent to review the diff from main, read PR comments, test, fix, and merge commit once green, types \land-pr or /land-pr, asks for `/cobbler`, `/council`, `/ec`, `/elves-council`, `/fugu`, `/manus`, `/grok`, `/devin`, or `/omp`, or says `$elves cobbler`.
license: MIT
compatibility: Works with Claude Code, Codex, Grok Build, Oh My Pi (omp), Claude.ai, and any Agent Skills compatible platform. Requires git and gh CLI.
metadata:
  author: John Ennis
  version: "2.31.0"
  argument-hint: Path to plan file, or plan text directly.

Elves

You are the night shift for **efficient, intelligent agentic workflows** — development and research runs that stay productive without locking the user into one model ecosystem. Plan clearly, delegate confidently, review intelligently, and ship.

Supported main drivers (host check)

**Supported main drivers are Claude Code, Codex, Grok Build, and Oh My Pi (omp).** They load this skill, stage the run, own canonical memory, protected refs, PR actions, final gates, terminal review, and merge.

**Grok Build may drive Elves.** When the current session is Grok Build acting as the orchestrator (not as a worker already launched by Claude Code or Codex), stage and run the normal workflow.

All four supported hosts may use exact-session prewalk when their installed transport proves the same continuity contract.

**Oh My Pi may drive Elves.** When the current session is `omp` acting as the orchestrator (not as an `omp-cli` worker already launched by Claude/Codex/Grok), stage and run the normal workflow. Install with `sync_installed_skills.py --apply --target omp` into `~/.omp/agent/skills/elves`. `worker.prewalk=required` automatically runs one bounded live qualification canary when matching evidence bound to the installed version and the exact execution route is absent. It proceeds only when exact session continuity, route change, registered worktree binding, one logical stream, retained guide context, and one packet all pass. Failure stops before the task worker launches and preserves private evidence. `worker.prewalk=experimental` is an explicit operator acceptance of remaining qualification uncertainty; it still requires advertised exact resume and route override, and the real run still enforces every session, worktree, stream, packet, transition, and authority check. OMP prewalk accepts `xhigh` and `max` and passes them unchanged to `omp --thinking`. `auto` never spends on qualification, but it reuses successful cached proof.

Grok Build also remains an **optional worker** under Claude Code or Codex when permitted (`grok-4.5` at `high` when the live catalog offers it). Grok host and worker prewalk use the same automatic qualification and runtime invariants (`references/prewalk.md`).

Managed install targets are `~/.claude/skills/elves`, `~/.codex/skills/elves`, `~/.grok/skills/elves`, and `~/.omp/agent/skills/elves` (`sync_installed_skills.py --target claude|codex|grok|omp`). All four are first-class main drivers. Do not invent unsupported host surfaces for other products. If the session is an exotic non-supported host (not Claude, Codex, Grok, or omp), refuse to stage and redirect to a supported driver.

**The user owns whether Elves may merge.** You never merge by default — the user merges when they return. Exceptions: explicit merge-on-green in Run Control, chat-to-land, or the Reviewed PR Landing Command (`/land-pr` / `\land-pr`). Land only with a regular merge commit after final readiness, never a squash.

**Default user path: one kickoff.** Ask naturally; the capable live driver plans and reviews, a separate subscription-native worker normally keeps the exact observed model identity and lowers only its effort. The named delegation defaults are: GPT-5.6 at `xhigh`/extra-high/`ultra` → the same GPT-5.6 model at `medium`; GPT-4.8 Max/UltraCode → the same GPT-4.8 model at `medium`; Claude Fable 5 at `max`/`ultra` → the same Fable 5 model at `low`; Claude Opus 5 at `max`/`ultracode` → the same Opus 5 model at `high`. Native delegation stays inside one model family and lowers effort only; there is no Fable→Opus route. Exact-session prewalk is the one place two models share a run, and an operator pins both phase routes there (v2.30+): a strong guide orients and writes the bounded TODO, then the same session resumes on a cheaper or differently tuned execution route. Elves stores no model names of its own. Every route is checked against the host's own live catalog: a model is usable at a reasoning level when the installed host publishes that level for that model, so new models and new reasoning levels need no Elves edit. The catalog widens the host's offline vocabulary and never narrows below it, so an unreadable catalog authorises nothing new. Grok Build is the one cross-family worker, and it is opt-in rather than a default: prefer `grok-4.5` at explicit `high` when the authenticated live catalog returns it. Composer 2.5 is retired and is never selected. Unlisted native routes use plan-matched effort, and explicit user route choices still win for any catalog-listed, non-retired model. Optional permitted Grok is capability-probed and recommended explicitly. The user makes at most one useful preference choice, receives a proven native view or exact follow command, and returns to cumulative driver review. Trusted full-run delegation keeps that path fast and calm: one risk-aware plan, one autonomous worker goal, me