|
|
|
|
@@ -11,7 +11,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
|
|
|
|
|
**Important:** Several MCP tools involve AI processing... The AI-powered tools include `parse_prd`, `analyze_project_complexity`, `update_subtask`, `update_task`, `update`, `expand_all`, `expand_task`, and `add_task`.
|
|
|
|
|
|
|
|
|
|
**Tagged Task Lists System:** Task Master now supports tagged task lists for multi-context task management. Existing projects automatically migrate to use a "master" tag with zero disruption. All commands continue to work unchanged while providing the foundation for enhanced multi-context workflows. MCP tools will be updated for full tagged support in Part 2 of the implementation.
|
|
|
|
|
**🏷️ Tagged Task Lists System:** Task Master now supports **tagged task lists** for multi-context task management. This allows you to maintain separate, isolated lists of tasks for different features, branches, or experiments. Existing projects are seamlessly migrated to use a default "master" tag. Most commands now support a `--tag <name>` flag to specify which context to operate on. If omitted, commands use the currently active tag.
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
@@ -39,6 +39,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
* `yes`: `Skip prompts and use defaults/provided arguments. Default is false.` (CLI: `-y, --yes`)
|
|
|
|
|
* **Usage:** Run this once at the beginning of a new project, typically via an integrated tool like Cursor. Operates on the current working directory of the MCP server.
|
|
|
|
|
* **Important:** Once complete, you *MUST* parse a prd in order to generate tasks. There will be no tasks files until then. The next step after initializing should be to create a PRD using the example PRD in .taskmaster/templates/example_prd.txt.
|
|
|
|
|
* **Tagging:** Use the `--tag` option to parse the PRD into a specific, non-default tag context. If the tag doesn't exist, it will be created automatically. Example: `task-master parse-prd spec.txt --tag=new-feature`.
|
|
|
|
|
|
|
|
|
|
### 2. Parse PRD (`parse_prd`)
|
|
|
|
|
|
|
|
|
|
@@ -94,8 +95,9 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
* **CLI Command:** `task-master list [options]`
|
|
|
|
|
* **Description:** `List your Taskmaster tasks, optionally filtering by status and showing subtasks.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `status`: `Show only Taskmaster tasks matching this status, e.g., 'pending' or 'done'.` (CLI: `-s, --status <status>`)
|
|
|
|
|
* `status`: `Show only Taskmaster tasks matching this status (or multiple statuses, comma-separated), e.g., 'pending' or 'done,in-progress'.` (CLI: `-s, --status <status>`)
|
|
|
|
|
* `withSubtasks`: `Include subtasks indented under their parent tasks in the list.` (CLI: `--with-subtasks`)
|
|
|
|
|
* `tag`: `Specify which tag context to list tasks from. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
|
|
|
|
|
* **Usage:** Get an overview of the project status, often used at the start of a work session.
|
|
|
|
|
|
|
|
|
|
@@ -112,11 +114,12 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** `get_task`
|
|
|
|
|
* **CLI Command:** `task-master show [id] [options]`
|
|
|
|
|
* **Description:** `Display detailed information for a specific Taskmaster task or subtask by its ID.`
|
|
|
|
|
* **Description:** `Display detailed information for one or more specific Taskmaster tasks or subtasks by ID.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `id`: `Required. The ID of the Taskmaster task, e.g., '15', or subtask, e.g., '15.2', you want to view.` (CLI: `[id]. Supports comma-separated list of tasks to get multiple tasks at once.` positional or `-i, --id <id>`)
|
|
|
|
|
* `id`: `Required. The ID of the Taskmaster task (e.g., '15'), subtask (e.g., '15.2'), or a comma-separated list of IDs ('1,5,10.2') you want to view.` (CLI: `[id]` positional or `-i, --id <id>`)
|
|
|
|
|
* `tag`: `Specify which tag context to get the task(s) from. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
|
|
|
|
|
* **Usage:** Understand the full details, implementation notes, and test strategy for a specific task before starting work.
|
|
|
|
|
* **Usage:** Understand the full details for a specific task. When multiple IDs are provided, a summary table is shown.
|
|
|
|
|
* **CRITICAL INFORMATION** If you need to collect information from multiple tasks, use comma-separated IDs (i.e. 1,2,3) to receive an array of tasks. Do not needlessly get tasks one at a time if you need to get many as that is wasteful.
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
@@ -171,13 +174,15 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** `update_task`
|
|
|
|
|
* **CLI Command:** `task-master update-task [options]`
|
|
|
|
|
* **Description:** `Modify a specific Taskmaster task or subtask by its ID, incorporating new information or changes.`
|
|
|
|
|
* **Description:** `Modify a specific Taskmaster task by ID, incorporating new information or changes. By default, this replaces the existing task details.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `id`: `Required. The specific ID of the Taskmaster task, e.g., '15', or subtask, e.g., '15.2', you want to update.` (CLI: `-i, --id <id>`)
|
|
|
|
|
* `id`: `Required. The specific ID of the Taskmaster task, e.g., '15', you want to update.` (CLI: `-i, --id <id>`)
|
|
|
|
|
* `prompt`: `Required. Explain the specific changes or provide the new information Taskmaster should incorporate into this task.` (CLI: `-p, --prompt <text>`)
|
|
|
|
|
* `append`: `If true, appends the prompt content to the task's details with a timestamp, rather than replacing them. Behaves like update-subtask.` (CLI: `--append`)
|
|
|
|
|
* `research`: `Enable Taskmaster to use the research role for more informed updates. Requires appropriate API key.` (CLI: `-r, --research`)
|
|
|
|
|
* `tag`: `Specify which tag context the task belongs to. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
|
|
|
|
|
* **Usage:** Refine a specific task based on new understanding or feedback. Example CLI: `task-master update-task --id='15' --prompt='Clarification: Use PostgreSQL instead of MySQL.\nUpdate schema details...'`
|
|
|
|
|
* **Usage:** Refine a specific task based on new understanding. Use `--append` to log progress without creating subtasks.
|
|
|
|
|
* **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.
|
|
|
|
|
|
|
|
|
|
### 10. Update Subtask (`update_subtask`)
|
|
|
|
|
@@ -186,12 +191,12 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
* **CLI Command:** `task-master update-subtask [options]`
|
|
|
|
|
* **Description:** `Append timestamped notes or details to a specific Taskmaster subtask without overwriting existing content. Intended for iterative implementation logging.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `id`: `Required. The specific ID of the Taskmaster subtask, e.g., '15.2', you want to add information to.` (CLI: `-i, --id <id>`)
|
|
|
|
|
* `prompt`: `Required. Provide the information or notes Taskmaster should append to the subtask's details. Ensure this adds *new* information not already present.` (CLI: `-p, --prompt <text>`)
|
|
|
|
|
* `research`: `Enable Taskmaster to use the research role for more informed updates. Requires appropriate API key.` (CLI: `-r, --research`)
|
|
|
|
|
* `id`: `Required. The ID of the Taskmaster task, e.g., '5', or subtask, e.g., '5.2', to permanently remove.` (CLI: `-i, --id <id>`)
|
|
|
|
|
* `yes`: `Skip the confirmation prompt and immediately delete the task.` (CLI: `-y, --yes`)
|
|
|
|
|
* `tag`: `Specify which tag context to remove the task from. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
|
|
|
|
|
* **Usage:** Add implementation notes, code snippets, or clarifications to a subtask during development. Before calling, review the subtask's current details to append only fresh insights, helping to build a detailed log of the implementation journey and avoid redundancy. Example CLI: `task-master update-subtask --id='15.2' --prompt='Discovered that the API requires header X.\nImplementation needs adjustment...'`
|
|
|
|
|
* **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.
|
|
|
|
|
* **Usage:** Permanently delete tasks or subtasks that are no longer needed in the project.
|
|
|
|
|
* **Notes:** Use with caution as this operation cannot be undone. Consider using 'blocked', 'cancelled', or 'deferred' status instead if you just want to exclude a task from active planning but keep it for reference. The command automatically cleans up dependency references in other tasks.
|
|
|
|
|
|
|
|
|
|
### 11. Set Task Status (`set_task_status`)
|
|
|
|
|
|
|
|
|
|
@@ -231,6 +236,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
* `research`: `Enable Taskmaster to use the research role for more informed subtask generation. Requires appropriate API key.` (CLI: `-r, --research`)
|
|
|
|
|
* `prompt`: `Optional: Provide extra context or specific instructions to Taskmaster for generating the subtasks.` (CLI: `-p, --prompt <text>`)
|
|
|
|
|
* `force`: `Optional: If true, clear existing subtasks before generating new ones. Default is false (append).` (CLI: `--force`)
|
|
|
|
|
* `tag`: `Specify which tag context the task belongs to. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
|
|
|
|
|
* **Usage:** Generate a detailed implementation plan for a complex task before starting coding. Automatically uses complexity report recommendations if available and `num` is not specified.
|
|
|
|
|
* **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.
|
|
|
|
|
@@ -245,6 +251,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
* `research`: `Enable research role for more informed subtask generation. Requires appropriate API key.` (CLI: `-r, --research`)
|
|
|
|
|
* `prompt`: `Optional: Provide extra context for Taskmaster to apply generally during expansion.` (CLI: `-p, --prompt <text>`)
|
|
|
|
|
* `force`: `Optional: If true, clear existing subtasks before generating new ones for each eligible task. Default is false (append).` (CLI: `--force`)
|
|
|
|
|
* `tag`: `Specify which tag context to expand. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
|
|
|
|
|
* **Usage:** Useful after initial task generation or complexity analysis to break down multiple tasks at once.
|
|
|
|
|
* **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.
|
|
|
|
|
@@ -338,6 +345,7 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
* **CLI Command:** `task-master fix-dependencies [options]`
|
|
|
|
|
* **Description:** `Automatically fix dependency issues (like circular references or links to non-existent tasks) in your Taskmaster tasks.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `tag`: `Specify which tag context to fix dependencies in. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
|
|
|
|
|
* **Usage:** Clean up dependency errors automatically.
|
|
|
|
|
|
|
|
|
|
@@ -351,9 +359,10 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
* **CLI Command:** `task-master analyze-complexity [options]`
|
|
|
|
|
* **Description:** `Have Taskmaster analyze your tasks to determine their complexity and suggest which ones need to be broken down further.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `output`: `Where to save the complexity analysis report (default: '.taskmaster/reports/task-complexity-report.json').` (CLI: `-o, --output <file>`)
|
|
|
|
|
* `output`: `Where to save the complexity analysis report. Default is '.taskmaster/reports/task-complexity-report.json' (or '..._tagname.json' if a tag is used).` (CLI: `-o, --output <file>`)
|
|
|
|
|
* `threshold`: `The minimum complexity score (1-10) that should trigger a recommendation to expand a task.` (CLI: `-t, --threshold <number>`)
|
|
|
|
|
* `research`: `Enable research role for more accurate complexity analysis. Requires appropriate API key.` (CLI: `-r, --research`)
|
|
|
|
|
* `tag`: `Specify which tag context to analyze. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `file`: `Path to your Taskmaster 'tasks.json' file. Default relies on auto-detection.` (CLI: `-f, --file <file>`)
|
|
|
|
|
* **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.
|
|
|
|
|
@@ -369,6 +378,21 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## File Management
|
|
|
|
|
|
|
|
|
|
### 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:**
|
|
|
|
|
* `output`: `The directory where Taskmaster should save the task files (default: in a 'tasks' directory).` (CLI: `-o, --output <directory>`)
|
|
|
|
|
* `tag`: `Specify which tag context to generate files for. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `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. This command is now manual and no longer runs automatically.
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## AI-Powered Research
|
|
|
|
|
|
|
|
|
|
### 25. Research (`research`)
|
|
|
|
|
@@ -378,11 +402,15 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
* **Description:** `Perform AI-powered research queries with project context to get fresh, up-to-date information beyond the AI's knowledge cutoff.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `query`: `Required. Research query/prompt (e.g., "What are the latest best practices for React Query v5?").` (CLI: `[query]` positional or `-q, --query <text>`)
|
|
|
|
|
* `taskIds`: `Comma-separated list of task/subtask IDs for context (e.g., "15,16.2,17").` (CLI: `-i, --id <ids>`)
|
|
|
|
|
* `taskIds`: `Comma-separated list of task/subtask IDs from the current tag context (e.g., "15,16.2,17").` (CLI: `-i, --id <ids>`)
|
|
|
|
|
* `filePaths`: `Comma-separated list of file paths for context (e.g., "src/api.js,docs/readme.md").` (CLI: `-f, --files <paths>`)
|
|
|
|
|
* `customContext`: `Additional custom context text to include in the research.` (CLI: `-c, --context <text>`)
|
|
|
|
|
* `includeProjectTree`: `Include project file tree structure in context (default: false).` (CLI: `--tree`)
|
|
|
|
|
* `detailLevel`: `Detail level for the research response: 'low', 'medium', 'high' (default: medium).` (CLI: `--detail <level>`)
|
|
|
|
|
* `saveTo`: `Task or subtask ID (e.g., "15", "15.2") to automatically save the research conversation to.` (CLI: `--save-to <id>`)
|
|
|
|
|
* `saveFile`: `If true, saves the research conversation to a markdown file in '.taskmaster/docs/research/'.` (CLI: `--save-file`)
|
|
|
|
|
* `noFollowup`: `Disables the interactive follow-up question menu in the CLI.` (CLI: `--no-followup`)
|
|
|
|
|
* `tag`: `Specify which tag context to use for task-based context gathering. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
* `projectRoot`: `The directory of the project. Must be an absolute path.` (CLI: Determined automatically)
|
|
|
|
|
* **Usage:** **This is a POWERFUL tool that agents should use FREQUENTLY** to:
|
|
|
|
|
* Get fresh information beyond knowledge cutoff dates
|
|
|
|
|
@@ -406,17 +434,79 @@ This document provides a detailed reference for interacting with Taskmaster, cov
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## File Management
|
|
|
|
|
## Tag Management
|
|
|
|
|
|
|
|
|
|
### 24. Generate Task Files (`generate`)
|
|
|
|
|
This new suite of commands allows you to manage different task contexts (tags).
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** `generate`
|
|
|
|
|
* **CLI Command:** `task-master generate [options]`
|
|
|
|
|
* **Description:** `Create or update individual Markdown files for each task based on your tasks.json.`
|
|
|
|
|
### 26. List Tags (`tags`)
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** `list_tags`
|
|
|
|
|
* **CLI Command:** `task-master tags [options]`
|
|
|
|
|
* **Description:** `List all available tags with task counts, completion status, and other metadata.`
|
|
|
|
|
* **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.
|
|
|
|
|
* `--show-metadata`: `Include detailed metadata in the output (e.g., creation date, description).` (CLI: `--show-metadata`)
|
|
|
|
|
|
|
|
|
|
### 27. Add Tag (`add_tag`)
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** `add_tag`
|
|
|
|
|
* **CLI Command:** `task-master add-tag <tagName> [options]`
|
|
|
|
|
* **Description:** `Create a new, empty tag context, or copy tasks from another tag.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `tagName`: `Name of the new tag to create (alphanumeric, hyphens, underscores).` (CLI: `<tagName>` positional)
|
|
|
|
|
* `--from-branch`: `Creates a tag with a name derived from the current git branch, ignoring the <tagName> argument.` (CLI: `--from-branch`)
|
|
|
|
|
* `--copy-from-current`: `Copy tasks from the currently active tag to the new tag.` (CLI: `--copy-from-current`)
|
|
|
|
|
* `--copy-from <tag>`: `Copy tasks from a specific source tag to the new tag.` (CLI: `--copy-from <tag>`)
|
|
|
|
|
* `--description <text>`: `Provide an optional description for the new tag.` (CLI: `-d, --description <text>`)
|
|
|
|
|
|
|
|
|
|
### 28. Delete Tag (`delete_tag`)
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** `delete_tag`
|
|
|
|
|
* **CLI Command:** `task-master delete-tag <tagName> [options]`
|
|
|
|
|
* **Description:** `Permanently delete a tag and all of its associated tasks.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `tagName`: `Name of the tag to delete.` (CLI: `<tagName>` positional)
|
|
|
|
|
* `--yes`: `Skip the confirmation prompt.` (CLI: `-y, --yes`)
|
|
|
|
|
|
|
|
|
|
### 29. Use Tag (`use_tag`)
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** `use_tag`
|
|
|
|
|
* **CLI Command:** `task-master use-tag <tagName>`
|
|
|
|
|
* **Description:** `Switch your active task context to a different tag.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `tagName`: `Name of the tag to switch to.` (CLI: `<tagName>` positional)
|
|
|
|
|
|
|
|
|
|
### 30. Rename Tag (`rename_tag`)
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** `rename_tag`
|
|
|
|
|
* **CLI Command:** `task-master rename-tag <oldName> <newName>`
|
|
|
|
|
* **Description:** `Rename an existing tag.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `oldName`: `The current name of the tag.` (CLI: `<oldName>` positional)
|
|
|
|
|
* `newName`: `The new name for the tag.` (CLI: `<newName>` positional)
|
|
|
|
|
|
|
|
|
|
### 31. Copy Tag (`copy_tag`)
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** `copy_tag`
|
|
|
|
|
* **CLI Command:** `task-master copy-tag <sourceName> <targetName> [options]`
|
|
|
|
|
* **Description:** `Copy an entire tag context, including all its tasks and metadata, to a new tag.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `sourceName`: `Name of the tag to copy from.` (CLI: `<sourceName>` positional)
|
|
|
|
|
* `targetName`: `Name of the new tag to create.` (CLI: `<targetName>` positional)
|
|
|
|
|
* `--description <text>`: `Optional description for the new tag.` (CLI: `-d, --description <text>`)
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## Miscellaneous
|
|
|
|
|
|
|
|
|
|
### 32. Sync Readme (`sync-readme`) -- experimental
|
|
|
|
|
|
|
|
|
|
* **MCP Tool:** N/A
|
|
|
|
|
* **CLI Command:** `task-master sync-readme [options]`
|
|
|
|
|
* **Description:** `Exports your task list to your project's README.md file, useful for showcasing progress.`
|
|
|
|
|
* **Key Parameters/Options:**
|
|
|
|
|
* `status`: `Filter tasks by status (e.g., 'pending', 'done').` (CLI: `-s, --status <status>`)
|
|
|
|
|
* `withSubtasks`: `Include subtasks in the export.` (CLI: `--with-subtasks`)
|
|
|
|
|
* `tag`: `Specify which tag context to export from. Defaults to the current active tag.` (CLI: `--tag <name>`)
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
Eyal Toledano