AIPM
Theme

AIPM package

Task Coordination Strategies

@wshobson/task-coordination-strategies@1.0.0

Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing.

Scanned · no issues · Nov 8, 2026

GitHub stars: ★ 42K

LinkedInPost

Install Skill

Pins this version in aipm.package.json and aipm-lock.json.

aipm add @wshobson/task-coordination-strategies@1.0.0

Without project tracking

Writes the skill files only. Add --no-init to skip aipm.package.json and the lockfile.

aipm add @wshobson/task-coordination-strategies@1.0.0 --no-init

How to use

Install the skill above, then run this in your AI tool:

/task-coordination-strategies <your description>

About

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

Source

What gets added to your project

Preview every file this package writes on install before you run the command above.

Summary

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 te...

Skill instructions

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):

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

Sequential (Necessary dependencies):

code
Task A → Task B → Task C

Diamond (Mixed):

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

Using blockedBy/blocks

code
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

code
## 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

SignalMeaningAction
Teammate idle, others busyUneven distributionReassign pending tasks
Teammate stuck on one taskPossible blockerCheck in, offer help
All tasks blockedDependency issueResolve critical path first
One teammate has 3x othersOverloadedSplit 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

Loading package files…

Share this package

Add an Install with AIPM badge

Add this badge to a GitHub README so readers can open the package page and install the same version.

Install with AIPM
[![Install with AIPM](https://www.aipm-registry.com/install-with-aipm.svg)](https://www.aipm-registry.com/skills/wshobson/task-coordination-strategies/1.0.0?utm_source=github&utm_medium=readme&utm_campaign=package_badge)

Publisher

Seth Hobson

This imported publisher has not claimed its AIPM account. A connected account confirms account control, but it does not guarantee that a package is safe.

AI assistant context

What this skill is for

@wshobson/task-coordination-strategies@1.0.0 is an AIPM skill package for All tools. Use it when a project needs the reusable AI behavior described as: 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 te...

Install
aipm add @wshobson/task-coordination-strategies@1.0.0
Use after install
/task-coordination-strategies <your description>

Tool targets

Install command by target

Add --no-init to any of these when you want the skill files without aipm.package.json or aipm-lock.json.

cursor

Run this variant when you want to install the package into cursor.

aipm add @wshobson/task-coordination-strategies@1.0.0 --target cursor --ci

claude

Run this variant when you want to install the package into claude.

aipm add @wshobson/task-coordination-strategies@1.0.0 --target claude --ci

Discussion

Comments (0)

Loading comments…

Package FAQ

Install and compatibility

How to install
Run aipm add @wshobson/task-coordination-strategies@1.0.0 in a project that has AIPM initialized.
Supported tools
@wshobson/task-coordination-strategies@1.0.0 supports All tools.

Before installing

AIPM skills can add files to your project. Review the package name, target, description, license, and publisher before installing. Use a clean branch when trying a new skill.