update_task
Modify and refine task details, dependencies, priorities, and statuses for precise project management. Update task hierarchy, time tracking, tags, and more to maintain accurate workflow organization.
Instructions
Adapt and refine tasks with comprehensive updates including dependencies, priorities, complexity, status, tags, and time tracking. Keep your workflow current and accurate with advanced project management capabilities including unlimited hierarchy movement.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| actualHours | No | Actual time spent on the task in hours | |
| completed | No | Mark task as completed (true) or incomplete (false) (optional) | |
| complexity | No | Updated complexity/effort estimate (1-10, where 10 is most complex) | |
| dependsOn | No | Updated array of task IDs that must be completed before this task | |
| details | No | New detailed description for the task (optional) | |
| estimatedHours | No | Updated estimated time to complete in hours | |
| id | Yes | The unique identifier of the task to update | |
| name | No | New name/title for the task (optional) | |
| parentId | No | Updated parent task ID for moving between hierarchy levels (optional - use null/empty to move to top level) | |
| priority | No | Updated task priority level (1-10, where 10 is highest priority) | |
| status | No | Updated task status | |
| tags | No | Updated tags for categorization and filtering | |
| 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. |