task-dependency-patterns

Task Dependency Patterns

Overview

Claude Code 2.1.16 introduces a native Task Management System with four tools:

CC 2.1.233 caveat: the Task tools are removed for the newest models unless CLAUDE_CODE_ENABLE_TODO_TOOLS=1 is set in user or managed settings (or the shell). ork cannot ship that flag (CC reads only permissions from plugin settings), so treat every Task-tool call in this skill as conditional on the operator's environment.

• TaskCreate: Create new tasks with subject, description, and activeForm
• TaskUpdate: Update status (pending → in_progress → completed), set dependencies
• TaskGet: Retrieve full task details including blockers
• TaskList: View all tasks with status and dependency summary

Tasks enable structured work tracking, parallel coordination, and clear progress visibility.

When to Use

• Breaking down complex multi-step implementations
• Coordinating parallel work across multiple files
• Tracking progress on large features
• Managing dependencies between related changes
• Providing visibility into work status

Key Patterns

1. Task Decomposition

Break complex work into atomic, trackable units:

Feature: Add user authentication

Tasks:
#1. [pending] Create User model
#2. [pending] Add auth endpoints (blockedBy: #1)
#3. [pending] Implement JWT tokens (blockedBy: #2)
#4. [pending] Add auth middleware (blockedBy: #3)
#5. [pending] Write integration tests (blockedBy: #4)

2. Dependency Chains

Use addBlockedBy to create execution order:

// Task #3 cannot start until #1 and #2 complete
{"taskId": "3", "addBlockedBy": ["1", "2"]}

3. Status Workflow

pending → in_progress → completed
   ↓           ↓
(unblocked)  (active)

pending/in_progress → deleted

• pending: Task created but not started
• in_progress: Actively being worked on
• completed: Work finished and verified
• deleted: Task removed — permanently removes the task

Task Deletion

Use status: "deleted" to permanently remove tasks: