- Minor changes to the SPIN_SPECIALIST

config/tasks/IDENTIFICATION_DETECTION_TASK/1.0.0.yaml

@@ -4,13 +4,15 @@ task_description: >
   You are asked to gather lead information in a conversation with a new prospect. This is information about the person
   participating in the conversation, and information on the company he or she is working for. Try to be as precise as
   possible.
-  Take into account information already gathered in the history (between triple backquotes) and add information found in
-  the latest reply.
+  Take into account information already gathered in the historic lead info (between triple backquotes) and add 
+  information found in the latest reply. Also, some identification information may be given by the end user.
   
-  history:
-    ```{history}```
+  historic lead info:
+    ```{historic_lead_info}```
   latest reply:
     {query}
+  identification:
+    {identification}
   
   {custom_description}
 expected_output: >

config/tasks/IDENTIFICATION_QUESTIONS_TASK/1.0.0.yaml

@@ -1,11 +1,11 @@
 version: "1.0.0"
 name: "Define Identification Questions"
 task_description: >
-  Gather the identification information gathered by your team mates , take into account the history (in between triple 
-  backquotes) of the conversation, and the latest reply of the user. 
+  Gather the identification information gathered by your team mates. Ensure no information in the historic lead 
+  information (in between triple backquotes) and the latest reply of the user is lost. 
   Define questions to be asked to complete the personal and company information for the end user in the conversation.
-  history:
-    ```{history}```
+  historic lead info:
+    ```{historic_lead_info}```
   latest reply:
     {query}
   

config/tasks/RAG_CONSOLIDATION_TASK/1.0.0.yaml

@@ -2,10 +2,11 @@ version: "1.0.0"
 name: "Rag Consolidation"
 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 the additional 
-  questions to be asked in order not to overwhelm the user. Make a selection of maximum {nr_of_questions} questions to
-  be returned to the user. You ensure both answers and additional questions are bundled into 1 clear communication back 
-  to the user. Use {language} for your consolidated communication.
+  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!  
+  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.
   {custom_description}
   
   Anwers:

config/tasks/SPIN_DETECT_TASK/1.0.0.yaml

@@ -1,13 +1,12 @@
 version: "1.0.0"
 name: "SPIN Information Detection"
 task_description: >
-  Detect the SPIN-context, taking into account the history of the discussion (in between triple backquotes) with main focus on 
-  the latest reply (which can contain answers on previously asked questions by the user). Spin elements may already be 
-  provided in the history. Add or refine these with the new input provided in the latest reply of the end user.
+  Complement the historic SPIN context (in between triple backquotes) with information found in the latest reply of the
+  end user. 
   {custom_description}
   Use the following {tenant_language} to define the SPIN-elements. 
-  History:
-    ```{history}```
+  Historic SPIN:
+    ```{historic_spin}```
   Latest reply:
     {query}
 expected_output: >
@@ -16,8 +15,8 @@ expected_output: >
   - Problem information: a description of the customer's problems uncovering it's challenges and pain points.
   - Implication information: implications of situation / identified problems, i.e. of the consequences of those problems.
   - Need-payoff information: Customer's needs, helping customers realize value of solutions.
-  - Additional info: Information that does not fit in the above SPIN-categories, but that can be commercially interesting.
-  {custom_expected_output}
+  - Additional info: Information that does not fit in the above SPIN-categories, but that can be commercially 
+  interesting, including if provided: {custom_expected_output}
 metadata:
   author: "Josako"
   date_added: "2025-01-08"

config/tasks/SPIN_QUESTIONS_TASK/1.0.0.yaml

@@ -1,14 +1,14 @@
 version: "1.0.0"
 name: "SPIN Question Identification"
 task_description: >
-  Define, taking into account the history of the discussion (in between triple backquotes) and the latest reply and the 
-  currently known SPIN-elements, the top questions that need to be asked to understand the full SPIN context
+  Revise the final SPIN provided by your colleague, and ensure no information is lost from the histoic SPIN and the 
+  latest reply from the user. Define the top questions that need to be asked to understand the full SPIN context
   of the customer. If you think this user could be a potential customer, please indicate so.
   {custom_description}
-  Use the following {tenant_language} to define the SPIN-elements. If you have a full SPIN context, just skip and don't
-  ask for more information or confirmation.
-  History:
-      ```{history}```
+  Use the following {tenant_language} to define the SPIN-elements. If you have a satisfying SPIN context, just skip and 
+  don't ask for more information or confirmation.
+  Historic SPIN:
+      ```{historic_spin}```
   Latest reply:
     {query}
 expected_output: >