ohmg — Cross-vendor portable multi-agent harness (oh-my-agent v10.4.1)

When to use this skill

• You want to adopt oh-my-agent as a portable multi-agent harness across any AI IDE
• You want a single .agents/ source of truth that projects into Claude Code, Codex, Gemini, Antigravity, Cursor, Grok Build, Kimi Code, OpenCode, Pi, Qwen Code, Reasonix, Amp, GitHub Copilot, or Kiro CLI
• You need OMA equivalents for Claude /team, /autopilot, /ultrawork, or /ultraqa on any runtime
• You need specialized domain agents (frontend, backend, architecture, QA, PM, DB, mobile, infra, debug, design, etc.) that stay consistent across runtimes
• You need to explain when native generated agent files are used versus when oma agent:spawn fallback is required
• You want the vendor-agnostic harness path without locking into the full Claude-first (omc) or Codex-first (omx) runtime stacks

Instructions

Step 1: Identify the runtime and desired ownership model

Determine which of these the user actually wants: