> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/runbooks/managing-test-plans/creating-a-test-plan.md).
# Creating a Test Plan
Step 1: From the **Test Plans** tab of the **Runbooks** module, click **New Test Plan**.
Step 2: Select whether to start a new plan or modify an existing test plan.
If starting from scratch, click **Next**.
If starting from an existing test plan, select that option, then click **Select** next to the plan to use as a template. Click **Next**.
Step 3: From the **Test Plan Details** tab, insert the test plan title (required) and enter a description and tags. Click **Continue**.
Step 4: From the **Select Procedures** tab, add the relevant procedures to the test plan. Use the filtering options to find desired procedures.
Add new procedures by clicking **Select** next to the procedure to include or delete existing ones from the engagement by clicking the x within the procedure box in the right-hand column. Click **Add X Procedures**.
Step 5: Review the engagement coverage. The plan can still be modified from this page by clicking Add Procedures or clicking the X to remove an existing procedure. The order of procedures can also be changed by selecting a box and dragging it to the desired location.
When ready, click **Create Test Plan**.
The engagement is now ready to be started. Click **Start new engagement**, or click **Close** and return to the **Test Plans** tab.
The test plan is now listed for future access on the Test Plans tab.
---
# 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://docs.plextrac.com/plextrac-documentation/product-documentation/runbooks/managing-test-plans/creating-a-test-plan.md?ask=&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.
