- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add first-fluke/oh-my-agent --skill oma-orchestration -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add first-fluke/oh-my-agent --skill oma-orchestration -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add first-fluke/oh-my-agent --skill oma-orchestration -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add first-fluke/oh-my-agent --skill oma-orchestration -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/first-fluke/oh-my-agent/tree/HEAD/.agents/skills/oma-orchestrationDo publicador
Automatically orchestrate multi-agent execution with task decomposition, native/fallback dispatch, memory coordination, progress monitoring, verification, QA cross-review, retry, and result collection.
.agents/oma-config.yaml, the runtime's native agent definitions (for example .claude/agents/*.md, .codex/agents/*.toml), or fallback oma agent spawnmemoryConfig, and the QA agent for cross-revieworchestration.route-selection per ../_shared/runtime/route-selection.md (native or oma agent spawn, and the vendor match or unavailability that decided it).partial or failed; never force completion.Phase names refer to Workflow Phases below.
oma agent spawn.
oma agent spawn <agent-type> <prompt-file> <session-id> --task-id <task.id> -w <workspace>
Spawn options: --vendor <vendor> (CLI vendor override), --model-id <id> (model for this spawn), --isolation worktree (git worktree per spawn), --read-only (non-destructive tools only, for review and QA passes), --edit-only (file edits approved, nothing else).oma verify agent <agent-type> --workspace <workspace> --json
Reads project configuration and writes the session, task-board, progress, and result files through the configured memory provider (under the basePath in memoryConfig), including session state and unresolved decisions. Starts agent processes (native subagents or oma agent spawn) and verify scripts. Spawned agents change code in the workspaces they own. A failed verify or review starts further agent runs, each consuming the recovery budget.
target_vendor === current_runtime_vendor and the runtime has a verified native path, use native dispatch.oma agent spawn.When the user names who should do a task, dispatch it with oma agent spawn; do not write a launcher by hand. The delegate knows only the brief, so put the goal, the files, the constraints, and the check that proves the work into a prompt file.
oma agent spawn <agent-type> <prompt-file> <session-id> --vendor <vendor> --model-id <model> --edit-only
--read-only for inspection and review. --edit-only for edits: file edits are approved and nothing else, so the delegate runs no commands and the parent runs the checks. Omit both only when the task needs commands and the user accepted the vendor's auto-approve mode. A vendor without an edit-only mode refuses the flag; report that and ask before widening.--model-id takes the name the vendor CLI uses (grok models, agy models, cursor-agent models). It replaces the configured plan for that spawn.oma agent batch <agent-type> <prompt-template> --items <file> --check "<command with {item}>" --vendor <vendor> --fallback-vendors <v1,v2> --edit-only
Items whose check already passes are skipped, the parent re-runs the check after each session, and a rerun resumes from what still fails. After two vendor failures in a row the batch moves to the next fallback vendor, or stops when none is left.Current native executor paths:
.claude/agents/{agent}.md definitions (multiple Agent tool calls in one message run in parallel; results return synchronously — no polling)task tool with subagent_type: {agent-id}; do not use oma agent spawn for same-session OpenCode or Kilo work because it will not appear as a native child task.codex/agents/*.toml when supported; otherwise use oma agent spawn. Model tiering follows ../_shared/core/vendor-detection.md.oma agent spawn unless a native role-subagent path is verified for the target vendor (../_shared/core/vendor-detection.md).codex exec and agy -p start external CLI sessions. An @agent string in a prompt does not establish native dispatch or apply a custom-role contract.
These are workflow defaults. Resolve model/vendor, parallelism, and budget settings from project configuration. config/cli-config.yaml supplies the vendor transport registry; it does not select the active vendor or override runtime execution settings.
Memory provider and tool names are configurable via .agents/mcp.json (not the repo-root .mcp.json, which is the Claude Code MCP server config):
{
"memoryConfig": {
"provider": "file",
"basePath": ".agents/state/memories",
"tools": {
"read": "Read",
"write": "Write",
"edit": "Edit"
}
}
}
PHASE 1 - Plan: Reuse the current valid plan or decompose the request; preserve injected session/task/run IDs.
PHASE 1.5 - References: For each task, classify into one or more domain_tags by matching against the Intent signature block of each installed .agents/skills/oma-*/SKILL.md. Tasks that match no domain confidently inherit the union of their parent feature's tags. Select the references needed by each task. One confidently matched skill is sufficient; expand the set when classification is uncertain or a dependency requires another domain. Record selected domains, references, and any fallback reason in the task board; record uncertainty and expansion reasons without assuming runtime enforcement. These are coordinator notes, not launcher-enforced exposure fields; use only reference/context controls supported by the active dispatch path.
PHASE 2 - Setup: Create session/task-board artifacts with the current IDs and selected references.
PHASE 3 - Execute: Dispatch ready tasks within MAX_PARALLEL using supported native or fallback context controls.
PHASE 4 - Monitor: Prefer completion notifications; otherwise use one coordinator with bounded polling backoff. Follow ../_shared/core/execution-policy.md for the shared deadline, cancellation, resource ownership, and shutdown rules. Cancellation or deadline exhaustion stops dispatch and recovery before verification.
PHASE 4.5 - Verify: Run mechanical checks for every completed agent; run oma verify agent {agent-type} only for backend, frontend, mobile, qa, debug, and pm; then run QA cross-review for every completed implementation
PHASE 5 - Collect: Read claims and run-scoped reports for plan tasks whose checks passed; compile summary without deleting evidence.
After each agent completes, enter an iterative review loop, not a single-pass verification.
Agent completes work
↓
[1] Mechanical Self-Check: lint, type-check, tests, diff scope
↓
[2] Verify: For supported types, run `oma verify agent {agent-type} --workspace {workspace}`
Unsupported (`db`, `refactor`, `architecture`, `tf-infra`, `docs`) → record SKIP and continue
↓ FAIL → Agent receives feedback, fixes, back to [1]
↓ PASS
[3] Cross-Review: QA agent reviews the changes
↓ FAIL → Agent receives review feedback, fixes, back to [1]
↓ PASS
Accept result
[1] Mechanical Self-Check: Before requesting external review, the implementation agent must:
Quality judgment is NOT performed in this step. Design quality, architecture alignment, and acceptance criteria satisfaction are evaluated exclusively in [3] Cross-Review by the QA agent. Reason: Self-evaluation bias causes agents to consistently overrate their own output (ref: Anthropic harness design research).
[2] Automated Verify:
oma verify agent {agent-type} --workspace {workspace} --json
backend, frontend, mobile, qa, debug, and pm.db, refactor, architecture, tf-infra, and docs, record that automated verify is unsupported and continue to QA cross-review after the mechanical checks.[3] Cross-Review: Spawn QA agent to review the changes:
QA agent reads the diff, runs checks, evaluates against acceptance criteria
If docs/CODE-REVIEW.md exists, QA agent uses it as the review checklist
QA agent outputs: PASS (with optional nits) or FAIL (with specific issues)
On FAIL: issues are fed back to the implementation agent for fixing
When feeding review results back to the implementation agent:
## Review Feedback (iteration {n}/{max})
**Reviewer**: {self / verify / qa-agent}
**Verdict**: FAIL
**Issues**:
1. {specific issue with file and line reference}
2. {specific issue}
**Fix instruction**: {what to change}
This replaces single-pass verification. Most "nitpicking" should happen agent-to-agent. Resolve relevant automated checks before handoff. Ask for approval only when the next action is outside existing authorization.
Maintain one budget per workflow lineage and logical goal: attempts_used, attempts_remaining, and any
configured cost cap. The original attempt, each ordinary retry, and each
exploration hypothesis consume one attempt. Before starting recovery, reserve
the complete next action; do not exceed the budget or start an incomplete
exploration round.
Use the plan's stable lineage_id and task goal_id from ../_shared/runtime/result-contract.md. New task/run/session IDs do not reset that budget. Freeze the full JSON plan at first dispatch; reject recursive planning/review tasks and post-dispatch plan revisions. A contract change requires an explicitly separated new session and lineage.
Classify failures before retrying: PRODUCT_FAILURE follows the remaining product recovery budget; WORKFLOW_EVIDENCE_FAILURE means current product checks passed but completion claims or bindings failed. Automatic resume stops evidence-only replay. Allow at most one metadata-only repair under the existing task and frozen plan, consuming the same budget, then stop with a partial handoff if unresolved. Do not create PM tasks, rerun product planning, or import another workflow's plan-review loop for evidence failures.
partial or failed, never completed.For material corrections or review findings, retain the cause, impact, and evidence in existing task artifacts. Use ../_shared/core/session-metrics.md when a retrospective or separate session summary is useful. Do not score clarification questions or require an RCA based on counters. Resolve the affected work and ask only for a material missing decision.
../_shared/core/collaboration-policy.md (before assigning parallel work or coordinating peer issues, ownership handoffs, and result collection)resources/subagent-prompt-template.mdresources/memory-schema.mdscripts/spawn-agent.sh, scripts/parallel-run.sh, scripts/verify.sh../_shared/core/skill-routing.mdscripts/verify.sh <agent-type>../_shared/core/session-metrics.md (requested retrospective or separate session summary)../_shared/core/api-contracts/template.md; read generated contracts from .agents/results/api-contracts/ (run artifact) or docs/plans/contracts/ (durable spec)../_shared/core/context-loading.md../_shared/core/difficulty-guide.md (unresolved scope or dependencies)../_shared/core/clarification-protocol.md../_shared/core/context-budget.md../_shared/core/code-intelligence.md../_shared/core/lessons-learned.md (recurring failure or requested retrospective)Dispatch and supervise parallel specialist agents with durable task state. Use for automated multi-agent execution, to coordinate agents step by step, or to hand a task to a named vendor or model.
---name: oma-orchestrationdescription: Dispatch and supervise parallel specialist agents with durable task state. Use for automated multi-agent…---# .agents/skills/oma-orchestration/SKILL.mdPerguntas frequentes
Baixe .agents/skills/oma-orchestration/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/first-fluke/oh-my-agent.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.