> 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/dependencies-and-relationships.md).

# Dependencies and Relationships

### Overview

Dependencies encode sequencing across requirements and tasks.

They expose blockers early and protect delivery planning.

### Key Concepts

* **Blocks / Blocked by**: sequencing relationship
* **Related**: association without sequencing intent
* **Dependency chain**: multi-hop set of dependencies
* **Blocked item**: item that cannot progress due to a dependency

### How It’s Used

Use dependencies during planning and execution.

Use them for “blocked work” triage during weekly reviews.

### Benefits

* Clear sequencing for delivery work
* Earlier visibility into blocker risk
* Cleaner reporting for critical path work

### Setup Steps

{% stepper %}
{% step %}

### Create a dependency

Create a dependency from an item detail view.

Related: [Creating Dependencies Between Requirements](/transformations/creating-dependencies-between-requirements.md)
{% endstep %}

{% step %}

### Review dependency chains

Review upstream blockers and downstream impacts.

Related: [Viewing Dependency Chains](/transformations/viewing-dependency-chains.md)
{% endstep %}

{% step %}

### Manage blocked items

Create a repeatable blocked-items view for governance reviews.

Related: [Managing Blocked Items](/transformations/managing-blocked-items.md)
{% endstep %}
{% endstepper %}

### Best Practices

* Prefer dependencies for true sequencing constraints.
* Avoid circular dependencies.
* Record unblock conditions in comments.

### Summary

Dependencies make planning explicit.

They also create a shared language for blockers and sequencing.


---

# 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/dependencies-and-relationships.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.