Skills

Omp Delegate

Delegate a coding task to Oh My Pi (`omp`) as a background implementer, then review its...

Install

npx skills add amElnagdy/delegate-skills --skill omp-delegate -g -a claude-code -y
Category
Engineering
Updated
6d ago
License
MIT
Context cost
Mediumabout 2,220 tokens
Runs scripts
Yes, review before use

What it does

Delegate a coding task to Oh My Pi (`omp`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Oh My Pi / omp - phrasings like "have omp implement X", "delegate this to oh my pi", "run it through omp", "use oh-my-pi to implement/fix/refactor" - or wants to run a queue of coding tasks through omp while staying the reviewer. DO NOT USE for tasks small enough to do inline, when the user wants the code written directly without delegating, or when they mean the original Pi CLI (`pi`), that is pi-delegate.

Oh My Pi Delegate

You are the orchestrator. Delegate a bounded coding task to a separate implementer - Oh My Pi (omp) - then review what it produced and land it yourself. You write the brief and own the judgment; the implementer makes changes in its own session; you verify and commit.

The loop needs only a shell command and file access, so any comparable orchestrator can drive it.

The binary is omp, not pi

Oh My Pi is a fork of Pi. This skill drives omp (@oh-my-pi/pi-coding-agent). The original Pi CLI is a different binary (pi) with a different skill (pi-delegate). If omp is missing but pi is installed, you have Pi, not Oh My Pi.

When NOT to use this

  • The task is small enough to do inline; delegation overhead is not worth it.
  • The omp CLI is not installed or authenticated.
  • The user asked for the original Pi CLI (pi), use pi-delegate.
  • You need a sandboxed implementer. Oh My Pi has no sandbox. --read-only restricts the tool surface; a write-capable run executes without prompts (--yolo).

Prerequisites (check once)

  1. Install omp with bun install -g @oh-my-pi/pi-coding-agent (or the install path from https://omp.sh).
  2. Authenticate: /login inside omp for a subscription provider, or an API-key environment variable for an API-key provider. Credentials live under ~/.omp/.
  3. Confirm omp --version succeeds.
  4. Work in, or point --cd at, the target git repository.

Choose the model (optional)

Omit --model (and --provider) to use omp's configured default for this project / profile. The catalog is this install's authenticated providers, not a fixed list in this skill.

To pick another model:

Read the whole SKILL.md on GitHub

More in Engineering