Index of every page on this site: llms.txt
All skills
wshobson avatar

/task-coordination-strategies

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.

Use this Skill: https://skilld.dev/gh/wshobson/agents/task-coordination-strategies

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈70 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈1.4k more on demand in 2 files.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈280 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Task Coordination Strategies

Strategies for decomposing complex tasks into parallelizable units, designing dependency graphs, writing effective task descriptions, and monitoring workload across agent teams.

When to Use This Skill

  • Breaking down a complex task for parallel execution
  • Designing task dependency relationships (blockedBy/blocks)
  • Writing task descriptions with clear acceptance criteria
  • Monitoring and rebalancing workload across teammates
  • Identifying the critical path in a multi-task workflow

Task Decomposition Strategies

By Layer

Split work by architectural layer:

  • Frontend components
  • Backend API endpoints
  • Database migrations/models
  • Test suites

Best for: Full-stack features, vertical slices

By Component

Split work by functional component:

  • Authentication module
  • User profile module
  • Notification module

Best for: Microservices, modular architectures

By Concern

Split work by cross-cutting concern:

  • Security review
  • Performance review
  • Architecture review

Best for: Code reviews, audits

By File Ownership

Split work by file/directory boundaries:

  • src/components/ — Implementer 1
  • src/api/ — Implementer 2
  • src/utils/ — Implementer 3

Best for: Parallel implementation, conflict avoidance

Dependency Graph Design

Principles

  1. Minimize chain depth — Prefer wide, shallow graphs over deep chains
  2. Identify the critical path — The longest chain determines minimum completion time
  3. Use blockedBy sparingly — Only add dependencies that are truly required
  4. Avoid circular dependencies — Task A blocks B blocks A is a deadlock

Patterns

Independent (Best parallelism):

Task A ─┐
Task B ─┼─→ Integration
Task C ─┘

Sequential (Necessary dependencies):

Task A → Task B → Task C

Diamond (Mixed):

        ┌→ Task B ─┐
Task A ─┤          ├→ Task D
        └→ Task C ─┘

Using blockedBy/blocks

TaskCreate: { subject: "Build API endpoints" }         → Task #1
TaskCreate: { subject: "Build frontend components" }    → Task #2
TaskCreate: { subject: "Integration testing" }          → Task #3
TaskUpdate: { taskId: "3", addBlockedBy: ["1", "2"] }  → #3 waits for #1 and #2

Task Description Best Practices

Every task should include:

  1. Objective — What needs to be accomplished (1-2 sentences)
  2. Owned Files — Explicit list of files/directories this teammate may modify
  3. Requirements — Specific deliverables or behaviors expected
  4. Interface Contracts — How this work connects to other teammates' work
  5. Acceptance Criteria — How to verify the task is done correctly
  6. Scope Boundaries — What is explicitly out of scope

Template

## Objective
Build the user authentication API endpoints.

## Owned Files
- src/api/auth.ts
- src/api/middleware/auth-middleware.ts
- src/types/auth.ts (shared — read only, do not modify)

## Requirements
- POST /api/login — accepts email/password, returns JWT
- POST /api/register — creates new user, returns JWT
- GET /api/me — returns current user profile (requires auth)

## Interface Contract
- Import User type from src/types/auth.ts (owned by implementer-1)
- Export AuthResponse type for frontend consumption

## Acceptance Criteria
- All endpoints return proper HTTP status codes
- JWT tokens expire after 24 hours
- Passwords are hashed with bcrypt

## Out of Scope
- OAuth/social login
- Password reset flow
- Rate limiting

Workload Monitoring

Indicators of Imbalance

Signal Meaning Action
Teammate idle, others busy Uneven distribution Reassign pending tasks
Teammate stuck on one task Possible blocker Check in, offer help
All tasks blocked Dependency issue Resolve critical path first
One teammate has 3x others Overloaded Split tasks or reassign

Rebalancing Steps

  1. Call TaskList to assess current state
  2. Identify idle or overloaded teammates
  3. Use TaskUpdate to reassign tasks
  4. Use SendMessage to notify affected teammates
  5. Monitor for improved throughput

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides strategies and documentation for task decomposition and coordination. No security risks were identified in the provided documentation files.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    3 files scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 10 months ago
version
1.0.2
  • task-decomposition
  • multi-agent
  • dependency-graph
  • workload-balancing
  • task-coordination
  • parallel-execution
  • critical-path
  • team-management

README badge

README badge for wshobson/agents/task-coordination-strategies

Breaks down complex tasks into parallelizable units using decomposition strategies (by layer, component, concern, or ownership), designs dependency graphs to minimize chain depth and identify critical paths, and provides templates for task descriptions with acceptance criteria and interface contracts. Use this skill when coordinating work across multiple agents to avoid dependencies, balance workload, and monitor team progress.

Generated from the current SKILL.md.

How do I decide which decomposition strategy to use?
Choose by layer for full-stack features, by component for microservices, by concern for reviews/audits, and by file ownership to avoid merge conflicts during parallel work.
What's the difference between blockedBy and blocks?
blockedBy means a task waits for other tasks to complete before starting; blocks means a task prevents other tasks from starting. They describe the same dependency from different perspectives.
How do I identify the critical path in a dependency graph?
Find the longest chain of dependent tasks from start to finish—this chain determines the minimum time to complete all work, even with parallel execution of independent tasks.
What signals indicate uneven workload distribution?
One teammate idle while others are busy, one teammate assigned 3x more tasks than others, or all tasks blocked on dependencies suggests rebalancing is needed.

Generated from the current SKILL.md. These answers refresh after source changes.