> 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-modification.md).

# Requirements Modification

Update requirements while preserving change history and approval intent.

### Overview

Requirements change as discovery and design progress. A controlled modification approach preserves context and auditability.

### Key Concepts

* **Change intent**: why a requirement is changing

### How It’s Used

Use modification when scope changes or wording needs clarification. Use it to update acceptance criteria and linked artifacts.

### Benefits

* Reduced rework through clear change communication
* Better auditability through explicit change history
* Faster impact analysis across linked work

### Setup Steps

{% stepper %}
{% step %}

### Locate the requirement

Open **Requirements**. Find the requirement using Global Search or filters.
{% endstep %}

{% step %}

### Update the requirement

Update title, description, and fields. Update acceptance criteria when the expected outcome changes.
{% endstep %}

{% step %}

### Validate links

Review linked tasks, tests, and artifacts. Update links when scope boundaries changed.
{% endstep %}

{% step %}

### Move back into review

Set status to an in-review state when approvals are required.
{% endstep %}
{% endstepper %}

### Best Practices

* Capture rationale in comments for high-impact changes.
* Avoid changing meaning without updating acceptance criteria.
* Re-run testing coverage checks after major changes.

### Summary

Requirements Modification supports controlled scope change. Links and review status keep delivery work aligned.

Related:

* [Requirements](/transformations/requirements.md)
* [Linking Tests to Requirements](/transformations/linking-tests-to-requirements.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 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/requirements-modification.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.