update_subtask
Modify subtask details, including name, description, and completion status, ensuring accurate and up-to-date project records. Ideal for refining requirements and tracking progress in real-time.
Instructions
Fine-tune subtask specifications and track completion progress with flexible updates to names, descriptions, and status. Maintain accurate, up-to-date work records that reflect evolving requirements and real-time progress in your detailed project execution.
Input Schema
Name | Required | Description | Default |
---|---|---|---|
completed | No | Mark subtask as completed (true) or incomplete (false) (optional) | |
details | No | New detailed description for the subtask (optional) | |
id | Yes | The unique identifier of the subtask to update | |
name | No | New name/title for the subtask (optional) | |
workingDirectory | Yes | The full absolute path to the working directory where data is stored. MUST be an absolute path, never relative. Windows: "C:\Users\username\project" or "D:\projects\my-app". Unix/Linux/macOS: "/home/username/project" or "/Users/username/project". Do NOT use: ".", "..", "~", "./folder", "../folder" or any relative paths. Ensure the path exists and is accessible before calling this tool. NOTE: When server is started with --claude flag, this parameter is ignored and a global user directory is used instead. |
Input Schema (JSON Schema)
{
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false,
"properties": {
"completed": {
"description": "Mark subtask as completed (true) or incomplete (false) (optional)",
"type": "boolean"
},
"details": {
"description": "New detailed description for the subtask (optional)",
"type": "string"
},
"id": {
"description": "The unique identifier of the subtask to update",
"type": "string"
},
"name": {
"description": "New name/title for the subtask (optional)",
"type": "string"
},
"workingDirectory": {
"description": "The full absolute path to the working directory where data is stored. MUST be an absolute path, never relative. Windows: \"C:\\Users\\username\\project\" or \"D:\\projects\\my-app\". Unix/Linux/macOS: \"/home/username/project\" or \"/Users/username/project\". Do NOT use: \".\", \"..\", \"~\", \"./folder\", \"../folder\" or any relative paths. Ensure the path exists and is accessible before calling this tool. NOTE: When server is started with --claude flag, this parameter is ignored and a global user directory is used instead.",
"type": "string"
}
},
"required": [
"workingDirectory",
"id"
],
"type": "object"
}