From 3a32d9723e88e1d526b0837fc5795559b9cf5592 Mon Sep 17 00:00:00 2001 From: anj-s <32556631+anj-s@users.noreply.github.com> Date: Wed, 1 Apr 2026 10:19:47 -0700 Subject: [PATCH] feat(core): enhance tracker task schemas for detailed titles and descriptions (#23902) --- packages/core/src/core/__snapshots__/prompts.test.ts.snap | 2 ++ packages/core/src/prompts/snippets.legacy.ts | 3 ++- packages/core/src/prompts/snippets.ts | 3 ++- packages/core/src/tools/definitions/trackerTools.ts | 8 +++++--- 4 files changed, 11 insertions(+), 5 deletions(-) diff --git a/packages/core/src/core/__snapshots__/prompts.test.ts.snap b/packages/core/src/core/__snapshots__/prompts.test.ts.snap index 40a3ee6a52..f95a4cc8df 100644 --- a/packages/core/src/core/__snapshots__/prompts.test.ts.snap +++ b/packages/core/src/core/__snapshots__/prompts.test.ts.snap @@ -2908,6 +2908,7 @@ You are operating with a persistent file-based task tracking system located at \ 5. **VERIFICATION**: Before marking a task as complete, verify the work is actually done (e.g., run the test, check the file existence). 6. **STATE OVER CHAT**: If the user says "I think we finished that," but the tool says it is 'pending', trust the tool--or verify explicitly before updating. 7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph. +8. **DETAILED TASKS**: Ensure that the tasks created have highly detailed titles and descriptions. The description MUST provide significantly more specific details and technical context than the title. # Operational Guidelines @@ -3087,6 +3088,7 @@ You are operating with a persistent file-based task tracking system located at \ 5. **VERIFICATION**: Before marking a task as complete, verify the work is actually done (e.g., run the test, check the file existence). 6. **STATE OVER CHAT**: If the user says "I think we finished that," but the tool says it is 'pending', trust the tool--or verify explicitly before updating. 7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph. +8. **DETAILED TASKS**: Ensure that the tasks created have highly detailed titles and descriptions. The description MUST provide significantly more specific details and technical context than the title. # Operational Guidelines diff --git a/packages/core/src/prompts/snippets.legacy.ts b/packages/core/src/prompts/snippets.legacy.ts index 0367596c69..5b97886046 100644 --- a/packages/core/src/prompts/snippets.legacy.ts +++ b/packages/core/src/prompts/snippets.legacy.ts @@ -502,7 +502,8 @@ You are operating with a persistent file-based task tracking system located at \ 4. **PLAN MODE INTEGRATION**: If an approved plan exists, you MUST use the \`${TRACKER_CREATE_TASK_TOOL_NAME}\` tool to decompose it into discrete tasks before writing any code. Maintain a bidirectional understanding between the plan document and the task graph. 5. **VERIFICATION**: Before marking a task as complete, verify the work is actually done (e.g., run the test, check the file existence). 6. **STATE OVER CHAT**: If the user says "I think we finished that," but the tool says it is 'pending', trust the tool--or verify explicitly before updating. -7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph.`.trim(); +7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph. +8. **DETAILED TASKS**: Ensure that the tasks created have highly detailed titles and descriptions. The description MUST provide significantly more specific details and technical context than the title.`.trim(); } // --- Leaf Helpers (Strictly strings or simple calls) --- diff --git a/packages/core/src/prompts/snippets.ts b/packages/core/src/prompts/snippets.ts index b71fca746d..77e397d5ca 100644 --- a/packages/core/src/prompts/snippets.ts +++ b/packages/core/src/prompts/snippets.ts @@ -552,7 +552,8 @@ You are operating with a persistent file-based task tracking system located at \ 4. **PLAN MODE INTEGRATION**: If an approved plan exists, you MUST use the ${trackerCreate} tool to decompose it into discrete tasks before writing any code. Maintain a bidirectional understanding between the plan document and the task graph. 5. **VERIFICATION**: Before marking a task as complete, verify the work is actually done (e.g., run the test, check the file existence). 6. **STATE OVER CHAT**: If the user says "I think we finished that," but the tool says it is 'pending', trust the tool--or verify explicitly before updating. -7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph.`.trim(); +7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph. +8. **DETAILED TASKS**: Ensure that the tasks created have highly detailed titles and descriptions. The description MUST provide significantly more specific details and technical context than the title.`.trim(); } export function renderPlanningWorkflow( diff --git a/packages/core/src/tools/definitions/trackerTools.ts b/packages/core/src/tools/definitions/trackerTools.ts index e136d90d04..f48be8fe46 100644 --- a/packages/core/src/tools/definitions/trackerTools.ts +++ b/packages/core/src/tools/definitions/trackerTools.ts @@ -23,11 +23,13 @@ export const TRACKER_CREATE_TASK_DEFINITION: ToolDefinition = { properties: { title: { type: 'string', - description: 'Short title of the task.', + description: + 'Detailed title of the task. Should be concise but provide enough detail to understand the objective.', }, description: { type: 'string', - description: 'Detailed description of the task.', + description: + 'Detailed description of the task. Must contain more specific details and context than the title.', }, type: { type: 'string', @@ -66,7 +68,7 @@ export const TRACKER_UPDATE_TASK_DEFINITION: ToolDefinition = { }, description: { type: 'string', - description: 'New description for the task.', + description: 'New detailed description for the task.', }, status: { type: 'string',