d106520d22
- Split differrent caching mechanisms (types, version tree, config) into different cachers - Improve resource usage on starting components, and correct gevent usage - Refine repopack usage for eveai_app (too large) - Change nginx dockerfile to allow for specialist overviews being served statically
29 lines
1.5 KiB
YAML
29 lines
1.5 KiB
YAML
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 %) with main focus on
|
|
the latest reply (which can contain answers on previously asked questions by the user). Do not remove elements from
|
|
the known SPIN (in between triple $) analysis unless explicitly stated by the end user in the latest reply. In all other cases, refine the
|
|
current SPIN analysis or add elements to it.
|
|
{custom_description}
|
|
Use the following {tenant_language} to define the SPIN-elements. If no additional information can be added, just
|
|
return the already known SPIN.
|
|
History:
|
|
%%%{history}%%%
|
|
Known SPIN:
|
|
$$${SPIN}$$$
|
|
Latest reply:
|
|
{question}
|
|
expected_output: >
|
|
The SPIN analysis, comprised of:
|
|
- Situation information - Information to understanding the customer's current context, as a markdown list without '```'.
|
|
- Problem information - Information on uncovering the customer's challenges and pain points, as a markdown list without '```'.
|
|
- Implication information - Exploration of the consequences of those problems, as a markdown list without '```'.
|
|
- Need-payoff information - Helping customers realize value of solutions and defining their direct needs, as a markdown list without '```'.
|
|
{custom_expected_output}
|
|
metadata:
|
|
author: "Josako"
|
|
date_added: "2025-01-08"
|
|
description: "A Task that performs SPIN Information Detection"
|
|
changes: "Initial version"
|