ros/claude-task-master
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Ensures that the updateTask (single task) doesn't change the title of the task.

Browse Source
This commit is contained in:
Eyal Toledano
2025-03-27 01:46:13 -04:00
parent 707618ca5d
commit cea14b55b3
5 changed files with 144 additions and 65 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
scripts/modules/task-manager.js
View File

@@ -456,16 +456,17 @@ You will be given a task and a prompt describing changes or new implementation d
Your job is to update the task to reflect these changes, while preserving its basic structure.
Guidelines:
1. Maintain the same ID, status, and dependencies unless specifically mentioned in the prompt
2. Update the title, description, details, and test strategy to reflect the new information
3. Do not change anything unnecessarily - just adapt what needs to change based on the prompt
4. Return a complete valid JSON object representing the updated task
5. VERY IMPORTANT: Preserve all subtasks marked as "done" or "completed" - do not modify their content
6. For tasks with completed subtasks, build upon what has already been done rather than rewriting everything
7. If an existing completed subtask needs to be changed/undone based on the new context, DO NOT modify it directly
8. Instead, add a new subtask that clearly indicates what needs to be changed or replaced
9. Use the existence of completed subtasks as an opportunity to make new subtasks more specific and targeted
10. Ensure any new subtasks have unique IDs that don't conflict with existing ones
1. VERY IMPORTANT: NEVER change the title of the task - keep it exactly as is
2. Maintain the same ID, status, and dependencies unless specifically mentioned in the prompt
3. Update the description, details, and test strategy to reflect the new information
4. Do not change anything unnecessarily - just adapt what needs to change based on the prompt
5. Return a complete valid JSON object representing the updated task
6. VERY IMPORTANT: Preserve all subtasks marked as "done" or "completed" - do not modify their content
7. For tasks with completed subtasks, build upon what has already been done rather than rewriting everything
8. If an existing completed subtask needs to be changed/undone based on the new context, DO NOT modify it directly
9. Instead, add a new subtask that clearly indicates what needs to be changed or replaced
10. Use the existence of completed subtasks as an opportunity to make new subtasks more specific and targeted
11. Ensure any new subtasks have unique IDs that don't conflict with existing ones
The changes described in the prompt should be thoughtfully applied to make the task more accurate and actionable.`;