> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/transformations/task-dependencies.md).

# Task Dependencies

### Overview

Task dependencies encode sequencing constraints across execution work.

They protect planning and reduce surprise blockers.

### Key Concepts

* **Blocks**: upstream task must complete first
* **Blocked by**: current task cannot start yet
* **Related**: association without sequencing intent

### How It’s Used

Use dependencies during sprint or phase planning.

Use them during blocker triage.

### Benefits

* Clear sequencing for execution work
* Faster identification of prerequisite work
* Cleaner “blocked” reporting signals

### Setup Steps

{% stepper %}
{% step %}

### Add a dependency

1. Open a task.
2. Locate the **Dependencies** area.
3. Select **Add dependency**.
4. Select the related task and relationship type.
   {% endstep %}

{% step %}

### Validate sequencing intent

1. Confirm the dependency represents a true constraint.
2. Remove dependencies that are only “related context”.
   {% endstep %}

{% step %}

### Review for cycles

1. Scan for circular dependencies.
2. Remove or re-sequence relationships when a cycle exists.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Keep dependencies minimal.
* Use comments to document why a dependency exists.
* Pair dependency review with blocked-item review.

### Summary

Dependencies should represent real sequencing constraints.

They should not replace links or references for general context.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/transformations/task-dependencies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.