Claude Code Tasks Reference

This skill is a shared reference for Claude Code's Task tools: TaskCreate, TaskGet, TaskUpdate, and TaskList. Load it when your skill or agent needs to create, manage, or coordinate tasks.

This reference covers:

• Complete tool parameter tables for all four Task tools
• Status lifecycle and transition rules
• Naming conventions (subject vs. activeForm)
• Dependency management with DAG design principles
• Metadata conventions for categorization and tracking

For deeper content, load the reference files listed at the end of this document.

TaskCreate

Creates a new task. Returns the created task object with a system-assigned id.

Parameters

Return Value

Returns the full task object including:

• id — System-assigned unique identifier (integer)
• subject — The subject provided
• description — The description provided (if any)
• activeForm — The activeForm provided (if any)
• status — Always pending for newly created tasks
• metadata — The metadata provided (if any)
• blockedBy — Empty array (no dependencies yet)
• blocks — Empty array (no dependents yet)

Example

TaskCreate:
  subject: "Create user authentication module"
  description: "Implement JWT-based auth with login, logout, and token refresh endpoints."
  activeForm: "Creating user authentication module"
  metadata:
    priority: "high"
    complexity: "medium"
    task_group: "user-auth"

TaskGet

Retrieves a single task by its ID. Use this to get full task details including description, metadata, and dependency information.

Parameters

Return Value

Returns the full task object:

• id — Task identifier
• subject — Task title
• description — Full description (may be long)
• activeForm — Present-continuous form (if set)
• status — Current status (pending, in_progress, completed, deleted)
• metadata — Key-value pairs
• blockedBy — Array of task IDs this task depends on
• blocks — Array of task IDs that depend on this task
• owner — The agent or session that owns this task (if set)

TaskUpdate

Updates an existing task. Only the fields you provide are changed; omitted fields remain unchanged.

Parameters

Return Value

Returns the updated task object with all current fields.

Example

TaskUpdate:
  taskId: 5
  status: "in_progress"
  activeForm: "Implementing user authentication module"

TaskList

Lists all tasks in the current task list. Takes no parameters.

Parameters

None.

Return Value

Returns an array of task summary objects. Each summary includes:

• id — Task identifier
• subject — Task title
• status — Current status
• blockedBy — Array of blocking task IDs
• blocks — Array of dependent task IDs
• metadata — Key-value pairs

Note: TaskList returns summary objects. Use TaskGet to retrieve the full description for a specific task.

Status Lifecycle

Tasks follow a simple three-state lifecycle with an additional terminal state.

pending --> in_progress --> completed
   |
   +--> deleted

States

Transition Rules

• pending -> in_progress: Set when an agent begins working on the task.
• in_progress -> completed: Set when the task is verified as done. Only mark complete after verification passes.
• in_progress -> pending: Valid for resetting a task (e.g., after a failed attempt or interrupted session).
• pending -> deleted: Remove a task that is no longer needed.
• in_progress -> deleted: Cancel a task that is in progress.
• Blocked tasks: A task with non-empty blockedBy (where blockers are not yet completed) should not be started. The system does not enforce this automatically — your orchestration logic must check dependencies before transitioning to in_progress.

Naming Conventions

Subject (Imperative)

The subject field uses imperative mood — a command that describes what the task will accomplish:

activeForm (Present-Continuous)

The activeForm field uses present-continuous tense — describing what is happening while the task runs:

The activeForm appears in the task list UI while the task status is in_progress. If omitted, the UI falls back to the subject.

Dependency Management

Tasks support dependency tracking via blockedBy and blocks fields, forming a Directed Acyclic Graph (DAG).

Fields

• blockedBy: Array of task IDs that must complete before this task can start. Set via addBlockedBy in TaskUpdate.
• blocks: Array of task IDs that are waiting on this task. Set via addBlocks in TaskUpdate. This is the inverse of blockedBy.

Setting Dependencies

Dependencies are set after task creation using TaskUpdate:

TaskUpdate:
  taskId: 5
  addBlockedBy: [3, 4]

This means task 5 cannot start until tasks 3 and 4 are both completed.

DAG Design Principles

1. No cycles: Never create circular dependencies (A blocks B, B blocks C, C blocks A). This creates deadlocks where no task can proceed.
2. Minimize depth: Prefer wider, shallower dependency graphs. Deep chains (A -> B -> C -> D -> E) serialize execution and slow throughput.
3. Depend on producers, not peers: A task should depend on the task that produces what it needs, not on unrelated tasks at the same level.
4. One-way information flow: Dependencies should follow the data flow — upstream tasks produce artifacts that downstream tasks consume.
5. Independent tasks run in parallel: Tasks at the same dependency level (no dependencies between them) can execute concurrently.

Common Dependency Patterns

Metadata Conventions

The metadata field accepts arbitrary string key-value pairs. These common keys are used across the agent-alchemy ecosystem:

Metadata Replacement Behavior

TaskUpdate's metadata field performs a full replacement, not a merge. To add a single key, you must read the existing metadata first, add the key, and provide the complete object:

TaskGet: taskId=5
# Returns metadata: { priority: "high", task_group: "auth" }

TaskUpdate:
  taskId: 5
  metadata:
    priority: "high"
    task_group: "auth"
    complexity: "medium"

Reference Files

For deeper content on task design patterns and common mistakes, load these reference files:

Task Patterns

Covers dependency graph design patterns (linear, fan-out, fan-in, diamond), task right-sizing guidance, multi-agent coordination via tasks, and metadata strategies.

Read ${CLAUDE_PLUGIN_ROOT}/skills/cc-tasks/references/task-patterns.md

Anti-Patterns

Documents common mistakes when using Tasks: circular dependencies, over-granular tasks, missing activeForm, batch status update pitfalls, duplicate task creation, and more. Each anti-pattern includes the problem, why it matters, and the correct alternative.

Read ${CLAUDE_PLUGIN_ROOT}/skills/cc-tasks/references/anti-patterns.md