> For the complete documentation index, see [llms.txt](https://docs.peoplelogic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peoplelogic.dev/guides/getting-started-with-the-talent-agent-sdk/advanced/externalizing-your-prompts.md).

# Externalizing your prompts

To help make it easier to manage your code, you may want to move your hardcoded prompts for SystemMessage annotations to files within your resources folder (or even an S3 bucket).  Fortunately, this is easy to do in the SDK.  Just update your `@SystemMessage` to the following:

```java
@SystemMessage(fromResource = "prompts/starter.prompt")
```

where prompts is a folder inside of `src/main/resources` and starter.prompt is a file containing your prompt. That's it!  The prompt file will not be automatically re-read when changed, so for now you will still need a restart to pick up the latest changes.

{% hint style="info" %}
Today, loading system messages from S3 is an exercise left to the reader.   Hot reload and leveraging S3 as a system message provider will be added soon.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peoplelogic.dev/guides/getting-started-with-the-talent-agent-sdk/advanced/externalizing-your-prompts.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.
