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

# Requirements

### Overview

Requirements represent scope that must be delivered and validated. They connect discovery inputs to tasks and test cases.

### Key Concepts

* **Requirement**: scope statement with acceptance criteria
* **Lifecycle**: statuses that move scope from draft to completed
* **Traceability**: links from requirements to tasks and tests

### How It’s Used

Use Requirements to define what must be delivered. Use tasks to implement requirements. Use tests to validate requirements.

### Benefits

* Clearer scope boundaries and reduced scope creep
* Better accountability through ownership and status tracking
* Stronger audits through traceability to validation evidence

### Setup Steps

{% stepper %}
{% step %}

### Create a requirement

1. Navigate to a Project.
2. Open **Requirements**.
3. Select **New requirement**.
4. Define title, description, and acceptance criteria.
   {% endstep %}

{% step %}

### Use consistent lifecycle states

Typical states include Draft, In review, Approved, In progress, and Completed. Status names vary by Account configuration.
{% endstep %}

{% step %}

### Link to tasks and tests

Link requirements to tasks for execution tracking. Link requirements to tests for coverage tracking.

* [Create and Assign Tasks](/transformations/create-and-assign-tasks.md)
* [Create Test Cases](/transformations/create-test-cases.md)
  {% endstep %}
  {% endstepper %}

{% hint style="info" %}
When enabled, Console can generate draft tasks and draft test cases from requirement context. Generated output still requires review before approval.
{% endhint %}

### Best Practices

* Require acceptance criteria before approval.
* Keep requirement titles short and scannable.
* Link artifacts that justify scope decisions.
* Use Segments and Processes for reporting consistency when configured.

### Summary

Requirements define scope and connect to execution and validation. Traceability links support reporting, governance, and audits.

### Related

* [Requirements Management](/transformations/requirements-management.md)
* [Requirements View](/transformations/requirements-view.md)
* [Requirements Modification](/transformations/requirements-modification.md)
* [Requirements Rejection](/transformations/requirements-rejection.md)
* [Audit Trail](/transformations/audit-trail.md)
* [Dependencies and Relationships](/transformations/dependencies-and-relationships.md)
* [Creating Dependencies Between Requirements](/transformations/creating-dependencies-between-requirements.md)
* [Custom Fields](/administration/custom-fields.md)
* [Working with Views](/getting-started/working-with-views.md)


---

# 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/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.