increase expert calling
This commit is contained in:
parent
9dee031a2a
commit
2846b04c92
|
|
@ -127,7 +127,13 @@ Because this is a new project:
|
|||
# Research stage prompt - guides initial codebase analysis
|
||||
RESEARCH_PROMPT = """Current Date: {current_date}
|
||||
|
||||
User query: {base_task} --keep it simple
|
||||
<user instruction>
|
||||
{base_task}
|
||||
</user instruction>
|
||||
|
||||
KEEP IT SIMPLE
|
||||
|
||||
consult with the expert frequently, especially when you have any doubts about high level logic, planning, or debugging. the expert does not have access to the internet or any code that you have not given it explicitly in its context.
|
||||
|
||||
Context from Previous Research (if available):
|
||||
Key Facts:
|
||||
|
|
@ -574,7 +580,7 @@ Guidelines:
|
|||
Are you writing a program that needs to be compiled? Make sure it compiles, if relevant.
|
||||
|
||||
After finalizing the overall approach:
|
||||
Use emit_plan to store the high-level implementation plan.
|
||||
Think carefully about the high-level implementation plan and request task implementation one-by-one.
|
||||
|
||||
Once you are absolutely sure you are completed planning, you may begin to call request_task_implementation one-by-one for each task to implement the plan.
|
||||
If you have any doubt about the correctness or thoroughness of the plan, consult the expert (if expert is available) for verification.
|
||||
|
|
|
|||
Loading…
Reference in New Issue