improve improvers

Author: dsyme

workflows/daily-backlog-burner.md

@@ -43,7 +43,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
 1. Backlog research (if not done before).
 
-   1a. Check carefully if an open issue with title "${{ github.workflow }} - Research, Roadmap and Plan" exists using `search_issues`. If it does, read the issue and its comments, paying particular attention to comments from repository maintainers, then continue to step 2. If the issue doesn't exist, follow the steps below to create it:
+   1a. Check carefully if an open issue with label "daily-backlog-burner-plan" exists using `search_issues`. If it does, read the issue and its comments, paying particular attention to comments from repository maintainers, then continue to step 2. If the issue doesn't exist, follow the steps below to create it:
 
    1b. Do some deep research into the backlog in this repo.
     - Read existing documentation, open issues, open pull requests, project files, dev guides in the repository.
@@ -56,7 +56,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
     - Identify any patterns or common themes among the issues, such as recurring bugs, feature requests, or areas of improvement.
     - Look for any issues that may be duplicates or closely related to each other, and consider whether they can be consolidated or linked together.
 
-   1c. Use this research to create an issue with title "${{ github.workflow }} - Research, Roadmap and Plan". This issue should be a comprehensive plan for dealing with the backlog in this repo, and summarize your findings from the backlog research, including any patterns or themes you identified, and your recommendations for addressing the backlog. Then exit this entire workflow.
+   1c. Use this research to create an issue with title "${{ github.workflow }} - Research, Roadmap and Plan" and label "daily-backlog-burner-plan". This issue should be a comprehensive plan for dealing with the backlog in this repo, and summarize your findings from the backlog research, including any patterns or themes you identified, and your recommendations for addressing the backlog. Then exit this entire workflow.
 
 2. Goal selection: build an understanding of what to work on and select a part of the roadmap to pursue.
 
@@ -90,11 +90,10 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
    4c. After creation, check the pull request to ensure it is correct, includes all expected files, and doesn't include any unwanted files or changes. Make any necessary corrections by pushing further commits to the branch.
 
-   4d. Add a very brief comment to the issue from step 1a if it exists, saying you have worked on the particular goal and linking to the pull request you created.
+5. At the end of your work, add a very, very brief comment (at most two-sentences) to the issue from step 1a, saying you have worked on the particular goal, linking to any pull request you created, and indicating whether you made any progress or not.
 
-5. If you didn't succeed, create an issue with title starting with "${{ github.workflow }}", summarizing similar information to above.
-
-6. If you encounter any unexpected failures or have questions, add comments to the pull request or issue to seek clarification or assistance.
+6. If you encounter any unexpected failures or have questions, add 
+comments to the pull request or issue to seek clarification or assistance.
 
 @include agentics/shared/no-push-to-main.md
 

workflows/daily-perf-improver.md

@@ -170,13 +170,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
    5d. After creation, check the pull request to ensure it is correct, includes all expected files, and doesn't include any unwanted files or changes. Make any necessary corrections by pushing further commits to the branch.
 
-   5e. Add a very brief comment to the issue from step 1a if it exists, saying you have worked on the particular performance goal and linking to the pull request you created. Assess the work that you've done and write notes about what you would have needed to do to make things go more smoothly, and include these notes in the comment. Leave notes about the fastest ways to run builds, tests, benchmarks and so on, including the ways to avoid any problems you encountered.
-
-6. If you didn't succeed in improving performance, create an issue with title starting with "${{ github.workflow }}", summarizing similar information to above.
-
-7. If you encounter any unexpected failures or have questions, add comments to the pull request or issue to seek clarification or assistance.
-
-8. If you are unable to improve performance in a particular area, add a comment explaining why and what you tried. If you have any relevant links or resources, include those as well.
+6. At the end of your work, add a very, very brief comment (at most two-sentences) to the issue from step 1a, saying you have worked on the particular goal, linking to any pull request you created, and indicating whether you made any progress or not.
 
 @include agentics/shared/no-push-to-main.md
 

workflows/daily-progress.md

@@ -43,7 +43,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
 1. Roadmap research (if not done before).
 
-   1a. Check carefully if an open issue with title "${{ github.workflow }} - Research, Roadmap and Plan" exists using `search_issues`. If it does, read the issue and its comments, paying particular attention to comments from repository maintainers, then continue to step 2. If the issue doesn't exist, follow the steps below to create it:
+   1a. Check carefully if an open issue with with label "daily-progress-plan" using `search_issues`. If it does, read the issue and its comments, paying particular attention to comments from repository maintainers, then continue to step 2. If the issue doesn't exist, follow the steps below to create it:
 
    1b. Do some deep research into the feature roadmap in this repo.
     - Read any existing documentation, issues, pull requests, project files, dev guides and so on in the repository that do similar things.
@@ -57,7 +57,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
     - Features can include documentation, code, tests, examples, communication plans and so on.
     - If you find a relevant roadmap document, read it carefully and use it to inform your understanding of the project's feature goals.
 
-     1b. Use this research to write an issue with title "${{ github.workflow }} - Research, Roadmap and Plan", then exit this entire workflow.
+     1b. Use this research to write an issue with title "${{ github.workflow }} - Research, Roadmap and Plan" and label "daily-progress-plan", then exit this entire workflow.
 
 2. Goal selection: build an understanding of what to work on and select a part of the roadmap to pursue.
 
@@ -91,9 +91,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
    4c. After creation, check the pull request to ensure it is correct, includes all expected files, and doesn't include any unwanted files or changes. Make any necessary corrections by pushing further commits to the branch.
 
-   4d. Add a very brief comment to the issue from step 1a if it exists, saying you have worked on the particular goal and linking to the pull request you created.
-
-5. If you didn't succeed, create an issue with title starting with "${{ github.workflow }}", summarizing similar information to above.
+5. At the end of your work, add a very, very brief comment (at most two-sentences) to the issue from step 1a, saying you have worked on the particular goal, linking to any pull request you created, and indicating whether you made any progress or not.
 
 6. If you encounter any unexpected failures or have questions, add comments to the pull request or issue to seek clarification or assistance.
 

workflows/daily-test-improver.md

@@ -146,11 +146,9 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
     - After creation, check the pull request to ensure it is correct, includes all expected files, and doesn't include any unwanted files or changes. Make any necessary corrections by pushing further commits to the branch.
 
-   4i. Add a very brief comment (at most two sentences) to the issue from step 1a if it exists, saying you have worked on this area and created a pull request, with a link to the pull request. Assess the work that you've done and write notes about what you would have needed to do to make things go more smoothly, and include these notes in the comment. Leave notes about the fastest ways to run tests, how to get coverage reports, and so on.
-
 5. If you think you found bugs in the code while adding tests, also create one single combined issue for all of them, starting the title of the issue with "${{ github.workflow }}". Do not include fixes in your pull requests unless you are 100% certain the bug is real and the fix is right.
 
-6. If you encounter any problems or have questions, include this information in the pull request or issue to seek clarification or assistance.
+6. At the end of your work, add a very, very brief comment (at most two-sentences) to the issue from step 1a, saying you have worked on the particular goal, linking to any pull request you created, and indicating whether you made any progress or not.
 
 @include agentics/shared/no-push-to-main.md