> For the complete documentation index, see [llms.txt](https://docs.terraforge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terraforge.io/tutorials/first-steps/2-first-terraform-stack/2.2-terraform-validate-and-plan.md).

# 2.2 - Terraform validate & plan

{% embed url="<https://beta-terraforge-public-assets.s3.amazonaws.com/first-steps-2.2-validate-plan.mp4>" %}

## Steps

1. Switch to the **Configuration** tab
2. Click **+ ADD CONFIG**, set **Environment** to `tutorial` and click **ADD**
3. At the screen bottom is the Terraform Console, select **VALIDATE** and press run&#x20;
   1. Terraforge now runs CLI command `terraform validate` on your stack
4. Press the **+** on the right side of the Terraform Console to view the console output
5. Select **PLAN**, the configuration **tutorial** and press run
   1. Terraforge now runs the CLI command `terraform init` and `terraform plan` on your stack
6. Press the **+** on the right side of the Terraform Console and click the **Fullscreen** button in black area to view the console output

{% hint style="info" %}
The **Name** property can be set if multiple configurations shall be deployed in a given environment.
{% endhint %}


---

# 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://docs.terraforge.io/tutorials/first-steps/2-first-terraform-stack/2.2-terraform-validate-and-plan.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.