omg
OMG — Integrated Agent Orchestration
Keyword:
omg·annotate·UI검토·agentui (deprecated)| Platforms: Claude Code · Codex CLI · Gemini CLI · OpenCodeA unified skill providing fully automated orchestration flow: Plan (ralph+plannotator) → Execute (team/bmad) → UI Feedback (agentation/annotate) → Cleanup (worktree cleanup)
Control Layers
OMG uses one cross-platform abstraction for orchestration:
settings: platform/runtime configuration such as Claude hooks, Codexconfig.toml, Geminisettings.json, MCP registration, and prompt parametersrules: policy constraints that must hold on every platformhooks: event callbacks that enforce those rules on each platform
The key OMG rules are:
- do not reopen the PLAN gate when the current plan hash already has a terminal result
More from jeo-tech-ai/oh-my-gods
bmad
BMAD + TEA: Structured System Design (SSD) for AI-driven development. Embeds TEA (Task→Execute→Architect) micro-cycles inside each BMAD phase (Analysis→Planning→Solutioning→Implementation) for traceable, multi-agent execution with automated architect validation before human review.
2agent-workflow
Practical AI agent workflows and productivity techniques. Provides optimized patterns for daily development tasks such as commands, shortcuts, Git integration, MCP usage, and session management.
2agent-development-principles
Universal principles for agentic development when collaborating with AI agents. Defines divide-and-conquer, context management, abstraction level selection, and an automation philosophy. Applicable to all AI coding tools.
2agent-configuration
AI agent configuration policy and security guide. Project description file writing, Hooks/Skills/Plugins setup, security policy, team shared workflow definition.
2agent-evaluation
Design and implement comprehensive evaluation systems for AI agents. Use when building evals for coding agents, conversational agents, research agents, or computer-use agents. Covers grader types, benchmarks, 8-step roadmap, and production integration.
2state-management
Implement state management patterns for frontend applications. Use when managing global state, handling complex data flows, or coordinating state across components. Handles React Context, Redux, Zustand, Recoil, and state management best practices.
1