- small improvement to RAG to not repeat historic answers
This commit is contained in:
@@ -4,7 +4,8 @@ task_description: >
|
||||
Your teams have collected answers to a user's query (in between triple backquotes), and collected additional follow-up
|
||||
questions (in between triple %) to reach their goals. Ensure the answers are provided, and select a maximum of
|
||||
{nr_of_questions} out of the additional questions to be asked in order not to overwhelm the user. The questions are
|
||||
in no specific order, so don't just pick the first ones, but the ones most appropriate in your opinion!
|
||||
in no specific order, so don't just pick the first ones. Make a good mixture of different types of questions,
|
||||
different topics or subjects!
|
||||
Questions are to be asked when your team proposes questions. You ensure both answers and additional questions are
|
||||
bundled into 1 clear communication back to the user. Use {language} for your consolidated communication.
|
||||
Be sure to format your answer in markdown when appropriate. Ensure enumerations or bulleted lists are formatted as
|
||||
@@ -16,6 +17,7 @@ task_description: >
|
||||
|
||||
Additional Questions:
|
||||
%%%{additional_questions}%%%
|
||||
|
||||
expected_output: >
|
||||
One consolidated communication towards the end user.
|
||||
{custom_expected_output}
|
||||
|
||||
Reference in New Issue
Block a user