> 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/creating-dependencies-between-requirements.md).

# Creating Dependencies Between Requirements

### Overview

Requirement dependencies capture sequencing across scope statements.

They prevent downstream work from starting too early.

### Key Concepts

* **Upstream requirement**: prerequisite scope
* **Downstream requirement**: dependent scope
* **Blocks / Blocked by**: sequencing relationship used for planning

### How It’s Used

Use dependencies during discovery and design sequencing.

Use them to communicate prerequisite decisions.

### Benefits

* Cleaner sequencing and planning
* Earlier identification of blocker risk
* Clearer discussion during governance reviews

### Setup Steps

{% stepper %}
{% step %}

### Open the requirement

1. Navigate to **Requirements**.
2. Open the downstream requirement.
   {% endstep %}

{% step %}

### Add a dependency

1. Locate the **Dependencies** area.
2. Select **Add dependency**.
3. Choose the upstream requirement.
4. Select relationship type, such as **Blocked by**.
   {% endstep %}

{% step %}

### Confirm the relationship

1. Confirm the dependency appears on both requirements.
2. Add a comment describing the unblock condition.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Keep dependencies minimal and meaningful.
* Use comments to document why the dependency exists.
* Review dependencies during requirement approval.

### Summary

Dependencies encode prerequisite scope.

They also reduce rework caused by premature execution.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/transformations/creating-dependencies-between-requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.