From 8d9fcf2064d8a917ba4fbfdf996b0d7be11be941 Mon Sep 17 00:00:00 2001 From: Ofer Shaal Date: Tue, 1 Jul 2025 05:44:44 -0400 Subject: [PATCH] Fix/spelling mistakes (#876) * docs: Auto-update and format models.md * fix: correct typos in documentation for parse-prd and taskmaster commands - Updated the `parse-prd` documentation to fix the spelling of "multiple." - Clarified the description of the `id` parameter in the `taskmaster` documentation to ensure proper syntax and readability. --------- Co-authored-by: github-actions[bot] --- .cursor/rules/dev_workflow.mdc | 2 +- .cursor/rules/taskmaster.mdc | 2 +- assets/rules/dev_workflow.mdc | 2 +- assets/rules/taskmaster.mdc | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.cursor/rules/dev_workflow.mdc b/.cursor/rules/dev_workflow.mdc index 741b1ade..ec2b326b 100644 --- a/.cursor/rules/dev_workflow.mdc +++ b/.cursor/rules/dev_workflow.mdc @@ -153,7 +153,7 @@ When users initialize Taskmaster on existing projects: 4. **Tag-Based Organization**: Parse PRDs into appropriate tags (`refactor-api`, `feature-dashboard`, `tech-debt`, etc.) 5. **Master List Curation**: Keep only the most valuable initiatives in master -The parse-prd's `--append` flag enables the user to parse multple PRDs within tags or across tags. PRDs should be focused and the number of tasks they are parsed into should be strategically chosen relative to the PRD's complexity and level of detail. +The parse-prd's `--append` flag enables the user to parse multiple PRDs within tags or across tags. PRDs should be focused and the number of tasks they are parsed into should be strategically chosen relative to the PRD's complexity and level of detail. ### Workflow Transition Examples diff --git a/.cursor/rules/taskmaster.mdc b/.cursor/rules/taskmaster.mdc index 44a8b349..3fc236f3 100644 --- a/.cursor/rules/taskmaster.mdc +++ b/.cursor/rules/taskmaster.mdc @@ -272,7 +272,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov * **CLI Command:** `task-master clear-subtasks [options]` * **Description:** `Remove all subtasks from one or more specified Taskmaster parent tasks.` * **Key Parameters/Options:** - * `id`: `The ID(s) of the Taskmaster parent task(s) whose subtasks you want to remove, e.g., '15' or '16,18'. Required unless using `all`.) (CLI: `-i, --id `) + * `id`: `The ID(s) of the Taskmaster parent task(s) whose subtasks you want to remove, e.g., '15' or '16,18'. Required unless using 'all'.` (CLI: `-i, --id `) * `all`: `Tell Taskmaster to remove subtasks from all parent tasks.` (CLI: `--all`) * `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag `) * `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file `) diff --git a/assets/rules/dev_workflow.mdc b/assets/rules/dev_workflow.mdc index ae6ceeee..84dd906f 100644 --- a/assets/rules/dev_workflow.mdc +++ b/assets/rules/dev_workflow.mdc @@ -153,7 +153,7 @@ When users initialize Taskmaster on existing projects: 4. **Tag-Based Organization**: Parse PRDs into appropriate tags (`refactor-api`, `feature-dashboard`, `tech-debt`, etc.) 5. **Master List Curation**: Keep only the most valuable initiatives in master -The parse-prd's `--append` flag enables the user to parse multple PRDs within tags or across tags. PRDs should be focused and the number of tasks they are parsed into should be strategically chosen relative to the PRD's complexity and level of detail. +The parse-prd's `--append` flag enables the user to parse multiple PRDs within tags or across tags. PRDs should be focused and the number of tasks they are parsed into should be strategically chosen relative to the PRD's complexity and level of detail. ### Workflow Transition Examples diff --git a/assets/rules/taskmaster.mdc b/assets/rules/taskmaster.mdc index b69aa9b0..892d7274 100644 --- a/assets/rules/taskmaster.mdc +++ b/assets/rules/taskmaster.mdc @@ -271,7 +271,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov * **CLI Command:** `task-master clear-subtasks [options]` * **Description:** `Remove all subtasks from one or more specified Taskmaster parent tasks.` * **Key Parameters/Options:** - * `id`: `The ID(s) of the Taskmaster parent task(s) whose subtasks you want to remove, e.g., '15' or '16,18'. Required unless using `all`.) (CLI: `-i, --id `) + * `id`: `The ID(s) of the Taskmaster parent task(s) whose subtasks you want to remove, e.g., '15' or '16,18'. Required unless using 'all'.` (CLI: `-i, --id `) * `all`: `Tell Taskmaster to remove subtasks from all parent tasks.` (CLI: `--all`) * `tag`: `Specify which tag context to operate on. Defaults to the current active tag.` (CLI: `--tag `) * `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file `)