oh-my-copilot

N coordinated agents on shared task list using Claude Code native teams

Configure HUD display options (layout, presets, display elements)

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

Durable multi-goal workflow that persists plan/ledger artifacts under .omcp/ultragoal and prints Claude /goal handoff text for the active session

Cancel any active OMC mode (autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team)

Diagnose and fix oh-my-copilot installation issues

Install or refresh oh-my-copilot for plugin, npm, and local-dev setups from the canonical setup flow

Strategic planning with optional interview workflow

Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

2-stage pipeline: trace (causal investigation) -> deep-interview (requirements crystallization) with 3-point injection

Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode

Configure notification integrations (Telegram, Discord, Slack) via natural language

Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions

Configure popular MCP servers for enhanced agent capabilities

Extract a learned skill from the current conversation

Turn a repeatable workflow from the current session into a reusable OMC skill draft

OMC agent catalog, available tools, team pipeline routing, commit protocol, and skills registry. Auto-loads when delegating to agents, using OMC tools, orchestrating teams, making commits, or invoking skills.

Manage local skills - list, add, remove, search, edit, setup wizard

Quadri-model orchestration — Copilot, Claude, Codex, and Gemini each provide independent analysis, then Copilot synthesizes

Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly

Full autonomous execution from idea to working code

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

Invoke parallel document-specialist agents for external web searches and documentation lookup

CLI-team runtime for claude, codex, or gemini workers in tmux panes when you need process-based parallel execution

Self-referential loop until task completion with configurable verification reviewer

Generic release assistant — analyzes repo release rules, caches them in .omcp/RELEASE_RULE.md, then guides the release

Orchestrate parallel scientist agents for comprehensive analysis with AUTO mode

Autonomous evolutionary code improvement engine with tournament selection

Use first for install/update routing — sends setup, doctor, or MCP requests to the correct OMC setup flow

QA cycling workflow - test, verify, fix, repeat until goal met

Parallel execution engine for high-throughput task completion

Agentic memory system for writers - track characters, relationships, scenes, and themes

Critique all unpushed commits before pushing to remote

Spawn parallel specialist agents to scan the codebase and produce a prioritized improvement backlog

Automated code review for Azure DevOps pull requests where you are assigned as reviewer. WHEN: User wants automated code reviews on PRs they're assigned to, wants AI-powered PR review comments, or wants to auto-review pending PRs in Azure DevOps. DO NOT USE FOR: Manual interactive PR review (use omc-ado-review), creating PRs (use git-master agent), sprint planning (use omc-ado-sprint), or non-ADO repositories.

Pull request review workflow for Azure DevOps repositories. WHEN: User wants to review PRs, add reviewers, create review comments, vote on PRs, or manage PR threads in Azure DevOps. DO NOT USE FOR: Creating PRs (use git-master agent), sprint planning (use omc-ado-sprint), work item triage (use omc-ado-triage), or non-ADO repositories.

Configure Azure DevOps integration for the current project. WHEN: User wants to set up ADO integration, connect a project to Azure DevOps, configure .omcp/config.json for ADO, or troubleshoot ADO connection issues. DO NOT USE FOR: Work item triage (use omc-ado-triage), sprint planning (use omc-ado-sprint), PR review (use omc-ado-review), or Azure cloud service configuration (use azure-skills plugin).

Sprint planning and iteration management for Azure DevOps projects. WHEN: User wants to plan sprints, manage iterations, check team capacity, groom backlogs, or assign work to sprints. DO NOT USE FOR: Work item triage (use omc-ado-triage), PR reviews (use omc-ado-review), pipeline management, or non-ADO projects.

Azure DevOps work item triage — surfaces untriaged items, active work, open PRs, pipeline failures, and security alerts. WHEN: User wants to check ADO board status, triage work items, see pipeline health, review open PRs, or get a project health overview. DO NOT USE FOR: Sprint planning (use omc-ado-sprint), PR code review (use omc-ado-review), initial ADO setup (use omc-ado-setup), or non-ADO projects.