> For the complete documentation index, see [llms.txt](https://docs.rainbowstandard.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rainbowstandard.io/rainbow-standard-documents/procedural-templates/project-design-document-template.md).

# Project Design Document template

This document summarizes all key elements of a project, allowing Rainbow and the general public to have a complete understanding of its actions and expected results.

:point\_right: Download the template [here](https://docs.google.com/document/d/1uxxsnO3zkgVvsL42l79erLBKpfeCk2V6Yg2vh_yJ6Ss/edit?usp=sharing)

{% hint style="info" %}
The data, responses, and their proof submitted by the Project Developer are used to generate the PDD through the Rainbow Certification platform. See the [PDD creation](/rainbow-standard-documents/procedures-manual/project-certification-procedure.md#pdd-creation) section of the Procedures Manual for more information.
{% endhint %}

{% hint style="info" %}
Templates are for reference only. If a template conflicts with the Standard or a methodology, the Standard or methodology takes precedence. Project Developers do not need to use the exact template file, as long as they address all template content concisely and in grouped form.
{% endhint %}

{% embed url="<https://docs.google.com/document/d/1uxxsnO3zkgVvsL42l79erLBKpfeCk2V6Yg2vh_yJ6Ss/edit?usp=sharing>" %}


---

# 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.rainbowstandard.io/rainbow-standard-documents/procedural-templates/project-design-document-template.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.