Remove low-information AI mannerisms and noisy boilerplate while preserving the intended technical result.
Teams-first multi-agent orchestration layer for Claude Code with guided setup, staged autopilot, native teams, provider advisers, planning, QA, memory, diagnostics, and many focused skills.
A Claude Code plugin and npm runtime with 41 indexed skills, hooks, state management, team workflows, provider-adviser commands, tmux worker support, documentation, and configuration schemas.
Turn a broad development goal into a planned, delegated, verified Claude Code workflow or ask external coding providers for bounded specialist input.
Choose it when Claude Code is the primary host and the project needs explicit multi-agent orchestration, persistent modes, diagnostics, and recoverable workflow state.
Remove low-information AI mannerisms and noisy boilerplate while preserving the intended technical result.
Send a bounded question to a configured external provider and bring the response back into the active workflow.
Run a staged plan-build-verify workflow from a high-level goal with checkpoints and recoverable state.
Execute an iterative, evidence-recorded research loop for measurable technical experiments.
Stop an active OMC mode or workflow and clean up its tracked state safely.
Ask multiple coding providers for complementary analysis and have Claude synthesize their findings.
Configure desktop or external notifications for long-running OMC activity.
Drive a reproduction-first debugging workflow that traces symptoms to root cause and verifies the fix.
Perform a deliberate, high-context investigation of a codebase, architecture, or difficult technical question.
Clarify an ambiguous project through structured questions before planning or implementation begins.
Create a deeper project initialization and context map for subsequent agent work.
Gather explicitly requested outside context and package it for the active Claude Code session.
Display compact workflow, context, and agent-status information during a session.
Capture reusable lessons from completed work and convert them into future guidance.
Keep source-build users aware when generated or compiled artifacts must be refreshed.
Configure supported MCP integrations and verify that Claude Code can reach them.
Assess tests, review findings, conflicts, and delivery evidence before a branch or pull request is merged.
Diagnose installation, configuration, runtime, hook, and dependency problems in OMC.
Open the consolidated OMC command, mode, configuration, and compatibility reference.
Install and configure OMC's project and user-level files through a guided setup flow.
Compatibility entry point that directs work to the current team orchestration surface.
Turn a request into an ordered implementation plan with explicit scope and verification steps.
Create and manage project sessions, worktrees, templates, and provider-specific execution contexts.
Persist on an implementation goal through bounded retries and verification until its completion condition is met.
Iterate on a plan with critique and refinement before expensive execution begins.
Coordinate versioning, validation, changelog, packaging, and release-readiness work.
Save an explicit fact or decision to OMC's durable project memory.
Apply a scientific hypothesis-experiment-measurement loop to technical investigation.
Evaluate agent behavior against goals and propose measured configuration or workflow improvements.
Provide the short in-session entry point to OMC installation and configuration.
Inspect, select, and use an installed OMC skill deliberately.
Convert a repeatable workflow or source document into a structured reusable skill.
Coordinate Claude Code's native multi-agent team through planning, execution, verification, and repair stages.
Trace agent decisions, hooks, state transitions, or execution paths for diagnosis.
Manage a large goal with durable state, decomposition, progress checks, and completion criteria.
Run a deeper quality-assurance pass across behavior, tests, edge cases, and deliverables.
Use higher-effort parallel execution for a broad, well-scoped implementation workload.
Check claims and deliverables against concrete tests, commands, artifacts, or acceptance criteria.
Evaluate visual output against explicit design and usability criteria.
Build and query durable project documentation from repository evidence.
Maintain writing-specific preferences, facts, terminology, and continuity across sessions.
Core plugin and CLI flows can run on Apple silicon. The README currently documents Linux-only support for named autopilot stage profiles that rely on flock; use legacy/default autopilot on Tahoe unless upstream expands support.
Teams-first multi-agent orchestration layer for Claude Code with guided setup, staged autopilot, native teams, provider advisers, planning, QA, memory, diagnostics, and many focused skills.
Combines a large skill set with a stateful teams-first orchestration runtime and several clearly separated provider-adviser surfaces.
The plugin installs hooks, instructions, state files, and can launch multiple agents or provider CLIs. Audit configuration, cap concurrency, review permissions, and avoid mixing overlapping orchestration owners.
Project context can reach Claude and any external provider explicitly invoked through ask/team flows. Treat tmux panes, transcripts, memory, notifications, and logs as sensitive project data.
None documented.
Routing guidance is an analyst synthesis based on the first-party repository and README.
Choose one primary lifecycle owner. Individual non-overlapping skills can be added selectively, but do not enable two automatic planning/delegation/verification systems without an explicit precedence policy.
Teams-first multi-agent orchestration layer for Claude Code with guided setup, staged autopilot, native teams, provider advisers, planning, QA, memory, diagnostics, and many focused skills.
Claude Code is the primary runtime and team orchestration is desired
Choose the closest narrowly scoped existing repository only after comparing permissions and workflow ownership.