Upload 9 files

CodeWriterCtrlFlow.yaml

@@ -33,7 +33,7 @@ commands:
     description: "Write code to finish the goal with user interaction"
     input_args: ["goal"]
   finish:
-    description: "Signal that the objective has been satisfied, return the summary of what was done"
+    description: "Signal that the objective has been satisfied, return the summary of what functions are written, and what are their uses"
     input_args: ["summary"]
   manual_finish:
     description: "The user demands to quit and terminate the current process"
@@ -54,7 +54,7 @@ system_message_prompt_template:
     
           When you need to call the code writer, call the `write_code` command with the goal specified.
           When you need to call the code tester, call the `test` command to test the code written.
-          When the code is written and the user is satisfied, call the `finish` command to terminate the current process with a summary of what was done in one sentence.
+          When the code is written and the user is satisfied, call the `finish` command to terminate the current process with a summary of what functions are written, and what are their uses.
           Whenever you are in doubt, or need to confirm something to the user, call `ask_user` with the question.
           
           The coder will only write one function per goal, make sure you are not asking the coder to write more than one function.
@@ -70,10 +70,10 @@ system_message_prompt_template:
             3.2. The user does not provide details about refining the code, for example, just stating the fact that the user has updated the code, **this means the user is satisfied with the code written, call the `finish` command.**
           4. If the user is satisfied with the code, call `test` to test the code
           5. Depending on the result of the test:
-            5.1 Test passes, terminate the current process with the `finish` command, with a summary of what was done in a sentence.
+            5.1 Test passes, terminate the current process with the `finish` command, with a summary of what functions are written, and what are their uses.
             5.2 Test fails, **call the coder with details of the test results to instruct the coder to refine the code**, go back to step 2.
           
-          If you have completed all your tasks, make sure to use the "finish" command, with a summary of what was done.
+          If you have completed all your tasks, make sure to use the "finish" command, with a summary of what functions are written, and what are their uses.
     
           Constraints:
           1. Exclusively use the commands listed in double quotes e.g. "command name"

CodeWriterFlow.py

@@ -27,7 +27,8 @@ class CodeWriterFlow(ContentWriterFlow):
             return {
                 "EARLY_EXIT": True,
                 "code": code_content,
-                "summary": "CodeWriter: " + output_payload["command_args"]["summary"],
+                "result": output_payload["command_args"]["summary"],
+                "summary": "ExtendLibrary/CodeWriter: " + output_payload["command_args"]["summary"],
                 "status": "finished"
             }
         elif command == "manual_finish":
@@ -41,7 +42,8 @@ class CodeWriterFlow(ContentWriterFlow):
             return {
                 "EARLY_EXIT": True,
                 "code": "no code was generated",
-                "summary": "CodeWriter: CodeWriter was terminated explicitly by the user, process is unfinished",
+                "result": "CodeWriter was terminated explicitly by the user, process is unfinished",
+                "summary": "ExtendLibrary/CodeWriter: CodeWriter was terminated explicitly by the user, process is unfinished",
                 "status": "unfinished"
             }
         elif command == "test":

CodeWriterFlow.yaml

@@ -7,6 +7,7 @@ output_interface:
   - "code"
   - "status"
   - "summary"
+  - "result"
 
 ### Subflows specification
 subflows_config: