How this skill is triggered — by the user, by Claude, or both
Slash command
/oma:coordinateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use Task tool + TaskCreate for task tracking and agent spawning instead of CLI spawning.
Use Task tool + TaskCreate for task tracking and agent spawning instead of CLI spawning.
Response language follows language setting in .agents/config/user-preferences.yaml.
pm-planner subagent via Task tool.agents/plan.jsonCreate each agent task with TaskCreate for progress tracking:
1. Register each task with TaskCreate (subject, description)
2. Spawn agents by priority tier (parallel)
- Same tier agents: Multiple Task tool calls in same message
3. Update status with TaskUpdate on completion
Agent mapping: Reference .claude/agents/{agent}.md
Task tool returns results directly → No polling needed.
Spawn qa-reviewer subagent via Task tool (review results: OWASP Top 10, performance, accessibility, code quality)
LOOP:
[1] Spawn implementation agents via Task tool (parallel)
[2] Receive results
[3] Spawn QA agent via Task tool (review results)
[4] Parse QA results:
- 0 CRITICAL/HIGH issues → ACCEPT ✓
- CRITICAL/HIGH issues exist:
→ Compose issues as feedback for that agent:
## Issue Remediation
**Agent**: {agent-name}
**Issues**:
- [CRITICAL] file:line — description — fix instruction
- [HIGH] file:line — description — fix instruction
→ Re-spawn only that agent via Task tool (include issues + fix instructions)
→ Back to [3] (re-review with QA)
This loop replaces CLI's "Step 7: Address Issues and Iterate" with a synchronous Task tool-based loop.
$ARGUMENTS
npx claudepluginhub kyongsik-yoon/oh-my-agent --plugin omaCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
2plugins reuse this skill
First indexed Jul 17, 2026