Agent skill

oma-coordination

Guide for coordinating PM, Frontend, Backend, Mobile, and QA agents on complex projects via CLI. Use for manual step-by-step coordination and workflow guidance.

Stars 208
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/first-fluke/fullstack-starter/tree/main/.agents/skills/oma-coordination

SKILL.md

Multi-Agent Workflow Guide

When to use

  • Complex feature spanning multiple domains (full-stack, mobile)
  • Coordination needed between frontend, backend, mobile, and QA
  • User wants step-by-step guidance for multi-agent coordination

When NOT to use

  • Simple single-domain task -> use the specific agent directly
  • User wants automated execution -> use orchestrator
  • Quick bug fixes or minor changes

Core Rules

  1. Always start with PM Agent for task decomposition
  2. Spawn independent tasks in parallel (same priority tier)
  3. Define API contracts before frontend/mobile tasks
  4. QA review is always the final step
  5. Assign separate workspaces to avoid file conflicts
  6. Always use Serena MCP tools as the primary method for code exploration and modification
  7. Never skip steps in the workflow — follow each step sequentially without omission

Workflow

Step 1: Plan with PM Agent

PM Agent analyzes requirements, selects tech stack, creates task breakdown with priorities.

Step 2: Spawn Agents by Priority

Spawn agents via CLI:

  1. Use spawn-agent.sh for each task
  2. CLI selection follows agent_cli_mapping in oma-config.yaml
  3. Spawn all same-priority tasks in parallel using background processes
bash
# Example: spawn backend and frontend in parallel
oma agent:spawn backend "task description" session-id -w ./backend &
oma agent:spawn frontend "task description" session-id -w ./frontend &
wait

Step 3: Monitor & Coordinate

  • Use memory read tool to poll progress-{agent}.md files
  • Verify API contracts align between agents
  • Ensure shared data models are consistent

Step 4: QA Review

Spawn QA Agent last to review all deliverables. Address CRITICAL issues by re-spawning agents.

Automated Alternative

For fully automated execution without manual spawning, use the orchestrator skill instead.

References

  • Workflow examples: resources/examples.md

Expand your agent's capabilities with these related and highly-rated skills.

first-fluke/fullstack-starter

oma-mobile

Mobile specialist for Flutter, React Native, and cross-platform mobile development. Use for mobile app, Flutter, Dart, iOS, Android, Riverpod, and widget work.

208 31
Explore
first-fluke/fullstack-starter

oma-frontend

Frontend specialist for React, Next.js, TypeScript with FSD-lite architecture, shadcn/ui, and design system alignment. Use for UI, component, page, layout, CSS, Tailwind, and shadcn work.

208 31
Explore
first-fluke/fullstack-starter

oma-backend

Backend specialist for APIs, databases, authentication with clean architecture (Repository/Service/Router pattern). Use for API, endpoint, REST, database, server, migration, and auth work.

208 31
Explore
first-fluke/fullstack-starter

oma-pdf

Convert PDF files to Markdown using opendataloader-pdf. Extracts text, tables, headings, lists, and images with correct reading order. Use for PDF parsing, PDF to Markdown conversion, document extraction, and AI-ready data preparation.

208 31
Explore
first-fluke/fullstack-starter

oma-brainstorm

Design-first ideation that explores user intent, constraints, and approaches before any planning or implementation. Use for brainstorming, ideation, exploring concepts, and evaluating approaches.

208 31
Explore
first-fluke/fullstack-starter

oma-translator

Context-aware translation that preserves tone, style, and natural word order. Use when translating UI strings, documentation, marketing copy, or any multilingual content. Infers register, domain, and style from the source text and surrounding codebase context.

208 31
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results