# Define Issue

This module is arguably one of my favorites! This module will pass the replies to all previous modules to an AI model (`mistral-medium`) and send the user automatic follow-up questions to make sure your mod team has a clear description of the problem without having to ask a lot of follow-ups themselves.

You can pick a persona which describes how the AI agent should present itself and rules which the AI will use to know what follow-up questions to ask. You can also configure how many times the AI is allowed to ask follow-up questions before sending the user to the next module in the pipeline.

The AI will only ask follow-up questions if it believes the user's inputs have not been enough to follow the rules set by you. If the AI deems the ticket as detailed enough it will pass the user on without asking any questions.

<figure><img src="/files/Qv1KTNZe2mMgjW2zIgU6" alt=""><figcaption></figcaption></figure>

The user is always presented with a "skip" button that will dismiss the AI follow-up process and forcefully move forwards in the pipeline even if the AI did not deem the ticket as detailed enough. This behavior is always on and cannot be altered.


---

# Agent Instructions: 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:

```
GET https://docs.threadwatcher.xyz/features/tickets/modules/define-issue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.