> 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/getting-started/tutorial-creating-a-first-transformation.md).

# Tutorial: Creating a First Transformation

### Overview

Transformations are delivered through requirements, tasks, and tests.

This tutorial creates a small, end-to-end delivery loop in one Project.

### Key Concepts

* **Requirement**: reviewable scope statement
* **Task**: owned execution work tied to scope
* **Test case**: verification step tied to requirements
* **Traceability**: links across requirements, tasks, and tests

### How It’s Used

Use this tutorial after the first Project is created.

Use this tutorial to align delivery teams on a standard flow.

### Benefits

* Faster conversion from discovery to execution
* Clear ownership and progress signals
* Measurable coverage through linked tests

### Setup Steps

{% stepper %}
{% step %}

### Create 3–5 requirements

1. Navigate to **Requirements**.
2. Select **Create**.
3. Enter a requirement statement and acceptance criteria.
4. Set an initial status, such as **Draft**.

Related: [Requirements](/transformations/requirements.md)
{% endstep %}

{% step %}

### Create tasks linked to requirements

1. Open one requirement.
2. Select **Create task** (or equivalent action).
3. Assign one Teammate as owner.
4. Set a due date when scheduling is needed.

Related: [Create and Assign Tasks](/transformations/create-and-assign-tasks.md)
{% endstep %}

{% step %}

### Create test cases for coverage

1. Navigate to **Testing**.
2. Select **Create test case**.
3. Link the test case to the relevant requirement.
4. Set status to **Draft** or **Ready** based on readiness.

Related: [Create Test Cases](/transformations/create-test-cases.md)\
Related: [Linking Tests to Requirements](/transformations/linking-tests-to-requirements.md)
{% endstep %}

{% step %}

### Review progress in a view

1. Open **Tasks**.
2. Filter for open work.
3. Save the configuration as a Save View.

Related: [Working with Views](/getting-started/working-with-views.md)
{% endstep %}
{% endstepper %}

### Best Practices

* Keep one owner per task.
* Use statuses to signal intent, not optimism.
* Link tests early to protect coverage reporting.

### Summary

The Project now contains linked requirements, tasks, and tests.

Next action:

* Add dependency signals: [Dependencies and Relationships](/transformations/dependencies-and-relationships.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/getting-started/tutorial-creating-a-first-transformation.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.