bulk_task_operations

Execute multiple task operations atomically.

Performance Optimization:

Operations processed in dependency order
Single-operation batches for consistency
Full transaction rollback on failure
Retry mechanism: 3 retries, 1s delay

Validation:

All create/update constraints apply
Cross-operation dependency validation
Status transition rules enforced
Parent-child relationships validated
Metadata schema checked

Best Practices:

Group related operations
Order operations by dependencies
Include clear operation reasoning
Handle parent-child updates together
Consider status propagation effects

Operation Limits:

Path: max length 1000 chars, max depth 10
Notes: max 100 per category
Dependencies: max 50 per task
Metadata fields: max 100 entries each

Example: { "operations": [ { "type": "create", "path": "project/backend/oauth2", "data": { "title": "Implement OAuth2 Authentication", "type": "MILESTONE", "description": "Replace JWT auth with OAuth2 implementation", "planningNotes": [ "Research OAuth2 providers", "Define integration requirements" ], "metadata": { "reasoning": "OAuth2 provides better security and standardization" } } }, { "type": "create", "path": "project/backend/oauth2/provider-setup", "data": { "title": "Configure OAuth2 Providers", "dependencies": ["project/backend/oauth2"], "planningNotes": [ "List required OAuth2 providers", "Document configuration requirements" ], "metadata": { "reasoning": "Provider setup required before implementation" } } }, { "type": "update", "path": "project/backend/auth", "data": { "status": "CANCELLED", "completionNotes": [ "Functionality replaced by OAuth2 implementation" ], "metadata": { "reasoning": "Replaced by OAuth2 implementation" } } } ], "reasoning": "Transitioning authentication system to OAuth2. Creating necessary task structure and updating existing tasks to reflect the change." }

Input Schema

Name	Required	Description	Default
`operations`	Yes	Sequence of atomic task operations with validation: Operation Constraints: - Path: max length 1000 chars, max depth 10 levels - Dependencies: max 50 per task - Notes: max 100 per category, each max 1000 chars - Metadata fields: max 100 entries each Create Operations: - title: Task name (required, max 200 chars) - description: Task details (max 2000 chars) - type: TASK/MILESTONE - dependencies: Required tasks (max 50) - metadata: Task tracking fields: - priority: low/medium/high - tags: max 100 tags, each max 100 chars - reasoning: max 2000 chars - tools_used: max 100 entries - resources_accessed: max 100 entries - context_used: max 100 entries, each max 1000 chars - notes: Each category max 100 notes, each max 1000 chars Update Operations: - Same field constraints as create - Status changes validate dependencies - Parent-child relationships enforced - Metadata schema validated - Note limits enforced Delete Operations: - Cascades to all child tasks - Updates dependent references - Validates relationship integrity Execution: - Operations processed in dependency order - Full transaction rollback on failure - Retry mechanism: 3 retries, 1s delay - Atomic - all succeed or all fail
`reasoning`	No	Explanation for bulk operation. Best practices: - Document overall goal and rationale - Explain relationships between operations - Note impact on existing tasks and dependencies - Record migration details and backup locations - Include validation and testing strategy - Document rollback procedures if needed

Input Schema (JSON Schema)

{
  "properties": {
    "operations": {
      "description": "Sequence of atomic task operations with validation:\n\nOperation Constraints:\n- Path: max length 1000 chars, max depth 10 levels\n- Dependencies: max 50 per task\n- Notes: max 100 per category, each max 1000 chars\n- Metadata fields: max 100 entries each\n\nCreate Operations:\n- title: Task name (required, max 200 chars)\n- description: Task details (max 2000 chars)\n- type: TASK/MILESTONE\n- dependencies: Required tasks (max 50)\n- metadata: Task tracking fields:\n  - priority: low/medium/high\n  - tags: max 100 tags, each max 100 chars\n  - reasoning: max 2000 chars\n  - tools_used: max 100 entries\n  - resources_accessed: max 100 entries\n  - context_used: max 100 entries, each max 1000 chars\n- notes: Each category max 100 notes, each max 1000 chars\n\nUpdate Operations:\n- Same field constraints as create\n- Status changes validate dependencies\n- Parent-child relationships enforced\n- Metadata schema validated\n- Note limits enforced\n\nDelete Operations:\n- Cascades to all child tasks\n- Updates dependent references\n- Validates relationship integrity\n\nExecution:\n- Operations processed in dependency order\n- Full transaction rollback on failure\n- Retry mechanism: 3 retries, 1s delay\n- Atomic - all succeed or all fail",
      "items": {
        "properties": {
          "data": {
            "description": "Operation-specific data:\nCreate/Update fields:\n- title: Task name\n- description: Task details\n- type: TASK/MILESTONE\n- status: Task state\n- dependencies: Required tasks\n- planningNotes: Planning notes\n- progressNotes: Progress notes\n- completionNotes: Completion notes\n- troubleshootingNotes: Troubleshooting notes\n- metadata: Additional context\nDelete: No additional data needed",
            "type": "object"
          },
          "path": {
            "description": "Task path for operation:\n- Must be valid path format\n- Create: Sets new task location\n- Update: Identifies target task\n- Delete: Specifies task to remove",
            "type": "string"
          },
          "type": {
            "description": "Operation type:\n- create: Add new task with full context\n- update: Modify existing task properties\n- delete: Remove task and children",
            "enum": [
              "create",
              "update",
              "delete"
            ],
            "type": "string"
          }
        },
        "required": [
          "type",
          "path"
        ],
        "type": "object"
      },
      "type": "array"
    },
    "reasoning": {
      "description": "Explanation for bulk operation. Best practices:\n- Document overall goal and rationale\n- Explain relationships between operations\n- Note impact on existing tasks and dependencies\n- Record migration details and backup locations\n- Include validation and testing strategy\n- Document rollback procedures if needed",
      "type": "string"
    }
  },
  "required": [
    "operations"
  ],
  "type": "object"
}