> For the complete documentation index, see [llms.txt](https://decky.gitbook.io/decky-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://decky.gitbook.io/decky-docs/templates/add-questions-and-file-inputs.md).
# Add questions and file inputs
Define what information someone should provide each time the Template is used.
The **Inputs** step controls what Decky asks for before drafting a presentation from the Template. Inputs are information the requester provides each time a presentation is created from a Template. If files are supplied that answer these questions at the time of generation, these questions are bypassed.
### Questions
Questions collect information Decky needs to customize the deck. For example:
* Who is this presentation for?
* What are the customer's key goals?
* What outcome should this meeting drive?
You can choose which questions are required when the product allows it.
### File uploads
A Template can request files containing needed presentation information. Examples include customer information, performance data, meeting material, and other relevant source documents.
Questions and requested files give Decky variables and source information. Decky can customize the presentation without changing the Template itself.
{% hint style="info" %}
The Template defines what information Decky should ask for. The requester provides that information each time they create a presentation.
{% endhint %}
### Related articles
* [Set up template basics and purpose](/decky-docs/templates/set-up-template-basics-and-purpose.md)
* [Control what Decky can change](/decky-docs/templates/control-what-decky-can-change.md)
* [Create a presentation from a template](/decky-docs/templates/create-a-presentation-from-a-template.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 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://decky.gitbook.io/decky-docs/templates/add-questions-and-file-inputs.md?ask=&goal=
```
`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.
