create_task
Generate actionable and trackable tasks with dependencies, priorities, and complexity estimation. Organize workflows by breaking projects into a structured hierarchy for efficient management.
Instructions
Transform project goals into actionable, trackable tasks with advanced features including dependencies, priorities, complexity estimation, and workflow management. Build structured workflows that break down complex projects into manageable components with unlimited hierarchy depth.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| complexity | No | Estimated complexity/effort (1-10, where 10 is most complex) | |
| dependsOn | No | Array of task IDs that must be completed before this task | |
| details | Yes | Detailed description of what the task involves | |
| estimatedHours | No | Estimated time to complete in hours | |
| name | Yes | The name/title of the new task | |
| parentId | No | Parent task ID for unlimited nesting (optional - creates top-level task if not specified) | |
| priority | No | Task priority level (1-10, where 10 is highest priority) | |
| projectId | Yes | The ID of the project this task belongs to | |
| status | No | Initial task status (defaults to pending) | |
| tags | No | 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. |