ros/claude-task-master
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
b9299c5af0dc2d946e9b436e94c9c01627378013
claude-task-master/.claude/commands/tm/remove-subtask/index.md
neno b9299c5af0 feat: Claude Code slash commands for Task Master (#774) 
* Fix Cursor deeplink installation with copy-paste instructions (#723)

* fix: expand-task (#755)

* docs: Update o3 model price (#751)

* docs: Auto-update and format models.md

* docs: Auto-update and format models.md

* feat: Add Claude Code task master commands

Adds Task Master slash commands for Claude Code under /project:tm/ namespace

---------

Co-authored-by: Joe Danziger <joe@ticc.net>
Co-authored-by: Ralph Khreish <35776126+Crunchyman-ralph@users.noreply.github.com>
Co-authored-by: Volodymyr Zahorniak <7808206+zahorniak@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: neno-is-ooo <204701868+neno-is-ooo@users.noreply.github.com>
2025-06-21 20:48:20 +02:00

1.8 KiB
Raw Blame History

Remove a subtask from its parent task.

Arguments: $ARGUMENTS

Parse subtask ID to remove, with option to convert to standalone task.

Removing Subtasks

Remove a subtask and optionally convert it back to a standalone task.

Argument Parsing

  • "remove subtask 5.1"
  • "delete 5.1"
  • "convert 5.1 to task" → remove and convert
  • "5.1 standalone" → convert to standalone

Execution Options

1. Delete Subtask

task-master remove-subtask --id=<parentId.subtaskId>

2. Convert to Standalone

task-master remove-subtask --id=<parentId.subtaskId> --convert

Pre-Removal Checks

  1. Validate Subtask

    • Verify subtask exists
    • Check completion status
    • Review dependencies

  2. Impact Analysis

    • Other subtasks that depend on it
    • Parent task implications
    • Data that will be lost

Removal Process

For Deletion:

  1. Confirm if subtask has work done
  2. Update parent task estimates
  3. Remove subtask and its data
  4. Clean up dependencies

For Conversion:

  1. Assign new standalone task ID
  2. Preserve all task data
  3. Update dependency references
  4. Maintain task history

Smart Features

  • Warn if subtask is in-progress
  • Show impact on parent task
  • Preserve important data
  • Update related estimates

Example Flows

/project:tm/remove-subtask 5.1
→ Warning: Subtask #5.1 is in-progress
→ This will delete all subtask data
→ Parent task #5 will be updated
Confirm deletion? (y/n)

/project:tm/remove-subtask 5.1 convert
→ Converting subtask #5.1 to standalone task #89
→ Preserved: All task data and history
→ Updated: 2 dependency references
→ New task #89 is now independent

Post-Removal

  • Update parent task status
  • Recalculate estimates
  • Show updated hierarchy
  • Suggest next actions