amoa-task-distribution

Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

7 stars

Best use case

amoa-task-distribution is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Teams using amoa-task-distribution should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/amoa-task-distribution/SKILL.md --create-dirs "https://raw.githubusercontent.com/Emasoft/ai-maestro-orchestrator-agent/main/skills/amoa-task-distribution/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/amoa-task-distribution/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How amoa-task-distribution Compares

Feature / Agentamoa-task-distributionStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Task Distribution Skill

## Overview

Distributes tasks to agents by priority, dependencies, and agent state.

## Prerequisites

Requires `gh` CLI, AI Maestro API, and familiarity with **amoa-label-taxonomy** and **amoa-messaging-templates**.

## Instructions

1. Query `status:ready` tasks, sort by priority (critical > high > normal > low), skip tasks with unresolved blockedBy deps
2. Select agent by availability, skill match, and load — see [op-select-agent.md](references/op-select-agent.md)
<!-- TOC: Purpose | Selection Criteria | Procedure | Specialization Preferences | Error Handling -->
3. Assign: add `assign:<agent>` + `status:in-progress` labels, send message via `agent-messaging` — see [op-assign-task.md](references/op-assign-task.md)
<!-- TOC: Purpose | Procedure | Commands | Message Format | Post-Assignment | Error Handling -->
4. Wait for ACK; if timeout, reassign per [op-reassign-task.md](references/op-reassign-task.md)
<!-- TOC: When to Reassign | Procedure | Commands | Partial Progress Gathering | Error Handling -->

Dependency types: Hard (block), Soft (assign with note), None (parallel). Circular deps → escalate. See [dependency-management.md](references/dependency-management.md)
<!-- TOC: Dependency Types | Dependency Resolution | Circular Dependency Detection -->

Load balancing: prefer lowest-load agent. See [load-balancing.md](references/load-balancing.md)
<!-- TOC: Even Distribution | Specialization -->

Blocked tasks: acknowledge, record, move to Blocked column, escalate. See [blocked-task-handling.md](references/blocked-task-handling.md)
<!-- TOC: Blocker Response Steps | Blocker Escalation Message Example | Verification Before Escalation | Checklist: Move Task to Blocked Column | Checklist: Restore Task from Blocked -->

Copy this checklist and track your progress:

- [ ] Query and sort ready tasks; assign best-match agent
- [ ] Update labels and send AI Maestro message; wait for ACK
- [ ] If no ACK or blocked, reassign per [op-reassign-task.md](references/op-reassign-task.md)
  <!-- TOC: Reassign | Procedure | Commands | Partial Progress | Errors -->

Full checklist: [distribution-workflow-checklist.md](references/distribution-workflow-checklist.md)
<!-- TOC: Step-by-Step Instructions | Distribution Checklist -->

## Output

Assignment confirmation (label + ACK) and delegation log.

## Examples

**Input:** 3 ready tasks, 2 agents — **Output:** Critical task assigned, labels updated, ACK received. See [examples.md](references/examples.md)
<!-- TOC: Query and Sort Ready Tasks | Check Agent Availability | Assign Task with Full Protocol | Handle Circular Dependency | Query the agent registry for `implementer-1` to get their current task count | Check the agent's last seen timestamp to determine if they are responsive -->


## Error Handling

See [error-handling.md](references/error-handling.md)
<!-- TOC: Error Table -->

## Resources

- [references/](references/) — procedures, examples, error handling, checklist

Related Skills

amoa-verification-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-two-phase-mode

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-remote-agent-coordinator

7
from Emasoft/ai-maestro-orchestrator-agent

Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-progress-monitoring

7
from Emasoft/ai-maestro-orchestrator-agent

Use when monitoring agent progress. Trigger with status check or stall detection requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-plan-phase

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan Phase of two-phase mode. Trigger with planning, requirements, or plan approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-loop

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running the orchestrator loop or managing stop hook behavior. Trigger with loop, stop hook, or state file requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-sync

7
from Emasoft/ai-maestro-orchestrator-agent

Use when syncing modules with GitHub Issues or troubleshooting module state. Trigger with sync, issue, or module troubleshooting requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-management

7
from Emasoft/ai-maestro-orchestrator-agent

Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-lifecycle

7
from Emasoft/ai-maestro-orchestrator-agent

Use when adding, modifying, removing, prioritizing, or reassigning modules. Trigger with module CRUD requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-messaging-templates

7
from Emasoft/ai-maestro-orchestrator-agent

Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-label-taxonomy

7
from Emasoft/ai-maestro-orchestrator-agent

Use when applying GitHub labels. Trigger with label query or assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent