Skip to content

oliverv/caro / .agents/skills/oma-orchestration

oma-orchestration

Unverified

Dispatch and supervise parallel specialist agents with durable task state. Use when automated multi-agent execution is requested.

FileKindSize
SKILL.mdskill md15.6 KB
config/cli-config.yamlconfig3.4 KB
resources/memory-schema.mdmarkdown6.7 KB
resources/subagent-prompt-template.mdmarkdown1.5 KB
scripts/parallel-run.shexecutablescript231 B
scripts/spawn-agent.shexecutablescript178 B
scripts/verify.shexecutablescript542 B
templates/backend-task.mdmarkdown634 B
templates/debug-task.mdmarkdown339 B
templates/frontend-task.mdmarkdown582 B
templates/mobile-task.mdmarkdown588 B
templates/qa-task.mdmarkdown441 B
templates/tasks-example.yamlconfig418 B

resources/memory-schema.md

View on GitHub
# MCP Memory Schema for Multi-Agent Orchestration

## Overview

Each subagent writes only to its own dedicated files. The orchestrator manages session-level files. This ownership model prevents write conflicts between concurrent agents.

## Configuration

Memory base path and tool names are configurable via `.agents/mcp.json` (not the repo-root `.mcp.json`, which is the Claude Code MCP server config):
```json
{
  "memoryConfig": {
    "basePath": ".agents/state/memories",
    "tools": {
      "read": "Read",
      "write": "Write",
      "edit": "Edit"
    }
  }
}
```

Default base path: `.agents/state/memories`

## File Structure

```
{memoryConfig.basePath}/
  orchestrator-session-{sessionId}.md                 # Session metadata
  task-board-{sessionId}.md                            # Master task list
  progress-{agentId}-{taskId}-{runId}-{sessionId}.md   # Per-run progress log
  result-{agentId}-{taskId}-{runId}-{sessionId}.md     # Per-run final report
```

> **Path rule**: Resolve paths from the project-root memory base, then isolate
> every artifact by session, task, and run. In monorepos, never choose a
> subproject memory root. The injected claim path and agent-run receipt keep
> their structured contract and are not replaced by this report layout.

## orchestrator-session.md

Created by the orchestrator at session start. Updated throughout execution.

```markdown
# Orchestrator Session
## ID: session-{YYYYMMDD}-{HHMMSS}
## Started: {ISO timestamp}
## Status: running | completed | failed | aborted

## Agents
| Agent ID | CLI | PID | Status | Task |
|----------|-----|-----|--------|------|
| backend  | gemini | 12345 | running | task-1 |
| frontend | gemini | 12346 | completed | task-2 |
| mobile   | claude | 12347 | running | task-3 |

## Configuration
- MAX_PARALLEL: 3
- MAX_RETRIES: 2
- POLL_INTERVAL: 30s

## Summary (filled on completion)
- Total Tasks: X
- Completed: X
- Failed: X
- Files Created: [list]
- Issues: [list]
```

## task-board.md

Master task list created by the orchestrator. Subagents read this to understand their assignment but never write to it.

`Exposed Skills` is the task's `exposed_skill_set` from the domain gate (PHASE 1.5 in `SKILL.md`): the specialist skills injected into the subagent's prompt. `Exposure Fallback` is `true` when classification confidence was too low and the full installed skill library was exposed instead.

```markdown
# Task Board
## Session: session-{YYYYMMDD}-{HHMMSS}

### task-1
- **Agent**: backend
- **CLI**: gemini
- **Title**: JWT authentication API
- **Status**: pending | in_progress | completed | failed | blocked
- **Priority**: 1
- **Dependencies**: none
- **Exposed Skills**: oma-backend, oma-db
- **Exposure Fallback**: false
- **Description**: Implement user registration and login with JWT tokens
- **Acceptance Criteria**:
  - POST /api/auth/register with email + password
  - POST /api/auth/login returns access + refresh tokens
  - Password hashing with bcrypt
  - Rate limiting on auth endpoints

### task-2
- **Agent**: frontend
- **CLI**: gemini
- **Title**: Login and registration UI
- **Status**: pending
- **Priority**: 1
- **Dependencies**: none
- **Exposed Skills**: oma-frontend, oma-design
- **Exposure Fallback**: false
- **Description**: Build login and registration forms with validation
- **Acceptance Criteria**:
  - Login form with email + password
  - Registration form with validation
  - Error handling for failed auth
  - JWT token storage and auto-refresh

### task-3
- **Agent**: qa
- **CLI**: gemini
- **Title**: Security and performance review
- **Status**: blocked
- **Priority**: 2
- **Dependencies**: task-1, task-2
- **Exposed Skills**: (all installed skills)
- **Exposure Fallback**: true
- **Description**: Review all deliverables for security and performance
- **Acceptance Criteria**:
  - OWASP Top 10 security check
  - Performance benchmarks pass
  - No critical or high severity issues
```

## progress-{agentId}-{taskId}-{runId}-{sessionId}.md

Each agent creates this file at start and appends entries every 3-5 turns. Only the owning agent writes to this file.

```markdown
# Progress: backend
## Task: task-1
## Agent ID: backend
## Started: {ISO timestamp}

### Turn 1 - {ISO timestamp}
- **Action**: Reading task-board.md and understanding requirements
- **Status**: in_progress
- **Details**: Identified 4 acceptance criteria for JWT auth API

### Turn 5 - {ISO timestamp}
- **Action**: Created user model and auth endpoints
- **Status**: in_progress
- **Details**: Implemented POST /api/auth/register and /api/auth/login
- **Files**: app/models/user.py, app/api/auth.py

### Turn 12 - {ISO timestamp}
- **Action**: Added tests and rate limiting
- **Status**: in_progress
- **Details**: 15 test cases passing, rate limiter configured

### Turn 18 - {ISO timestamp}
- **Action**: All acceptance criteria met
- **Status**: completed
- **Summary**: JWT auth API fully implemented with tests
```

## result-{agentId}-{taskId}-{runId}-{sessionId}.md

Each agent creates this file upon completion (success or failure). Only the owning agent writes to this file.

```markdown
# Result: backend
## Task: task-1
## Status: completed
## Turns Used: 18

## Summary
Implemented JWT authentication API with user registration, login,
password hashing (bcrypt), and rate limiting.

## Files Created/Modified
- `app/models/user.py` (NEW) - User model with password hashing
- `app/api/auth.py` (NEW) - Auth endpoints
- `app/middleware/rate_limit.py` (NEW) - Rate limiting middleware
- `tests/test_auth.py` (NEW) - 15 test cases
- `alembic/versions/001_create_users.py` (NEW) - Migration

## Acceptance Criteria
- [x] POST /api/auth/register with email + password
- [x] POST /api/auth/login returns access + refresh tokens
- [x] Password hashing with bcrypt
- [x] Rate limiting on auth endpoints

## Issues Encountered
- None

## Notes
- Access token expiry: 15 minutes
- Refresh token expiry: 7 days
- Rate limit: 5 requests/minute on login endpoint
```

### Failed Result Example

```markdown
# Result: backend
## Task: task-1
## Status: failed
## Turns Used: 20

## Summary
Unable to complete JWT auth API. Database connection issues prevented testing.

## Files Created/Modified
- `app/models/user.py` (NEW) - User model (untested)
- `app/api/auth.py` (NEW) - Auth endpoints (untested)

## Acceptance Criteria
- [x] POST /api/auth/register with email + password
- [x] POST /api/auth/login returns access + refresh tokens
- [x] Password hashing with bcrypt
- [ ] Rate limiting on auth endpoints (NOT DONE)

## Issues Encountered
- PostgreSQL connection refused on localhost:5432
- Could not run integration tests
- Rate limiting implementation incomplete due to turn limit

## Notes
- Needs database running to complete testing
- Rate limiting code is written but untested
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall