commandsagent-doc-disciplineWriting-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 se
ai-slop-cleanerClean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
architecture-surveyPeriodic architecture survey — walks the module graph and reports ranked deepening candidates (shallow modules, hypothetical seams, logic behind the wrong seam). Survey, not rescue: it finds candidates and hands them to the captain; it never refactors on its own.
ask-navigatorShipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding,
askProcess-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly
autopilotFull autonomous execution from idea to working code
autoresearchStateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior
cancelCancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state
configure-notificationsConfigure notification integrations (Telegram, Discord, Slack) via natural language
debugDiagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
deep-interviewSocratic deep interview with mathematical ambiguity gating before explicit execution approval
deepinitDeep codebase initialization with hierarchical AGENTS.md documentation
diagramUse the smallest visual when prose must carry structure—control flow, call depth, module ownership, or change shape: pseudocode, call tree, component/file tree, Mermaid diagram, or diff. Skip it when prose already answers the question.
drydockLay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo;
executeCarry an approved task through to working, verified code
external-contextInvoke parallel document-specialist agents for external web searches and documentation lookup
graphDeterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery
harborHarbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, im
hudConfigure HUD display options (layout, presets, display elements)
intentShipyard's internal requirements intake for non-engineer contributors (support/ops) — turn a pasted chat log or verbal problem report into a five-section intent.md through numbered batch questioning with a completion gate, walk it through tracker review with harbor's four records, and hand the accep
launchShipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the
loftLoft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the arti
minimal-code-disciplineYAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away
minimal-prose-disciplineWriting-time discipline for the prose an agent speaks to a human (replies, reports, pointers): a protected core never rewritten (code, commands, paths, errors, negators, numbers), filler dies, no narration, auto-clarity where terse misleads
omc-doctorDiagnose and fix oh-my-claudecode installation issues
omc-setupInstall or refresh oh-my-claudecode for plugin, npm, and local-dev setups from the canonical setup flow
omc-planStrategic planning with optional interview workflow
project-session-managerWorktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
ralphSelf-referential loop until task completion with configurable verification reviewer
ralplanConsensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution
releaseGeneric release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release
rememberReview reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
researchInvestigate an open question and return grounded, sourced findings
omc-reviewEvaluate finished work for defects, risk, and simplification before it ships
self-improveAutonomous evolutionary code improvement engine with tournament selection
skillManage local skills - list, add, remove, search, edit, setup wizard
skillifyTurn a repeatable workflow from the current session into a reusable OMC skill draft
teamN coordinated agents on shared task list using Claude Code implicit agent teams
traceEvidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode
ultragoalDurable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session
verifyvisual-verdictwiki