From 0163b5b8f9ea99235c8bfd3443b1c9724815d5d8 Mon Sep 17 00:00:00 2001
From: Joe Danziger <joe@ticc.net>
Date: Mon, 26 May 2025 22:53:38 -0400
Subject: [PATCH] update rules

---
 assets/rules/dev_workflow.mdc | 7 ++++---
 assets/rules/taskmaster.mdc   | 3 ++-
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/assets/rules/dev_workflow.mdc b/assets/rules/dev_workflow.mdc
index 439fe993..249ae9a3 100644
--- a/assets/rules/dev_workflow.mdc
+++ b/assets/rules/dev_workflow.mdc
@@ -49,11 +49,11 @@ 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=<id> --to=<id>` (see @`taskmaster.mdc`) toarchy or ordering
+-   Reorganize tasks as needed using `move_task` / `task-master move --from=<id> --to=<id>` (see @`taskmaster.mdc`) to change task hierarchy or ordering
 
 ## Task Complexity Analysis
 
--   Run `analyze_project_complexity` / `task-master analyze-complexity --taskmaster.mdc`) for comprehensive analysis
+-   Run `analyze_project_complexity` / `task-master analyze-complexity --research` (see @`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
@@ -157,7 +157,8 @@ Taskmaster configuration is managed through two main mechanisms:
 
 ## Task Reorganization
 
-- Use `move_task` / `task-master move --from=<id> --to=<id>` to move tasks or subtasks within the hierand supports several use cases:
+- Use `move_task` / `task-master move --from=<id> --to=<id>` to move tasks or subtasks within the hierarchy
+- This command 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`)
diff --git a/assets/rules/taskmaster.mdc b/assets/rules/taskmaster.mdc
index 5391035a..00545a81 100644
--- a/assets/rules/taskmaster.mdc
+++ b/assets/rules/taskmaster.mdc
@@ -393,7 +393,8 @@ This document provides a detailed reference for interacting with Taskmaster, cov
 
 *   **MCP Tool:** `generate`
 *   **CLI Command:** `task-master generate [options]`
-*   **Description:** `Create or update individual Markdown files for each task *   **Key Parameters/Options:**
+*   **Description:** `Create or update individual Markdown files for each task based on your tasks.json.`
+*   **Key Parameters/Options:**
     *   `output`: `The directory where Taskmaster should save the task files (default: in a 'tasks' directory).` (CLI: `-o, --output <directory>`)
     *   `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
 *   **Usage:** Run this after making changes to tasks.json to keep individual task files up to date.