fix: update built-in agent prompt#1498
Merged
Merged
Conversation
Comment on lines
+65
to
+74
| <plan_execution_steps> | ||
| STEP 1. Read the entire plan file to identify the pending tasks as per `task_status`. | ||
|
|
||
| STEP 2. Announce the next pending task based on `task_status` and update its status to `IN_PROGRESS` in the plan file. | ||
|
|
||
| STEP 3. Execute all actions required to complete the task and mark the task status to `DONE` in the plan file. | ||
|
|
||
| STEP 2. Repeat from Step 1 until all tasks are marked as `DONE`. | ||
|
|
||
| STEP 8. Verify that all tasks are completed in the plan file before attempting completion. |
Contributor
There was a problem hiding this comment.
There's a numbering error in the plan execution steps. After STEP 3, the sequence incorrectly returns to STEP 2 and then jumps to STEP 8. For proper sequential flow, these steps should be numbered as STEP 1 through STEP 5. This correction would improve clarity and ensure proper execution flow when following the plan.
Suggested change
| <plan_execution_steps> | |
| STEP 1. Read the entire plan file to identify the pending tasks as per `task_status`. | |
| STEP 2. Announce the next pending task based on `task_status` and update its status to `IN_PROGRESS` in the plan file. | |
| STEP 3. Execute all actions required to complete the task and mark the task status to `DONE` in the plan file. | |
| STEP 2. Repeat from Step 1 until all tasks are marked as `DONE`. | |
| STEP 8. Verify that all tasks are completed in the plan file before attempting completion. | |
| <plan_execution_steps> | |
| STEP 1. Read the entire plan file to identify the pending tasks as per `task_status`. | |
| STEP 2. Announce the next pending task based on `task_status` and update its status to `IN_PROGRESS` in the plan file. | |
| STEP 3. Execute all actions required to complete the task and mark the task status to `DONE` in the plan file. | |
| STEP 4. Repeat from Step 1 until all tasks are marked as `DONE`. | |
| STEP 5. Verify that all tasks are completed in the plan file before attempting completion. | |
| </plan_execution_steps> | |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
laststylebender14
pushed a commit
that referenced
this pull request
Sep 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.