diff --git a/assets/rules/dev_workflow.mdc b/assets/rules/dev_workflow.mdc index 003251d8..439fe993 100644 --- a/assets/rules/dev_workflow.mdc +++ b/assets/rules/dev_workflow.mdc @@ -49,11 +49,12 @@ Task Master offers two primary ways to interact: - Maintain valid dependency structure with `add_dependency`/`remove_dependency` tools or `task-master add-dependency`/`remove-dependency` commands, `validate_dependencies` / `task-master validate-dependencies`, and `fix_dependencies` / `task-master fix-dependencies` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) when needed - Respect dependency chains and task priorities when selecting work - Report progress regularly using `get_tasks` / `task-master list` +- Reorganize tasks as needed using `move_task` / `task-master move --from= --to=` (see @`taskmaster.mdc`) toarchy or ordering ## Task Complexity Analysis -- Run `analyze_project_complexity` / `task-master analyze-complexity --research` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) for comprehensive analysis -- Review complexity report via `complexity_report` / `task-master complexity-report` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) for a formatted, readable version. +- Run `analyze_project_complexity` / `task-master analyze-complexity --taskmaster.mdc`) for comprehensive analysis +- Review complexity report via `complexity_report` / `task-master complexity-report` (see @`taskmaster.mdc`) for a formatted, readable version. - Focus on tasks with highest complexity scores (8-10) for detailed breakdown - Use analysis results to determine appropriate subtask allocation - Note that reports are automatically used by the `expand_task` tool/command @@ -154,12 +155,30 @@ Taskmaster configuration is managed through two main mechanisms: - Task files are automatically regenerated after dependency changes - Dependencies are visualized with status indicators in task listings and files +## Task Reorganization + +- Use `move_task` / `task-master move --from= --to=` to move tasks or subtasks within the hierand supports several use cases: + - Moving a standalone task to become a subtask (e.g., `--from=5 --to=7`) + - Moving a subtask to become a standalone task (e.g., `--from=5.2 --to=7`) + - Moving a subtask to a different parent (e.g., `--from=5.2 --to=7.3`) + - Reordering subtasks within the same parent (e.g., `--from=5.2 --to=5.4`) + - Moving a task to a new, non-existent ID position (e.g., `--from=5 --to=25`) + - Moving multiple tasks at once using comma-separated IDs (e.g., `--from=10,11,12 --to=16,17,18`) +- The system includes validation to prevent data loss: + - Allows moving to non-existent IDs by creating placeholder tasks + - Prevents moving to existing task IDs that have content (to avoid overwriting) + - Validates source tasks exist before attempting to move them +- The system maintains proper parent-child relationships and dependency integrity +- Task files are automatically regenerated after the move operation +- This provides greater flexibility in organizing and refining your task structure as project understanding evolves +- This is especially useful when dealing with potential merge conflicts arising from teams creating tasks on separate branches. Solve these conflicts very easily by moving your tasks and keeping theirs. + ## Iterative Subtask Implementation Once a task has been broken down into subtasks using `expand_task` or similar methods, follow this iterative process for implementation: 1. **Understand the Goal (Preparation):** - * Use `get_task` / `task-master show ` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to thoroughly understand the specific goals and requirements of the subtask. + * Use `get_task` / `task-master show ` (see @`taskmaster.mdc`) to thoroughly understand the specific goals and requirements of the subtask. 2. **Initial Exploration & Planning (Iteration 1):** * This is the first attempt at creating a concrete implementation plan. diff --git a/assets/rules/taskmaster.mdc b/assets/rules/taskmaster.mdc index 52a52e70..5391035a 100644 --- a/assets/rules/taskmaster.mdc +++ b/assets/rules/taskmaster.mdc @@ -290,11 +290,36 @@ This document provides a detailed reference for interacting with Taskmaster, cov * `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file `) * **Usage:** Delete unnecessary subtasks or promote a subtask to a top-level task. +### 17. Move Task (`move_task`) + +* **MCP Tool:** `move_task` +* **CLI Command:** `task-master move [options]` +* **Description:** `Move a task or subtask to a new position within the task hierarchy.` +* **Key Parameters/Options:** + * `from`: `Required. ID of the task/subtask to move (e.g., "5" or "5.2"). Can be comma-separated for multiple tasks.` (CLI: `--from `) + * `to`: `Required. ID of the destination (e.g., "7" or "7.3"). Must match the number of source IDs if comma-separated.` (CLI: `--to `) + * `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file `) +* **Usage:** Reorganize tasks by moving them within the hierarchy. Supports various scenarios like: + * Moving a task to become a subtask + * Moving a subtask to become a standalone task + * Moving a subtask to a different parent + * Reordering subtasks within the same parent + * Moving a task to a new, non-existent ID (automatically creates placeholders) + * Moving multiple tasks at once with comma-separated IDs +* **Validation Features:** + * Allows moving tasks to non-existent destination IDs (creates placeholder tasks) + * Prevents moving to existing task IDs that already have content (to avoid overwriting) + * Validates that source tasks exist before attempting to move them + * Maintains proper parent-child relationships +* **Example CLI:** `task-master move --from=5.2 --to=7.3` to move subtask 5.2 to become subtask 7.3. +* **Example Multi-Move:** `task-master move --from=10,11,12 --to=16,17,18` to move multiple tasks to new positions. +* **Common Use:** Resolving merge conflicts in tasks.json when multiple team members create tasks on different branches. + --- ## Dependency Management -### 17. Add Dependency (`add_dependency`) +### 18. Add Dependency (`add_dependency`) * **MCP Tool:** `add_dependency` * **CLI Command:** `task-master add-dependency [options]` @@ -305,7 +330,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov * `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file `) * **Usage:** Establish the correct order of execution between tasks. -### 18. Remove Dependency (`remove_dependency`) +### 19. Remove Dependency (`remove_dependency`) * **MCP Tool:** `remove_dependency` * **CLI Command:** `task-master remove-dependency [options]` @@ -316,7 +341,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov * `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file `) * **Usage:** Update task relationships when the order of execution changes. -### 19. Validate Dependencies (`validate_dependencies`) +### 20. Validate Dependencies (`validate_dependencies`) * **MCP Tool:** `validate_dependencies` * **CLI Command:** `task-master validate-dependencies [options]` @@ -325,7 +350,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov * `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file `) * **Usage:** Audit the integrity of your task dependencies. -### 20. Fix Dependencies (`fix_dependencies`) +### 21. Fix Dependencies (`fix_dependencies`) * **MCP Tool:** `fix_dependencies` * **CLI Command:** `task-master fix-dependencies [options]` @@ -338,7 +363,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov ## Analysis & Reporting -### 21. Analyze Project Complexity (`analyze_project_complexity`) +### 22. Analyze Project Complexity (`analyze_project_complexity`) * **MCP Tool:** `analyze_project_complexity` * **CLI Command:** `task-master analyze-complexity [options]` @@ -351,7 +376,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov * **Usage:** Used before breaking down tasks to identify which ones need the most attention. * **Important:** This MCP tool makes AI calls and can take up to a minute to complete. Please inform users to hang tight while the operation is in progress. -### 22. View Complexity Report (`complexity_report`) +### 23. View Complexity Report (`complexity_report`) * **MCP Tool:** `complexity_report` * **CLI Command:** `task-master complexity-report [options]` @@ -364,12 +389,11 @@ This document provides a detailed reference for interacting with Taskmaster, cov ## File Management -### 23. Generate Task Files (`generate`) +### 24. Generate Task Files (`generate`) * **MCP Tool:** `generate` * **CLI Command:** `task-master generate [options]` -* **Description:** `Create or update individual Markdown files for each task based on your tasks.json.` -* **Key Parameters/Options:** +* **Description:** `Create or update individual Markdown files for each task * **Key Parameters/Options:** * `output`: `The directory where Taskmaster should save the task files (default: in a 'tasks' directory).` (CLI: `-o, --output `) * `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file `) * **Usage:** Run this after making changes to tasks.json to keep individual task files up to date. @@ -400,4 +424,4 @@ Environment variables are used **only** for sensitive API keys related to AI pro --- -For details on how these commands fit into the development process, see the [Development Workflow Guide](mdc:.cursor/rules/dev_workflow.mdc). +For details on how these commands fit into the development process, see the @Development Workflow Guide.