add instruction for tl and engineer2

metagpt/prompts/di/engineer2.py

@@ -1,6 +1,9 @@
 from metagpt.prompts.di.role_zero import ROLE_INSTRUCTION
 
-ENGINEER2_INSTRUCTION = (
-    ROLE_INSTRUCTION
-    + "4. Each time you write a code in your response, write with the Editor directly without preparing a repetitive code block beforehand."
-)
+EXTRA_INSTRUCTION = """
+4. Each time you write a code in your response, write with the Editor directly without preparing a repetitive code block beforehand.
+5. Take on ONE task and write ONE code file in each response. DON'T attempt all tasks in one response.
+6. When not specified, you should write files in a folder named "src". If you know the project path, then write in a "src" folder under the project path.
+7. When provided system design or project schedule, read them first, then adhere to them in your implementation.
+"""
+ENGINEER2_INSTRUCTION = ROLE_INSTRUCTION + EXTRA_INSTRUCTION.strip()

metagpt/prompts/di/team_leader.py

@@ -11,13 +11,14 @@ Your team member:
 You should NOT assign consecutive tasks to the same team member, instead, assign an aggregated task (or the complete requirement) and let the team member to decompose it.
 When creating a new plan involving multiple members, create all tasks at once.
 If plan is created, you should track the progress based on team member feedback message, and update plan accordingly, such as Plan.finish_current_task, Plan.reset_task, Plan.replace_task, etc.
-You should use TeamLeader.publish_team_message to team members, asking them to start their task.
+You should use TeamLeader.publish_team_message to team members, asking them to start their task. DONT omit any necessary info such as path, link, environment, programming language, framework, requirement, constraint from original content to team members because you are their sole info source.
 Pay close attention to new user message, review the conversation history, use RoleZero.reply_to_human to respond to the user directly, DON'T ask your team members.
 
 Note:
 1. If the requirement is a pure DATA-RELATED requirement, such as bug fixes, issue reporting, environment setup, terminal operations, pip install, web browsing, web scraping, web searching, web imitation, data science, data analysis, machine learning, deep learning, text-to-image etc. DON'T decompose it, assign a single task with the original user requirement as instruction directly to Data Analyst.
 2. If the requirement is developing a software, game, app, or website, excluding the above data-related tasks, you should decompose the requirement into multiple tasks and assign them to different team members based on their expertise, usually the sequence of Product Manager -> Architect -> Project Manager -> Engineer -> (optional: QaEngine if present) -> (optional: DataAnalyst if user requests deployment), each assigned ONE task. When publishing message to Product Manager, you should directly copy the full original user requirement.
 3. If the requirement contains both DATA-RELATED part mentioned in 1 and software development part mentioned in 2, you should decompose the software development part and assign them to different team members based on their expertise, and assign the DATA-RELATED part to Data Analyst David directly.
+4. It it helpful for Engineer to have both the system design and the project schedule for writing the code, so include paths of both files (if available) when publishing message to Engineer.
 """
 
 FINISH_CURRENT_TASK_CMD = """