Claude Code Agent Teams

Appearance

SOP-005: Task Assignment and Management ​

ID: SOP-005 | Version: 1.0 | Status: Current | Date: 2026-02-12

Fresh 🌱

Coordinate work across the team using shared task lists, explicit assignments, and task dependencies.

Overview ​

All team members share a single task list. Work is coordinated through explicit assignment by the lead or through self-claiming by available teammates.

Prerequisites ​

  • Agent team created (SOP-002)
  • Multiple teammates spawned (SOP-004)
  • Familiar with team communication

Task Lifecycle ​

Creating Tasks ​

Create Task Manually ​

Create a task: "Refactor authentication module with new OAuth2 flow"

Claude adds to shared list. Status: Pending

Create Multiple Tasks at Once ​

Create these tasks:
1. Research database migration strategies
2. Write migration script for user table
3. Create rollback procedure
4. Test migration in staging
5. Document changes

Assigning Tasks ​

Explicit Assignment by Lead ​

Assign task #3 to the database specialist

Lead explicitly assigns. Teammate must accept or negotiate.

Self-Claiming by Teammates ​

After finishing their current task, teammates automatically:

  1. Check the task list
  2. Find next unclaimed task
  3. Verify no blockers/dependencies
  4. Self-claim and start work

Lead doesn't need to manually assign every task.

Assign Task with Specific Instructions ​

Assign task #7 to the frontend team with instructions:
"This module needs responsive design. Focus on mobile-first approach.
Keep component size under 500 lines. Add comprehensive error states."

Managing Task Dependencies ​

Create Task with Dependencies ​

Create task: "Write unit tests for auth module"
Block on: task #5 "Write authentication module"

Task won't be claimed until task #5 completes.

Set Dependency After Creation ​

Task #8 depends on task #6

Or:

Task #8 is blocked by task #6

View Dependency Graph ​

Show me task dependencies

Or view with:

Ctrl+T (show task list with dependency indicators)

Verify Dependencies Resolved ​

When a task completes, Claude automatically:

  1. Marks it completed
  2. Unblocks dependent tasks
  3. Notifies waiting teammates
  4. Allows next task to be claimed

Tracking Progress ​

View All Tasks ​

Press Ctrl+T in in-process mode or:

Show me the task list

Output format:

Tasks:
  [P] #1: Research OAuth2 libraries
      Owner: None | Depends on: None
  [I] #2: Design auth flow diagram
      Owner: Security Specialist | Depends on: #1
  [C] #3: Implement JWT token generation
      Owner: Backend Dev | Depends on: #2

Legend:

  • [P] = Pending (unclaimed)
  • [I] = In Progress (assigned/claimed)
  • [C] = Completed
  • [B] = Blocked (waiting on dependencies)

Check Specific Teammate's Tasks ​

What is the backend specialist currently working on?

Or select teammate with Shift+Up/Down and check their task.

Get Task Details ​

Show details for task #5

Shows:

  • Title and description
  • Current status
  • Assigned to (teammate)
  • Dependencies
  • Created/completed dates

Updating Task Status ​

Mark Task Complete ​

Mark task #5 as complete

Or teammate completes their current turn:

I've finished the authentication module

Claude marks task as completed automatically.

Reopen Task if Needed ​

Reopen task #3, it needs more work

Changes status back to "In Progress" or "Pending".

Cancel Task ​

Cancel task #7, we're taking a different approach

Removes from active list. Other tasks depending on it also canceled.

Reassigning Work ​

Take Over a Task ​

I'll take task #4 from the database specialist

Transfer ownership from teammate to lead (or to another teammate).

Reassign to Different Teammate ​

Move task #6 from Developer 1 to Developer 2

Task continues with new owner.

Return to Pool (Unassign) ​

Unassign task #3

Task becomes pending again. Any teammate can claim.

Blocking and Unblocking ​

Block a Task Manually ​

Block task #8 until task #5 is complete

Unblock Task Early ​

Task #8 can proceed even though task #5 isn't done

Use carefully - bypasses dependency safety.

Best Practices ​

Task Sizing ​

Too small:

Create task: "Add semicolon to line 42"

❌ Overhead > benefit

Too large:

Create task: "Refactor entire authentication system"

❌ Too long without check-ins

Just right:

Create task: "Implement JWT token generation and refresh logic"

✅ 30-60 minute deliverable

Task Independence ​

Good (parallel work):

  • Task 1: Frontend UI components
  • Task 2: Backend API endpoints
  • Task 3: Integration tests (No file conflicts)

Bad (sequential work):

  • Task 1: Write function
  • Task 2: Call function from Task 1
  • Task 3: Test function from Task 1 (Heavy dependencies)

Clear Task Descriptions ​

❌ Poor:

Fix the bug

✅ Good:

Fix authentication timeout bug:
- User session expires after 15 minutes idle
- Should be 30 minutes per requirements
- Check config validation in auth middleware
- Add test for timeout behavior

Prioritize with Dependencies ​

Create task: "Write database migration"
Create task: "Deploy migration to production"
Task #2 depends on: task #1

Track Blockers ​

What tasks are currently blocked?

Claude shows tasks waiting on dependencies and helps prioritize unblocking them.

Quality Gates with Task Completion ​

Require Review Before Completion ​

Use hooks to enforce standards:

When task completes, require approval from lead
Exit with code 2 if not ready

Configure in settings.

Update Task with Review Notes ​

Task #5 has been approved for merge:
"Code review complete. Tests passing. Documentation updated."

Verification Checklist ​

✓ Tasks created

  • Visible in task list (Ctrl+T)
  • Each has unique ID
  • Status shows Pending

✓ Teammates can claim

  • After finishing, they pick up next task
  • Blockers prevent premature claiming
  • No race conditions between teammates

✓ Dependencies working

  • Setting dependency blocks task
  • Task unblocks when dependency completes
  • Next teammate auto-claims

✓ Status tracking accurate

  • Pending tasks awaiting assignment
  • In Progress shows current owner
  • Completed tasks marked and reviewed

Troubleshooting ​

Q: Task shows blocked but dependency is done A:

  1. Manually unblock: Task #5 can proceed
  2. Or refresh: ask lead to check dependencies
  3. Sometimes lag in status update

Q: Teammate not picking up available tasks A:

  1. They may still be working. Wait a moment
  2. Explicitly assign: Assign task #3 to backend specialist
  3. Or tell them directly

Q: Task marked complete but work isn't done A:

  1. Reopen: Reopen task #4
  2. Add more tasks for remaining work
  3. Set stricter completion standards

Q: Too many blocking dependencies A:

  1. Break work into more independent tasks
  2. Reorder so prerequisites are first
  3. Use overlapping tasks where possible

See Also ​