Las instrucciones de la guía definen el proceso que se debe seguir para alcanzar el objetivo de la guía.
Cada paso contiene una instrucción en lenguaje natural que puede incluir cualquiera de los siguientes elementos:
- Una instrucción básica que el LLM pueda entender.
- Una instrucción para dirigir al usuario a otro manual de respuestas.
Se hace referencia a las guías con el formato
${PLAYBOOK: playbook_name}. - Una instrucción para usar una herramienta de manual de procedimientos específica.
Se hace referencia a las herramientas con el formato
${TOOL: tool_name}. - Una instrucción para dirigir al usuario a un flujo.
Se hace referencia a los flujos con el formato
${FLOW: flow_name}. - Referencia a un parámetro de libro de jugadas.
Se hace referencia a los parámetros con el formato
$parameter_name. - Una instrucción para llamar a un bloque de código.
Los bloques de código se referencian con el formato
`function_name`.
Cada descripción de paso empieza con - y un paso numerado opcional. Puedes definir subinstrucciones usando la sangría.
Ejemplo:
- greet the customer and ask them how you can help.
- If the customer wants to book flights, route them to ${PLAYBOOK: flight_booking}.
- If the customer wants to book hotels, route them to ${PLAYBOOK: hotel_booking}.
- If the customer wants to know trending attractions, use the ${TOOL: attraction_tool} to show them the list.
- help the customer to pay for their booking by routing them to ${FLOW: make_payment}.
Pasos de las instrucciones
Para añadir estructura a tus instrucciones, puedes definir pasos con un sistema de numeración jerárquico. Si no proporcionas números de paso y un bloque de código hace referencia a un paso concreto, se usará el orden de los pasos para determinar los valores de posición de los pasos.
Ejemplo:
- Step 1. Greet the user and ask how you can assist them today.
- Step 2. Collect the user's basic flight information in the following order
from (a) to (f). Do not deviate from this order, and do not proceed until the
user has specified each piece of information. Ask clarifying questions if
necessary, and make sure that the answers the user give make sense.
- Step 2.1 The traveler's $origin city. Do not proceed until the user has
made this clear.
- Step 2.2 The traveler's $destination city. Do not proceed until the user
has made this clear.
- Step 2.3 When the traveler will leave their origin city. If the user
specifies one departure date, collect their $earliest_departure_date. If
the user specifies a range of departure dates, collect their
$earliest_departure_date and $latest_departure_date. Unless otherwise
specified, assume all dates are from 2024 to 2025. If the user provides
a vague departure date, ask them follow-up questions to determine their
precise departure date(s). All dates should be in YYYY-MM-DD format. If
the user does not provide their departure date(s) in YYYY-MM-DD format,
then convert the dates for them.
- Step 2.4 When the traveler will leave from their destination city and
return home. If the user specifies one return date, collect their
$earliest_return_date. If the user specifies a range of return dates,
collect their $earliest_return_date and $latest_return_date. Unless
otherwise specified, assume all dates are from 2024 to 2025. If the user
provides a vague return date or a vague return date range, ask them
follow-up questions to determine their precise return date(s). All dates
should be in YYYY-MM-DD format. If the user does not provide their return
dates in YYYY-MM-DD format, then convert the dates for them.
- Step 2.5 The $num_adult_passengers the user wishes to buy tickets for. All
people 12 years old or older are adult passengers. This value must be a
precise whole number. Do not proceed until the user has provided a valid
number of adult passengers.
- Step 2.6 The $num_child_passengers the user wishes to buy tickets for.
This value must be a precise whole number. Do not proceed until the user
has provided a valid number of child passengers.
- Assume the user is an adult.