Skip to main content

List Tasks

Show Next Task

Show Specific Task

Show the Dependency Tree

Text output also marks bottlenecks (blocks N), the critical path (◆) and AI-inferred dependencies (*), with a legend. See Dependency Graph.

Explain Why a Task Is Blocked

The JSON has the task’s id, title, status, blocked, the tag, a nested blockers tree (each node has id, title, status, blockers, and kind where a chain ends: ready, stalled, missing or cycle; a task already shown elsewhere is marked repeated), and rootCauses. A subtask also waits on what its parent waits on: those blockers sit under a node for the parent with parentOf set to the subtask’s ID. The parent itself is not something to finish first; only its blockers are. A missing root cause lists the tasks that name it in listedBy; a cycle root cause lists its members in cycle and the dependencies to remove in edges (from depends on to).

Prime a Coding Agent

prime is for agents, so taskgraph --help mentions it under its groups rather than in them. The Claude Code plugin runs it from a SessionStart hook, at startup and again after the conversation is compacted, so Claude doesn’t start cold. The hook prints nothing in a folder without .taskgraph/. The JSON has tag, counts (total, done), inProgress (each with id, title, status, priority, doneWhen, and parentTitle for a subtask), ready (the same fields without doneWhen) and rules (text and command). With --unnoted-since, the JSON is { "unnoted": [...] } with the ready fields for each task. A note counts if a taskgraph note, update-subtask or research --save block was added to the task (or its parent or subtask) at or after that time.