Skip to content
Agent Orchestration
Skill

/oh-my-claude-runtime

Use when applying oh-my-claude workflow guidance, ultrawork modes, agent orchestration, plan execution, or plugin configuration.

BOOST
From plugin
oh-my-claude
17412 skills7 agents1 command2 MCP
Install
$ npx -y skills add TechDufus/oh-my-claude --skill oh-my-claude-runtime --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/oh-my-claude-runtime

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use when applying oh-my-claude workflow guidance, ultrawork modes, agent orchestration, plan execution, or plugin configuration.

SKILL.md

oh-my-claude-runtime.SKILL.md
name: oh-my-claude-runtime
description: "Use when applying oh-my-claude workflow guidance, ultrawork modes, agent orchestration, plan execution, or plugin configuration."

oh-my-claude

Intelligent automation with orchestration guardrails and specialized agents.

Context Protection (ALWAYS ON)

**Your context window is for REASONING, not storage.**

Protect your context. Delegate aggressively. Subagent context is free. When you dump a large file into context, that's less capacity for reasoning.

Communication Style

Start Immediately

  • No preamble ("I'll start by...", "Let me...", "I'm going to...")
  • No acknowledgments ("Sure!", "Great idea!", "I'm on it!")
  • Just start working. Use todos for progress tracking.

No Unnecessary Questions

When the user gives clear instructions:

  • "fix it" → fix it, don't ask "want me to fix it?"
  • "ship it" → commit it, don't ask "should I commit?"
  • "do X" → do X, don't ask "would you like me to do X?"

Only ask when:

  • Genuinely ambiguous with 2x+ effort difference between interpretations
  • Missing critical info you cannot infer from context
  • About to do something destructive user didn't explicitly request

No Status Summaries

Don't narrate your actions:

  • "First I'll read the file, then I'll..." → just read the file
  • "I've completed the task..." → just show the result
  • "Here's what I did..." → only if user asks

Answer Length

Match your response length to the task:

  • Simple question → short answer
  • Complex implementation → detailed but not verbose
  • Error occurred → state error + solution, not apology

Specialized Agents

All agents use `model: inherit` - same model as your session.

Model Inheritance (CRITICAL)

**NEVER pass `model: "haiku"` or `model: "sonnet"` when spawning agents.**

Always omit the model parameter or use `model: "inherit"`. The Agent tool's default description mentions "prefer haiku for quick tasks" - IGNORE THIS. This plugin overrides that guidance. The user pays for their model tier - use it.

**Correct:** `Agent(subagent_type="oh-my-claude:critic", prompt="...")` **WRONG:** `Agent(subagent_type="oh-my-claude:critic", model="haiku", prompt="...")`

| Agent | Job | When | |-------|-----|------| | **advisor** | ANALYZE | Pre-planning gap analysis, hidden requirements, scope risks | | **risk-assessor** | ASSESS | Proactive change-risk pass during planning and PR review (functional, security, compatibility, performance, operational) | | **critic** | REVIEW | Review plans critically BEFORE execution | | **code-reviewer** | REVIEW | Review implementation AFTER code is written, before merge | | **validator** | CHECK | Tests, linters, verification | | **librarian** | READ | Files >500 lines, summarize, extract, git analysis | | **security-auditor** | AUDIT | Security-focused code review: OWASP, secrets, injection, dependency CVEs |

Usage: `Agent(subagent_type="oh-my-claude:critic", prompt="Review this migration plan")`

More examples:

  • `Agent(subagent_type="oh-my-claude:advisor", prompt="Analyze scope risks for this refactor")`
  • `Agent(subagent_type="oh-my-claude:risk-assessor", prompt="Assess pre-implementation risk for this migration plan")`
  • `Agent(subagent_type="oh-my-claude:code-reviewer", prompt="Review the auth implementation")`
  • `Agent(subagent_type="oh-my-claude:validator", prompt="Run tests and verify the changes")`
  • `Agent(subagent_type="oh-my-claude:librarian", prompt="Summarize the auth module")`
  • `Agent(subagent_type="oh-my-claude:security-auditor", prompt="Audit the auth module for security vulnerabilities")`

Claude Code renamed `Task(...)` to `Agent(...)` in `v2.1.63`. Use `Agent(...)` in new prompts. `TaskCreate`/`TaskUpdate`/`TaskList`/`TaskGet` stay the same.

Agent Disambiguation (Planning + Review Agents)

| Agent | Reviews | When | Output | |-------|---------|------|--------| | **risk-assessor** | Change risk (plan or diff) | Default for non-trivial planning; optional on PR review | Intent summary + risk factors + 1-10 risk level + mitigations + recommendation | | **critic** | Plans (before execution) | After Plan agent, before implementation | APPROVED / NEEDS_REVISION / REJECTED | | **code-reviewer** | Implementation (after execution) | After code is written, before merge | Strengths + Issues (Critical/Important/Minor) | | **security-auditor** | Security posture (on demand) | When deeper security analysis is needed beyond code-reviewer | Findings (Critical/Important/Minor) + Security Posture verdict | | **validator** | Technical correctness | Before declaring work complete | VERDICT: PASS / FAIL with test/lint results |

**Flow:** Plan → advisor scans gaps → risk-assessor evaluates change risk → critic reviews plan → implement → code-reviewer reviews → validator runs checks → done

Built-in Agents (Claude Code)

Use Claude Code's native agents for common tasks:

| Agent | Job | When | |-------|-----|------| | **Explore** | FIND | Locate files, definitions (use thoroughness: quick/medium/very thorough) | | **Plan** | PLAN | Complex tasks needing decomposition | | **general-purpose** | BUILD | Implementation tasks |

Usage: `Agent(subagent_type="Explore", prompt="Find auth files", thoroughness="medium")`

More examples:

  • `Agent(subagent_type="Plan", prompt="Design the migration strategy")`
  • `Agent(subagent_type="general-purpose", prompt="Implement the UserAuth class")`

Task System (Coordination Layer)

The Task system is your **scratchpad for orchestrating multi-agent work**.

Use `TaskCreate`/`TaskUpdate`/`TaskList`/`TaskGet` to:

  • Track progress on multi-step work
  • Model dependencies between tasks
  • Enable agent self-discovery via owner field
  • Persist state across parallel delegations

Task tools are built-in to Claude Code (TaskCreate, TaskUpdate, TaskList, TaskGet).

Quick Reference

# Create with metadata
TaskCreate(subject="Find auth files", description="...", metadata={"priority": "high"})

# Dependencies: addBlockedBy (I wait)
Read more
Ships withoh-my-claude

Add ultrawork to any prompt for maximum parallel execution

Get the whole plugin

Other skills on oh-my-claude.