> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/implementation-guides/team-implementation-guide/prerequisites-project-plan-templates.md).

# Prerequisites: project plan templates

Downloadable project plan templates and suggested timelines to guide your Snyk team implementation

The templates provided below are the basis of the following sections of this guide.\
You can download and use these templates in your project management system.

{% hint style="info" %}
The suggested timelines are typically for individual teams and small companies, which may involve a small team or company. Adjust accordingly for what makes sense for your company.
{% endhint %}

You can download or import these plans:

* Comma Separated Values (.csv) - [*Download*](https://assets.ctfassets.net/4un77bcsnjzw/5IT8v4WlcYTlq5LHYGC82T/62b88657a50d1051b45c752c72252175/Team_Implementation_Project_Plan.csv)
* .csv formatted for Asana - [*Download*](https://assets.ctfassets.net/4un77bcsnjzw/2xnLzEX3mZ9oxqCPS3m9qd/3e5ac6f600109f401f63f082045053b0/Team_Implementation_Project_Plan_-_Asana.csv)
* Microsoft Excel - [*Download*](https://assets.ctfassets.net/4un77bcsnjzw/6UGko1dUlCd9kCZt4BqkKe/d6a46b052f2ebf873ad84c6e8b8e0b60/Team_Implementation_Project_Plan.xlsx)


---

# 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.snyk.io/implementation-guides/team-implementation-guide/prerequisites-project-plan-templates.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.