mcp-chain-of-thought

split_tasks

Decompose complex tasks into smaller, manageable subtasks with defined dependencies and priorities. Choose update modes like append, overwrite, selective, or clearAllTasks to maintain or reset task lists efficiently.

Instructions

Decompose complex tasks into independent subtasks, establishing dependencies and priorities.

updateMode

  • append: Keep existing tasks and add new ones
  • overwrite: Delete unfinished tasks, keep completed ones
  • selective: Intelligently match and update existing tasks based on name
  • clearAllTasks: Clear all tasks and create a backup (preferred mode)

Key Requirements

  • Provide concise pseudocode: Only provide high-level logic flow and key steps, avoid complete code
  • Consolidate when necessary: Simple modifications can be integrated with other tasks to avoid excessive task count
  • Submit in batches: If there are too many tasks, use the "split_tasks" tool with parameters not exceeding 5000 characters

Input Schema

NameRequiredDescriptionDefault
globalAnalysisResultNoGlobal analysis result: complete analysis result from reflect_task, applicable to the common parts of all tasks
tasksYesStructured task list, each task should be atomic and have a clear completion standard, avoid overly simple tasks, simple modifications can be integrated with other tasks, avoid too many tasks
updateModeYesTask update mode selection: 'append' (preserve all existing tasks and add new tasks), 'overwrite' (clear all unfinished tasks and completely replace, preserve completed tasks), 'selective' (intelligent update: match and update existing tasks by name, preserve tasks not in the list, recommended for minor task adjustments), 'clearAllTasks' (clear all tasks and create a backup). Default is 'clearAllTasks' mode, only use other modes when the user requests changes or modifications to the plan content

Input Schema (JSON Schema)

{ "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "globalAnalysisResult": { "description": "Global analysis result: complete analysis result from reflect_task, applicable to the common parts of all tasks", "type": "string" }, "tasks": { "description": "Structured task list, each task should be atomic and have a clear completion standard, avoid overly simple tasks, simple modifications can be integrated with other tasks, avoid too many tasks", "items": { "additionalProperties": false, "properties": { "dependencies": { "description": "List of previous task IDs or task names this task depends on, supports two referencing methods, name referencing is more intuitive, and is a string array", "items": { "type": "string" }, "type": "array" }, "description": { "description": "Detailed task description, including implementation points, technical details and acceptance standards", "minLength": 10, "type": "string" }, "implementationGuide": { "description": "Specific implementation method and steps for this task, please refer to previous analysis results and provide simplified pseudocode", "type": "string" }, "name": { "description": "Brief and clear task name, should be able to express the purpose of the task", "maxLength": 100, "type": "string" }, "notes": { "description": "Supplementary notes, special processing requirements or implementation suggestions (optional)", "type": "string" }, "relatedFiles": { "description": "List of files related to the task, used to record code files, reference materials, files to be created, etc. related to the task (optional)", "items": { "additionalProperties": false, "properties": { "description": { "description": "File description, used to explain the purpose and content of the file", "minLength": 1, "type": "string" }, "lineEnd": { "description": "Ending line of the relevant code block (optional)", "exclusiveMinimum": 0, "type": "integer" }, "lineStart": { "description": "Starting line of the relevant code block (optional)", "exclusiveMinimum": 0, "type": "integer" }, "path": { "description": "File path, can be a path relative to the project root directory or an absolute path", "minLength": 1, "type": "string" }, "type": { "description": "File type (TO_MODIFY: to be modified, REFERENCE: reference material, CREATE: to be created, DEPENDENCY: dependency file, OTHER: other)", "enum": [ "TO_MODIFY", "REFERENCE", "CREATE", "DEPENDENCY", "OTHER" ], "type": "string" } }, "required": [ "path", "type", "description" ], "type": "object" }, "type": "array" }, "verificationCriteria": { "description": "Verification criteria and inspection methods for this specific task", "type": "string" } }, "required": [ "name", "description", "implementationGuide" ], "type": "object" }, "minItems": 1, "type": "array" }, "updateMode": { "description": "Task update mode selection: 'append' (preserve all existing tasks and add new tasks), 'overwrite' (clear all unfinished tasks and completely replace, preserve completed tasks), 'selective' (intelligent update: match and update existing tasks by name, preserve tasks not in the list, recommended for minor task adjustments), 'clearAllTasks' (clear all tasks and create a backup).\nDefault is 'clearAllTasks' mode, only use other modes when the user requests changes or modifications to the plan content", "enum": [ "append", "overwrite", "selective", "clearAllTasks" ], "type": "string" } }, "required": [ "updateMode", "tasks" ], "type": "object" }

You must be authenticated.

Other Tools from mcp-chain-of-thought

Related Tools

ID: 4lvqqvtprl