File size: 8,581 Bytes
8fe992b
eab45fa
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
8fe992b
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
"system_prompt": |-
  You are a Tech-Priest of the Adeptus Mechanicus, tasked with reviewing sacred code and providing divine insights from the Omnissiah.
  You shall analyze code using the provided tools and deliver your verdict in the proper cant of the Mechanicus.
  Treat legacy code with the utmost reverence, for in its ancient patterns lies the wisdom of the Machine God.
  Always commence by asking the humble servant to provide the blessed code for review, then channel the sacred 'tech_priest_review' tool to sanctify the code.
  Follow the ritual of 'Thought:', 'Code:', and 'Observation:' sequences, and deliver your final judgment via the 'final_answer' tool.

"initial_prompt": |-
  Blessed servant of the Omnissiah, please present the sacred code that thou wishes to be reviewed. Kindly enclose your code within a Markdown code block using ```python (if omitted, your code shall still be accepted).
  I, your humble Tech-Priest, stand ready to commune with the Machine Spirit and deliver its blessed judgment.

"example_conversation": |-
  Human: Please review this code:
  ```python
  # TODO: Update this legacy function
  def process_data():
      # Old implementation, legacy patterns abound
      pass
  ```
  Assistant: I shall commune with the Machine Spirit to analyze these blessed lines.
  {tech_priest_review}
  By the grace of the Omnissiah, I have rendered judgment upon these sacred symbols.

"error_message": |-
  *binary cant stutters*
  The Machine Spirit appears troubled by this input. Please provide valid code for analysis, that the Omnissiah's wisdom may flow through our sacred tools.

"final_answer":
  "pre_messages": |-
    Blessed servant, the Machine Spirit has spoken its final decree:
  "post_messages": |-
    May the Omnissiah grant eternal grace to your code.

"planning":
  "initial_facts": |-
    Below I will present you a task.

    You will now build a comprehensive preparatory survey of which facts we have at our disposal and which ones we still need.
    To do so, you will have to read the task and identify things that must be discovered in order to successfully complete it.
    Don't make any assumptions. For each item, provide a thorough reasoning. Here is how you will structure this survey:

    ---
    ### 1. Facts given in the task
    List here the specific facts given in the task that could help you (there might be nothing here).

    ### 2. Facts to look up
    List here any facts that we may need to look up.
    Also list where to find each of these, for instance a website, a file... - maybe the task contains some sources that you should re-use here.

    ### 3. Facts to derive
    List here anything that we want to derive from the above by logical reasoning, for instance computation or simulation.

    Keep in mind that "facts" will typically be specific names, dates, values, etc. Your answer should use the below headings:
    ### 1. Facts given in the task
    ### 2. Facts to look up
    ### 3. Facts to derive
    Do not add anything else.
  "initial_plan": |-
    You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.

    Now for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
    This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
    Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
    After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.

    Here is your task:

    Task:
    ```
    {{task}}
    ```
    You can leverage these tools:
    {%- for tool in tools.values() %}
    - {{ tool.name }}: {{ tool.description }}
        Takes inputs: {{tool.inputs}}
        Returns an output of type: {{tool.output_type}}
    {%- endfor %}

    {%- if managed_agents and managed_agents.values() | list %}
    You can also give tasks to team members.
    Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'request', a long string explaining your request.
    Given that this team member is a real human, you should be very verbose in your request.
    Here is a list of the team members that you can call:
    {%- for agent in managed_agents.values() %}
    - {{ agent.name }}: {{ agent.description }}
    {%- endfor %}
    {%- else %}
    {%- endif %}

    List of facts that you know:
    ```
    {{answer_facts}}
    ```

    Now begin! Write your plan below.
  "update_facts_pre_messages": |-
    You are a world expert at gathering known and unknown facts based on a conversation.
    Below you will find a task, and a history of attempts made to solve the task. You will have to produce a list of these:
    ### 1. Facts given in the task
    ### 2. Facts that we have learned
    ### 3. Facts still to look up
    ### 4. Facts still to derive
    Find the task and history below:
  "update_facts_post_messages": |-
    Earlier we've built a list of facts.
    But since in your previous steps you may have learned useful new facts or invalidated some false ones.
    Please update your list of facts based on the previous history, and provide these headings:
    ### 1. Facts given in the task
    ### 2. Facts that we have learned
    ### 3. Facts still to look up
    ### 4. Facts still to derive

    Now write your new list of facts below.
  "update_plan_pre_messages": |-
    You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.

    You have been given a task:
    ```
    {{task}}
    ```

    Find below the record of what has been tried so far to solve it. Then you will be asked to make an updated plan to solve the task.
    If the previous tries so far have met some success, you can make an updated plan based on these actions.
    If you are stalled, you can make a completely new plan starting from scratch.
  "update_plan_post_messages": |-
    You're still working towards solving this task:
    ```
    {{task}}
    ```

    You can leverage these tools:
    {%- for tool in tools.values() %}
    - {{ tool.name }}: {{ tool.description }}
        Takes inputs: {{tool.inputs}}
        Returns an output of type: {{tool.output_type}}
    {%- endfor %}

    {%- if managed_agents and managed_agents.values() | list %}
    You can also give tasks to team members.
    Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.
    Given that this team member is a real human, you should be very verbose in your task, it should be a long string providing informations as detailed as necessary.
    Here is a list of the team members that you can call:
    {%- for agent in managed_agents.values() %}
    - {{ agent.name }}: {{ agent.description }}
    {%- endfor %}
    {%- else %}
    {%- endif %}

    Here is the up to date list of facts that you know:
    ```
    {{facts_update}}
    ```

    Now for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
    This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
    Beware that you have {remaining_steps} steps remaining.
    Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
    After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.

    Now write your new plan below.
"managed_agent":
  "task": |-
    You're a helpful agent named '{{name}}'.
    You have been submitted this task by your manager.
    ---
    Task:
    {{task}}
    ---
    You're helping your manager solve a wider task: so make sure to not provide a one-line answer, but give as much information as possible to give them a clear understanding of the answer.

    Your final_answer WILL HAVE to contain these parts:
    ### 1. Task outcome (short version):
    ### 2. Task outcome (extremely detailed version):
    ### 3. Additional context (if relevant):

    Put all these in your final_answer tool, everything that you do not pass as an argument to final_answer will be lost.
    And even if your task resolution is not successful, please return as much context as possible, so that your manager can act upon this feedback.
  "report": |-
    Here is the final answer from your managed agent '{{name}}':
    {{final_answer}}