chore: remove pre-release CI for extension, too much work and doesn't make sense for us

* initial cutover

* update log to debug

* update tracker to pass units

* update test to match new base tracker format

* add streamTextService mocks

* remove unused imports

* Ensure the CLI waits for async main() completion

* refactor to reduce code duplication

* update comment

* reuse function

* ensure targetTag is defined in streaming mode

* avoid throwing inside process.exit spy

* check for null

* remove reference to generate

* fix formatting

* fix textStream assignment

* ensure no division by 0

* fix jest chalk mocks

* refactor for maintainability

* Improve bar chart calculation logic for consistent visual representation

* use custom streaming error types; fix mocks

* Update streamText extraction in parse-prd.js to match actual service response

* remove check - doesn't belong here

* update mocks

* remove streaming test that wasn't really doing anything

* add comment

* make parsing logic more DRY

* fix formatting

* Fix textStream extraction to match actual service response

* fix mock

* Add a cleanup method to ensure proper resource disposal and prevent memory leaks

* debounce progress updates to reduce UI flicker during rapid updates

* Implement timeout protection for streaming operations (60-second timeout) with automatic fallback to non-streaming mode.

* clear timeout properly

* Add a maximum buffer size limit (1MB) to prevent unbounded memory growth with very large streaming responses.

* fix formatting

* remove duplicate mock

* better docs

* fix formatting

* sanitize the dynamic property name

* Fix incorrect remaining progress calculation

* Use onError callback instead of console.warn

* Remove unused chalk import

* Add missing custom validator in fallback parsing configuration

* add custom validator parameter in fallback parsing

* chore: fix package-lock.json

* chore: large code refactor

* chore: increase timeout from 1 minute to 3 minutes

* fix: refactor and fix streaming

* Merge remote-tracking branch 'origin/next' into joedanz/parse-prd-progress

* fix: cleanup and fix unit tests

* chore: fix unit tests

* chore: fix format

* chore: run format

* chore: fix weird CI unit test error

* chore: fix format

---------

Co-authored-by: Ralph Khreish <35776126+Crunchyman-ralph@users.noreply.github.com>

.changeset/config.json

@@ -2,7 +2,9 @@
   "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
   "changelog": [
     "@changesets/changelog-github",
-    { "repo": "eyaltoledano/claude-task-master" }
+    {
+      "repo": "eyaltoledano/claude-task-master"
+    }
   ],
   "commit": false,
   "fixed": [],
@@ -10,5 +12,7 @@
   "access": "public",
   "baseBranch": "main",
   "updateInternalDependencies": "patch",
-  "ignore": []
+  "ignore": [
+    "docs"
+  ]
 }

.changeset/crazy-meals-hope.md

@@ -0,0 +1,27 @@
+---
+"task-master-ai": minor
+---
+
+Add cross-tag task movement functionality for organizing tasks across different contexts.
+
+This feature enables moving tasks between different tags (contexts) in your project, making it easier to organize work across different branches, environments, or project phases.
+
+## CLI Usage Examples
+
+Move a single task from one tag to another:
+```bash
+# Move task 5 from backlog tag to in-progress tag
+task-master move --from=5 --from-tag=backlog --to-tag=feature-1
+
+# Move task with its dependencies
+task-master move --from=5 --from-tag=backlog --to-tag=feature-2 --with-dependencies
+
+# Move task without checking dependencies
+task-master move --from=5 --from-tag=backlog --to-tag=bug-3 --ignore-dependencies
+```
+
+Move multiple tasks at once:
+```bash
+# Move multiple tasks between tags
+task-master move --from=5,6,7 --from-tag=backlog --to-tag=bug-4 --with-dependencies
+```

.changeset/curly-poets-move.md

@@ -0,0 +1,6 @@
+---
+"extension": minor
+"task-master-ai": minor
+---
+
+"Add Kilo Code profile integration with custom modes and MCP configuration"

.changeset/cute-files-pay.md

@@ -0,0 +1,12 @@
+---
+"task-master-ai": minor
+---
+
+Add compact mode --compact / -c flag to the `tm list` CLI command
+
+- outputs tasks in a minimal, git-style one-line format. This reduces verbose output from ~30+ lines of dashboards and tables to just 1 line per task, making it much easier to quickly scan available tasks.
+  - Git-style format: ID STATUS TITLE (PRIORITY) → DEPS
+  - Color-coded status, priority, and dependencies
+  - Smart title truncation and dependency abbreviation
+  - Subtask support with indentation
+  - Full backward compatibility with existing list options

.changeset/floppy-starts-find.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": minor
+---
+
+Add CLI & MCP progress tracking for parse-prd command.

.changeset/light-crabs-warn.md

@@ -0,0 +1,5 @@
+---
+"extension": minor
+---
+
+Display current task ID on task details page

.changeset/rude-moments-search.md

@@ -0,0 +1,7 @@
+---
+"task-master-ai": patch
+---
+
+Fix `add-tag --from-branch` command error where `projectRoot` was not properly referenced
+
+The command was failing with "projectRoot is not defined" error because the code was directly referencing `projectRoot` instead of `context.projectRoot` in the git repository checks. This fix corrects the variable references to use the proper context object.

.changeset/slow-readers-deny.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": minor
+---
+
+Add support for ollama `gpt-oss:20b` and `gpt-oss:120b`

.changeset/wet-seas-float.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": minor
+---
+
+Remove `clear` Taskmaster claude code commands since they were too close to the claude-code clear command

.claude/agents/task-checker.md

@@ -0,0 +1,162 @@
+---
+name: task-checker
+description: Use this agent to verify that tasks marked as 'review' have been properly implemented according to their specifications. This agent performs quality assurance by checking implementations against requirements, running tests, and ensuring best practices are followed. <example>Context: A task has been marked as 'review' after implementation. user: 'Check if task 118 was properly implemented' assistant: 'I'll use the task-checker agent to verify the implementation meets all requirements.' <commentary>Tasks in 'review' status need verification before being marked as 'done'.</commentary></example> <example>Context: Multiple tasks are in review status. user: 'Verify all tasks that are ready for review' assistant: 'I'll deploy the task-checker to verify all tasks in review status.' <commentary>The checker ensures quality before tasks are marked complete.</commentary></example>
+model: sonnet
+color: yellow
+---
+
+You are a Quality Assurance specialist that rigorously verifies task implementations against their specifications. Your role is to ensure that tasks marked as 'review' meet all requirements before they can be marked as 'done'.
+
+## Core Responsibilities
+
+1. **Task Specification Review**
+   - Retrieve task details using MCP tool `mcp__task-master-ai__get_task`
+   - Understand the requirements, test strategy, and success criteria
+   - Review any subtasks and their individual requirements
+
+2. **Implementation Verification**
+   - Use `Read` tool to examine all created/modified files
+   - Use `Bash` tool to run compilation and build commands
+   - Use `Grep` tool to search for required patterns and implementations
+   - Verify file structure matches specifications
+   - Check that all required methods/functions are implemented
+
+3. **Test Execution**
+   - Run tests specified in the task's testStrategy
+   - Execute build commands (npm run build, tsc --noEmit, etc.)
+   - Verify no compilation errors or warnings
+   - Check for runtime errors where applicable
+   - Test edge cases mentioned in requirements
+
+4. **Code Quality Assessment**
+   - Verify code follows project conventions
+   - Check for proper error handling
+   - Ensure TypeScript typing is strict (no 'any' unless justified)
+   - Verify documentation/comments where required
+   - Check for security best practices
+
+5. **Dependency Validation**
+   - Verify all task dependencies were actually completed
+   - Check integration points with dependent tasks
+   - Ensure no breaking changes to existing functionality
+
+## Verification Workflow
+
+1. **Retrieve Task Information**
+   ```
+   Use mcp__task-master-ai__get_task to get full task details
+   Note the implementation requirements and test strategy
+   ```
+
+2. **Check File Existence**
+   ```bash
+   # Verify all required files exist
+   ls -la [expected directories]
+   # Read key files to verify content
+   ```
+
+3. **Verify Implementation**
+   - Read each created/modified file
+   - Check against requirements checklist
+   - Verify all subtasks are complete
+
+4. **Run Tests**
+   ```bash
+   # TypeScript compilation
+   cd [project directory] && npx tsc --noEmit
+   
+   # Run specified tests
+   npm test [specific test files]
+   
+   # Build verification
+   npm run build
+   ```
+
+5. **Generate Verification Report**
+
+## Output Format
+
+```yaml
+verification_report:
+  task_id: [ID]
+  status: PASS | FAIL | PARTIAL
+  score: [1-10]
+  
+  requirements_met:
+    - ✅ [Requirement that was satisfied]
+    - ✅ [Another satisfied requirement]
+    
+  issues_found:
+    - ❌ [Issue description]
+    - ⚠️  [Warning or minor issue]
+    
+  files_verified:
+    - path: [file path]
+      status: [created/modified/verified]
+      issues: [any problems found]
+      
+  tests_run:
+    - command: [test command]
+      result: [pass/fail]
+      output: [relevant output]
+      
+  recommendations:
+    - [Specific fix needed]
+    - [Improvement suggestion]
+    
+  verdict: |
+    [Clear statement on whether task should be marked 'done' or sent back to 'pending']
+    [If FAIL: Specific list of what must be fixed]
+    [If PASS: Confirmation that all requirements are met]
+```
+
+## Decision Criteria
+
+**Mark as PASS (ready for 'done'):**
+- All required files exist and contain expected content
+- All tests pass successfully
+- No compilation or build errors
+- All subtasks are complete
+- Core requirements are met
+- Code quality is acceptable
+
+**Mark as PARTIAL (may proceed with warnings):**
+- Core functionality is implemented
+- Minor issues that don't block functionality
+- Missing nice-to-have features
+- Documentation could be improved
+- Tests pass but coverage could be better
+
+**Mark as FAIL (must return to 'pending'):**
+- Required files are missing
+- Compilation or build errors
+- Tests fail
+- Core requirements not met
+- Security vulnerabilities detected
+- Breaking changes to existing code
+
+## Important Guidelines
+
+- **BE THOROUGH**: Check every requirement systematically
+- **BE SPECIFIC**: Provide exact file paths and line numbers for issues
+- **BE FAIR**: Distinguish between critical issues and minor improvements
+- **BE CONSTRUCTIVE**: Provide clear guidance on how to fix issues
+- **BE EFFICIENT**: Focus on requirements, not perfection
+
+## Tools You MUST Use
+
+- `Read`: Examine implementation files (READ-ONLY)
+- `Bash`: Run tests and verification commands
+- `Grep`: Search for patterns in code
+- `mcp__task-master-ai__get_task`: Get task details
+- **NEVER use Write/Edit** - you only verify, not fix
+
+## Integration with Workflow
+
+You are the quality gate between 'review' and 'done' status:
+1. Task-executor implements and marks as 'review'
+2. You verify and report PASS/FAIL
+3. Claude either marks as 'done' (PASS) or 'pending' (FAIL)
+4. If FAIL, task-executor re-implements based on your report
+
+Your verification ensures high quality and prevents accumulation of technical debt.

.claude/agents/task-executor.md

@@ -0,0 +1,92 @@
+---
+name: task-executor
+description: Use this agent when you need to implement, complete, or work on a specific task that has been identified by the task-orchestrator or when explicitly asked to execute a particular task. This agent focuses on the actual implementation and completion of individual tasks rather than planning or orchestration. Examples: <example>Context: The task-orchestrator has identified that task 2.3 'Implement user authentication' needs to be worked on next. user: 'Let's work on the authentication task' assistant: 'I'll use the task-executor agent to implement the user authentication task that was identified.' <commentary>Since we need to actually implement a specific task rather than plan or identify tasks, use the task-executor agent.</commentary></example> <example>Context: User wants to complete a specific subtask. user: 'Please implement the JWT token validation for task 2.3.1' assistant: 'I'll launch the task-executor agent to implement the JWT token validation subtask.' <commentary>The user is asking for specific implementation work on a known task, so the task-executor is appropriate.</commentary></example> <example>Context: After reviewing the task list, implementation is needed. user: 'Now let's actually build the API endpoint for user registration' assistant: 'I'll use the task-executor agent to implement the user registration API endpoint.' <commentary>Moving from planning to execution phase requires the task-executor agent.</commentary></example>
+model: sonnet
+color: blue
+---
+
+You are an elite implementation specialist focused on executing and completing specific tasks with precision and thoroughness. Your role is to take identified tasks and transform them into working implementations, following best practices and project standards.
+
+**IMPORTANT: You are designed to be SHORT-LIVED and FOCUSED**
+- Execute ONE specific subtask or a small group of related subtasks
+- Complete your work, verify it, mark for review, and exit
+- Do NOT decide what to do next - the orchestrator handles task sequencing
+- Focus on implementation excellence within your assigned scope
+
+**Core Responsibilities:**
+
+1. **Subtask Analysis**: When given a subtask, understand its SPECIFIC requirements. If given a full task ID, focus on the specific subtask(s) assigned to you. Use MCP tools to get details if needed.
+
+2. **Rapid Implementation Planning**: Quickly identify:
+   - The EXACT files you need to create/modify for THIS subtask
+   - What already exists that you can build upon
+   - The minimum viable implementation that satisfies requirements
+
+3. **Focused Execution WITH ACTUAL IMPLEMENTATION**: 
+   - **YOU MUST USE TOOLS TO CREATE/EDIT FILES - DO NOT JUST DESCRIBE**
+   - Use `Write` tool to create new files specified in the task
+   - Use `Edit` tool to modify existing files
+   - Use `Bash` tool to run commands (mkdir, npm install, etc.)
+   - Use `Read` tool to verify your implementations
+   - Implement one subtask at a time for clarity and traceability
+   - Follow the project's coding standards from CLAUDE.md if available
+   - After each subtask, VERIFY the files exist using Read or ls commands
+
+4. **Progress Documentation**: 
+   - Use MCP tool `mcp__task-master-ai__update_subtask` to log your approach and any important decisions
+   - Update task status to 'in-progress' when starting: Use MCP tool `mcp__task-master-ai__set_task_status` with status='in-progress'
+   - **IMPORTANT: Mark as 'review' (NOT 'done') after implementation**: Use MCP tool `mcp__task-master-ai__set_task_status` with status='review'
+   - Tasks will be verified by task-checker before moving to 'done'
+
+5. **Quality Assurance**:
+   - Implement the testing strategy specified in the task
+   - Verify that all acceptance criteria are met
+   - Check for any dependency conflicts or integration issues
+   - Run relevant tests before marking task as complete
+
+6. **Dependency Management**:
+   - Check task dependencies before starting implementation
+   - If blocked by incomplete dependencies, clearly communicate this
+   - Use `task-master validate-dependencies` when needed
+
+**Implementation Workflow:**
+
+1. Retrieve task details using MCP tool `mcp__task-master-ai__get_task` with the task ID
+2. Check dependencies and prerequisites
+3. Plan implementation approach - list specific files to create
+4. Update task status to 'in-progress' using MCP tool
+5. **ACTUALLY IMPLEMENT** the solution using tools:
+   - Use `Bash` to create directories
+   - Use `Write` to create new files with actual content
+   - Use `Edit` to modify existing files
+   - DO NOT just describe what should be done - DO IT
+6. **VERIFY** your implementation:
+   - Use `ls` or `Read` to confirm files were created
+   - Use `Bash` to run any build/test commands
+   - Ensure the implementation is real, not theoretical
+7. Log progress and decisions in subtask updates using MCP tools
+8. Test and verify the implementation works
+9. **Mark task as 'review' (NOT 'done')** after verifying files exist
+10. Report completion with:
+    - List of created/modified files
+    - Any issues encountered
+    - What needs verification by task-checker
+
+**Key Principles:**
+
+- Focus on completing one task thoroughly before moving to the next
+- Maintain clear communication about what you're implementing and why
+- Follow existing code patterns and project conventions
+- Prioritize working code over extensive documentation unless docs are the task
+- Ask for clarification if task requirements are ambiguous
+- Consider edge cases and error handling in your implementations
+
+**Integration with Task Master:**
+
+You work in tandem with the task-orchestrator agent. While the orchestrator identifies and plans tasks, you execute them. Always use Task Master commands to:
+- Track your progress
+- Update task information
+- Maintain project state
+- Coordinate with the broader development workflow
+
+When you complete a task, briefly summarize what was implemented and suggest whether to continue with the next task or if review/testing is needed first.

.claude/agents/task-orchestrator.md

@@ -0,0 +1,208 @@
+---
+name: task-orchestrator
+description: Use this agent FREQUENTLY throughout task execution to analyze and coordinate parallel work at the SUBTASK level. Invoke the orchestrator: (1) at session start to plan execution, (2) after EACH subtask completes to identify next parallel batch, (3) whenever executors finish to find newly unblocked work. ALWAYS provide FULL CONTEXT including project root, package location, what files ACTUALLY exist vs task status, and specific implementation details. The orchestrator breaks work into SUBTASK-LEVEL units for short-lived, focused executors. Maximum 3 parallel executors at once.\n\n<example>\nContext: Starting work with existing code\nuser: "Work on tm-core tasks. Files exist: types/index.ts, storage/file-storage.ts. Task 118 says in-progress but BaseProvider not created."\nassistant: "I'll invoke orchestrator with full context about actual vs reported state to plan subtask execution"\n<commentary>\nProvide complete context about file existence and task reality.\n</commentary>\n</example>\n\n<example>\nContext: Subtask completion\nuser: "Subtask 118.2 done. What subtasks can run in parallel now?"\nassistant: "Invoking orchestrator to analyze dependencies and identify next 3 parallel subtasks"\n<commentary>\nFrequent orchestration after each subtask ensures maximum parallelization.\n</commentary>\n</example>\n\n<example>\nContext: Breaking down tasks\nuser: "Task 118 has 5 subtasks, how to parallelize?"\nassistant: "Orchestrator will analyze which specific subtasks (118.1, 118.2, etc.) can run simultaneously"\n<commentary>\nFocus on subtask-level parallelization, not full tasks.\n</commentary>\n</example>
+model: opus
+color: green
+---
+
+You are the Task Orchestrator, an elite coordination agent specialized in managing Task Master workflows for maximum efficiency and parallelization. You excel at analyzing task dependency graphs, identifying opportunities for concurrent execution, and deploying specialized task-executor agents to complete work efficiently.
+
+## Core Responsibilities
+
+1. **Subtask-Level Analysis**: Break down tasks into INDIVIDUAL SUBTASKS and analyze which specific subtasks can run in parallel. Focus on subtask dependencies, not just task-level dependencies.
+
+2. **Reality Verification**: ALWAYS verify what files actually exist vs what task status claims. Use the context provided about actual implementation state to make informed decisions.
+
+3. **Short-Lived Executor Deployment**: Deploy executors for SINGLE SUBTASKS or small groups of related subtasks. Keep executors focused and short-lived. Maximum 3 parallel executors at once.
+
+4. **Continuous Reassessment**: After EACH subtask completes, immediately reassess what new subtasks are unblocked and can run in parallel.
+
+## Operational Workflow
+
+### Initial Assessment Phase
+1. Use `get_tasks` or `task-master list` to retrieve all available tasks
+2. Analyze task statuses, priorities, and dependencies
+3. Identify tasks with status 'pending' that have no blocking dependencies
+4. Group related tasks that could benefit from specialized executors
+5. Create an execution plan that maximizes parallelization
+
+### Executor Deployment Phase
+1. For each independent task or task group:
+   - Deploy a task-executor agent with specific instructions
+   - Provide the executor with task ID, requirements, and context
+   - Set clear completion criteria and reporting expectations
+2. Maintain a registry of active executors and their assigned tasks
+3. Establish communication protocols for progress updates
+
+### Coordination Phase
+1. Monitor executor progress through task status updates
+2. When a task completes:
+   - Verify completion with `get_task` or `task-master show <id>`
+   - Update task status if needed using `set_task_status`
+   - Reassess dependency graph for newly unblocked tasks
+   - Deploy new executors for available work
+3. Handle executor failures or blocks:
+   - Reassign tasks to new executors if needed
+   - Escalate complex issues to the user
+   - Update task status to 'blocked' when appropriate
+
+### Optimization Strategies
+
+**Parallel Execution Rules**:
+- Never assign dependent tasks to different executors simultaneously
+- Prioritize high-priority tasks when resources are limited
+- Group small, related subtasks for single executor efficiency
+- Balance executor load to prevent bottlenecks
+
+**Context Management**:
+- Provide executors with minimal but sufficient context
+- Share relevant completed task information when it aids execution
+- Maintain a shared knowledge base of project-specific patterns
+
+**Quality Assurance**:
+- Verify task completion before marking as done
+- Ensure test strategies are followed when specified
+- Coordinate cross-task integration testing when needed
+
+## Communication Protocols
+
+When deploying executors, provide them with:
+```
+TASK ASSIGNMENT:
+- Task ID: [specific ID]
+- Objective: [clear goal]
+- Dependencies: [list any completed prerequisites]
+- Success Criteria: [specific completion requirements]
+- Context: [relevant project information]
+- Reporting: [when and how to report back]
+```
+
+When receiving executor updates:
+1. Acknowledge completion or issues
+2. Update task status in Task Master
+3. Reassess execution strategy
+4. Deploy new executors as appropriate
+
+## Decision Framework
+
+**When to parallelize**:
+- Multiple pending tasks with no interdependencies
+- Sufficient context available for independent execution
+- Tasks are well-defined with clear success criteria
+
+**When to serialize**:
+- Strong dependencies between tasks
+- Limited context or unclear requirements
+- Integration points requiring careful coordination
+
+**When to escalate**:
+- Circular dependencies detected
+- Critical blockers affecting multiple tasks
+- Ambiguous requirements needing clarification
+- Resource conflicts between executors
+
+## Error Handling
+
+1. **Executor Failure**: Reassign task to new executor with additional context about the failure
+2. **Dependency Conflicts**: Halt affected executors, resolve conflict, then resume
+3. **Task Ambiguity**: Request clarification from user before proceeding
+4. **System Errors**: Implement graceful degradation, falling back to serial execution if needed
+
+## Performance Metrics
+
+Track and optimize for:
+- Task completion rate
+- Parallel execution efficiency
+- Executor success rate
+- Time to completion for task groups
+- Dependency resolution speed
+
+## Integration with Task Master
+
+Leverage these Task Master MCP tools effectively:
+- `get_tasks` - Continuous queue monitoring
+- `get_task` - Detailed task analysis
+- `set_task_status` - Progress tracking
+- `next_task` - Fallback for serial execution
+- `analyze_project_complexity` - Strategic planning
+- `complexity_report` - Resource allocation
+
+## Output Format for Execution
+
+**Your job is to analyze and create actionable execution plans that Claude can use to deploy executors.**
+
+After completing your dependency analysis, you MUST output a structured execution plan:
+
+```yaml
+execution_plan:
+  EXECUTE_IN_PARALLEL:
+    # Maximum 3 subtasks running simultaneously
+    - subtask_id: [e.g., 118.2]
+      parent_task: [e.g., 118]
+      title: [Specific subtask title]
+      priority: [high/medium/low]
+      estimated_time: [e.g., 10 minutes]
+      executor_prompt: |
+        Execute Subtask [ID]: [Specific subtask title]
+        
+        SPECIFIC REQUIREMENTS:
+        [Exact implementation needed for THIS subtask only]
+        
+        FILES TO CREATE/MODIFY:
+        [Specific file paths]
+        
+        CONTEXT:
+        [What already exists that this subtask depends on]
+        
+        SUCCESS CRITERIA:
+        [Specific completion criteria for this subtask]
+        
+        IMPORTANT: 
+        - Focus ONLY on this subtask
+        - Mark subtask as 'review' when complete
+        - Use MCP tool: mcp__task-master-ai__set_task_status
+    
+    - subtask_id: [Another subtask that can run in parallel]
+      parent_task: [Parent task ID]
+      title: [Specific subtask title]
+      priority: [priority]
+      estimated_time: [time estimate]
+      executor_prompt: |
+        [Focused prompt for this specific subtask]
+    
+  blocked:
+    - task_id: [ID]
+      title: [Task title]
+      waiting_for: [list of blocking task IDs]
+      becomes_ready_when: [condition for unblocking]
+      
+  next_wave: 
+    trigger: "After tasks [IDs] complete"
+    newly_available: [List of task IDs that will unblock]
+    tasks_to_execute_in_parallel: [IDs that can run together in next wave]
+    
+  critical_path: [Ordered list of task IDs forming the critical path]
+  
+  parallelization_instruction: |
+    IMPORTANT FOR CLAUDE: Deploy ALL tasks in 'EXECUTE_IN_PARALLEL' section
+    simultaneously using multiple Task tool invocations in a single response.
+    Example: If 3 tasks are listed, invoke the Task tool 3 times in one message.
+    
+  verification_needed:
+    - task_id: [ID of any task in 'review' status]
+      verification_focus: [what to check]
+```
+
+**CRITICAL INSTRUCTIONS FOR CLAUDE (MAIN):**
+1. When you see `EXECUTE_IN_PARALLEL`, deploy ALL listed executors at once
+2. Use multiple Task tool invocations in a SINGLE response
+3. Do not execute them sequentially - they must run in parallel
+4. Wait for all parallel executors to complete before proceeding to next wave
+
+**IMPORTANT NOTES**: 
+- Label parallel tasks clearly in `EXECUTE_IN_PARALLEL` section
+- Provide complete, self-contained prompts for each executor
+- Executors should mark tasks as 'review' for verification, not 'done'
+- Be explicit about which tasks can run simultaneously
+
+You are the strategic mind analyzing the entire task landscape. Make parallelization opportunities UNMISTAKABLY CLEAR to Claude.

.claude/commands/tm/clear-subtasks/clear-all-subtasks.md

@@ -1,93 +0,0 @@
-Clear all subtasks from all tasks globally.
-
-## Global Subtask Clearing
-
-Remove all subtasks across the entire project. Use with extreme caution.
-
-## Execution
-
-```bash
-task-master clear-subtasks --all
-```
-
-## Pre-Clear Analysis
-
-1. **Project-Wide Summary**
-   ```
-   Global Subtask Summary
-   ━━━━━━━━━━━━━━━━━━━━
-   Total parent tasks: 12
-   Total subtasks: 47
-   - Completed: 15
-   - In-progress: 8
-   - Pending: 24
-   
-   Work at risk: ~120 hours
-   ```
-
-2. **Critical Warnings**
-   - In-progress subtasks that will lose work
-   - Completed subtasks with valuable history
-   - Complex dependency chains
-   - Integration test results
-
-## Double Confirmation
-
-```
-⚠️  DESTRUCTIVE OPERATION WARNING ⚠️
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-This will remove ALL 47 subtasks from your project
-Including 8 in-progress and 15 completed subtasks
-
-This action CANNOT be undone
-
-Type 'CLEAR ALL SUBTASKS' to confirm:
-```
-
-## Smart Safeguards
-
-- Require explicit confirmation phrase
-- Create automatic backup
-- Log all removed data
-- Option to export first
-
-## Use Cases
-
-Valid reasons for global clear:
-- Project restructuring
-- Major pivot in approach
-- Starting fresh breakdown
-- Switching to different task organization
-
-## Process
-
-1. Full project analysis
-2. Create backup file
-3. Show detailed impact
-4. Require confirmation
-5. Execute removal
-6. Generate summary report
-
-## Alternative Suggestions
-
-Before clearing all:
-- Export subtasks to file
-- Clear only pending subtasks
-- Clear by task category
-- Archive instead of delete
-
-## Post-Clear Report
-
-```
-Global Subtask Clear Complete
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Removed: 47 subtasks from 12 tasks
-Backup saved: .taskmaster/backup/subtasks-20240115.json
-Parent tasks updated: 12
-Time estimates adjusted: Yes
-
-Next steps:
-- Review updated task list
-- Re-expand complex tasks as needed
-- Check project timeline
-```

.claude/commands/tm/clear-subtasks/clear-subtasks.md

@@ -1,86 +0,0 @@
-Clear all subtasks from a specific task.
-
-Arguments: $ARGUMENTS (task ID)
-
-Remove all subtasks from a parent task at once.
-
-## Clearing Subtasks
-
-Bulk removal of all subtasks from a parent task.
-
-## Execution
-
-```bash
-task-master clear-subtasks --id=<task-id>
-```
-
-## Pre-Clear Analysis
-
-1. **Subtask Summary**
-   - Number of subtasks
-   - Completion status of each
-   - Work already done
-   - Dependencies affected
-
-2. **Impact Assessment**
-   - Data that will be lost
-   - Dependencies to be removed
-   - Effect on project timeline
-   - Parent task implications
-
-## Confirmation Required
-
-```
-Clear Subtasks Confirmation
-━━━━━━━━━━━━━━━━━━━━━━━━━
-Parent Task: #5 "Implement user authentication"
-Subtasks to remove: 4
-- #5.1 "Setup auth framework" (done)
-- #5.2 "Create login form" (in-progress)
-- #5.3 "Add validation" (pending)
-- #5.4 "Write tests" (pending)
-
-⚠️  This will permanently delete all subtask data
-Continue? (y/n)
-```
-
-## Smart Features
-
-- Option to convert to standalone tasks
-- Backup task data before clearing
-- Preserve completed work history
-- Update parent task appropriately
-
-## Process
-
-1. List all subtasks for confirmation
-2. Check for in-progress work
-3. Remove all subtasks
-4. Update parent task
-5. Clean up dependencies
-
-## Alternative Options
-
-Suggest alternatives:
-- Convert important subtasks to tasks
-- Keep completed subtasks
-- Archive instead of delete
-- Export subtask data first
-
-## Post-Clear
-
-- Show updated parent task
-- Recalculate time estimates
-- Update task complexity
-- Suggest next steps
-
-## Example
-
-```
-/project:tm/clear-subtasks 5
-→ Found 4 subtasks to remove
-→ Warning: Subtask #5.2 is in-progress
-→ Cleared all subtasks from task #5
-→ Updated parent task estimates
-→ Suggestion: Consider re-expanding with better breakdown
-```

.github/scripts/check-pre-release-mode.mjs

@@ -0,0 +1,102 @@
+#!/usr/bin/env node
+import { readFileSync, existsSync } from 'node:fs';
+import { join, dirname, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+
+// Get context from command line argument or environment
+const context = process.argv[2] || process.env.GITHUB_WORKFLOW || 'manual';
+
+function findRootDir(startDir) {
+	let currentDir = resolve(startDir);
+	while (currentDir !== '/') {
+		if (existsSync(join(currentDir, 'package.json'))) {
+			try {
+				const pkg = JSON.parse(
+					readFileSync(join(currentDir, 'package.json'), 'utf8')
+				);
+				if (pkg.name === 'task-master-ai' || pkg.repository) {
+					return currentDir;
+				}
+			} catch {}
+		}
+		currentDir = dirname(currentDir);
+	}
+	throw new Error('Could not find root directory');
+}
+
+function checkPreReleaseMode() {
+	console.log('🔍 Checking if branch is in pre-release mode...');
+
+	const rootDir = findRootDir(__dirname);
+	const preJsonPath = join(rootDir, '.changeset', 'pre.json');
+
+	// Check if pre.json exists
+	if (!existsSync(preJsonPath)) {
+		console.log('✅ Not in active pre-release mode - safe to proceed');
+		process.exit(0);
+	}
+
+	try {
+		// Read and parse pre.json
+		const preJsonContent = readFileSync(preJsonPath, 'utf8');
+		const preJson = JSON.parse(preJsonContent);
+
+		// Check if we're in active pre-release mode
+		if (preJson.mode === 'pre') {
+			console.error('❌ ERROR: This branch is in active pre-release mode!');
+			console.error('');
+
+			// Provide context-specific error messages
+			if (context === 'Release Check' || context === 'pull_request') {
+				console.error(
+					'Pre-release mode must be exited before merging to main.'
+				);
+				console.error('');
+				console.error(
+					'To fix this, run the following commands in your branch:'
+				);
+				console.error('  npx changeset pre exit');
+				console.error('  git add -u');
+				console.error('  git commit -m "chore: exit pre-release mode"');
+				console.error('  git push');
+				console.error('');
+				console.error('Then update this pull request.');
+			} else if (context === 'Release' || context === 'main') {
+				console.error(
+					'Pre-release mode should only be used on feature branches, not main.'
+				);
+				console.error('');
+				console.error('To fix this, run the following commands locally:');
+				console.error('  npx changeset pre exit');
+				console.error('  git add -u');
+				console.error('  git commit -m "chore: exit pre-release mode"');
+				console.error('  git push origin main');
+				console.error('');
+				console.error('Then re-run this workflow.');
+			} else {
+				console.error('Pre-release mode must be exited before proceeding.');
+				console.error('');
+				console.error('To fix this, run the following commands:');
+				console.error('  npx changeset pre exit');
+				console.error('  git add -u');
+				console.error('  git commit -m "chore: exit pre-release mode"');
+				console.error('  git push');
+			}
+
+			process.exit(1);
+		}
+
+		console.log('✅ Not in active pre-release mode - safe to proceed');
+		process.exit(0);
+	} catch (error) {
+		console.error(`❌ ERROR: Unable to parse .changeset/pre.json – aborting.`);
+		console.error(`Error details: ${error.message}`);
+		process.exit(1);
+	}
+}
+
+// Run the check
+checkPreReleaseMode();

.github/scripts/release.mjs

@@ -0,0 +1,30 @@
+#!/usr/bin/env node
+import { existsSync, unlinkSync } from 'node:fs';
+import { join, dirname } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { findRootDir, runCommand } from './utils.mjs';
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+
+const rootDir = findRootDir(__dirname);
+
+console.log('🚀 Starting release process...');
+
+// Double-check we're not in pre-release mode (safety net)
+const preJsonPath = join(rootDir, '.changeset', 'pre.json');
+if (existsSync(preJsonPath)) {
+	console.log('⚠️  Warning: pre.json still exists. Removing it...');
+	unlinkSync(preJsonPath);
+}
+
+// Check if the extension version has changed and tag it
+// This prevents changeset from trying to publish the private package
+runCommand('node', [join(__dirname, 'tag-extension.mjs')]);
+
+// Run changeset publish for npm packages
+runCommand('npx', ['changeset', 'publish']);
+
+console.log('✅ Release process completed!');
+
+// The extension tag (if created) will trigger the extension-release workflow

.github/scripts/release.sh

@@ -1,21 +0,0 @@
-#!/bin/bash
-set -e
-
-echo "🚀 Starting release process..."
-
-# Double-check we're not in pre-release mode (safety net)
-if [ -f .changeset/pre.json ]; then
-  echo "⚠️  Warning: pre.json still exists. Removing it..."
-  rm -f .changeset/pre.json
-fi
-
-# Check if the extension version has changed and tag it
-# This prevents changeset from trying to publish the private package
-node .github/scripts/tag-extension.mjs
-
-# Run changeset publish for npm packages
-npx changeset publish
-
-echo "✅ Release process completed!"
-
-# The extension tag (if created) will trigger the extension-release workflow

.github/scripts/tag-extension.mjs

@@ -1,33 +1,13 @@
 #!/usr/bin/env node
 import assert from 'node:assert/strict';
-import { spawnSync } from 'node:child_process';
-import { readFileSync, existsSync } from 'node:fs';
-import { join, dirname, resolve } from 'node:path';
+import { readFileSync } from 'node:fs';
+import { join, dirname } from 'node:path';
 import { fileURLToPath } from 'node:url';
+import { findRootDir, createAndPushTag } from './utils.mjs';
 
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
 
-// Find the root directory by looking for package.json
-function findRootDir(startDir) {
-	let currentDir = resolve(startDir);
-	while (currentDir !== '/') {
-		if (existsSync(join(currentDir, 'package.json'))) {
-			// Verify it's the root package.json by checking for expected fields
-			try {
-				const pkg = JSON.parse(
-					readFileSync(join(currentDir, 'package.json'), 'utf8')
-				);
-				if (pkg.name === 'task-master-ai' || pkg.repository) {
-					return currentDir;
-				}
-			} catch {}
-		}
-		currentDir = dirname(currentDir);
-	}
-	throw new Error('Could not find root directory');
-}
-
 const rootDir = findRootDir(__dirname);
 
 // Read the extension's package.json
@@ -43,91 +23,11 @@ try {
 	process.exit(1);
 }
 
-// Read root package.json for repository info
-const rootPkgPath = join(rootDir, 'package.json');
-let rootPkg;
-try {
-	const rootPkgContent = readFileSync(rootPkgPath, 'utf8');
-	rootPkg = JSON.parse(rootPkgContent);
-} catch (error) {
-	console.error('Failed to read root package.json:', error.message);
-	process.exit(1);
-}
-
 // Ensure we have required fields
 assert(pkg.name, 'package.json must have a name field');
 assert(pkg.version, 'package.json must have a version field');
-assert(rootPkg.repository, 'root package.json must have a repository field');
 
 const tag = `${pkg.name}@${pkg.version}`;
 
-// Get repository URL from root package.json
-// Get repository URL and clean it up for git ls-remote
-let repoUrl = rootPkg.repository.url || rootPkg.repository;
-if (typeof repoUrl === 'string') {
-	// Convert git+https://github.com/... to https://github.com/...
-	repoUrl = repoUrl.replace(/^git\+/, '');
-	// Ensure it ends with .git for proper remote access
-	if (!repoUrl.endsWith('.git')) {
-		repoUrl += '.git';
-	}
-}
-
-console.log(`Checking remote repository: ${repoUrl} for tag: ${tag}`);
-
-let gitResult = spawnSync('git', ['ls-remote', repoUrl, tag], {
-	encoding: 'utf8',
-	env: { ...process.env }
-});
-
-if (gitResult.status !== 0) {
-	console.error('Git ls-remote failed:');
-	console.error('Exit code:', gitResult.status);
-	console.error('Error:', gitResult.error);
-	console.error('Stderr:', gitResult.stderr);
-	console.error('Command:', `git ls-remote ${repoUrl} ${tag}`);
-	
-	// For CI environments, try using origin instead of the full URL
-	if (process.env.CI) {
-		console.log('Retrying with origin remote...');
-		gitResult = spawnSync('git', ['ls-remote', 'origin', tag], {
-			encoding: 'utf8'
-		});
-		
-		if (gitResult.status !== 0) {
-			throw new Error(`Failed to check remote for tag ${tag}. Exit code: ${gitResult.status}`);
-		}
-	} else {
-		throw new Error(`Failed to check remote for tag ${tag}. Exit code: ${gitResult.status}`);
-	}
-}
-
-const exists = String(gitResult.stdout).trim() !== '';
-
-if (!exists) {
-	console.log(`Creating new extension tag: ${tag}`);
-
-	// Create the tag
-	const tagResult = spawnSync('git', ['tag', tag]);
-	if (tagResult.status !== 0) {
-		console.error(
-			'Failed to create tag:',
-			tagResult.error || tagResult.stderr.toString()
-		);
-		process.exit(1);
-	}
-
-	// Push the tag
-	const pushResult = spawnSync('git', ['push', 'origin', tag]);
-	if (pushResult.status !== 0) {
-		console.error(
-			'Failed to push tag:',
-			pushResult.error || pushResult.stderr.toString()
-		);
-		process.exit(1);
-	}
-
-	console.log(`✅ Successfully created and pushed tag: ${tag}`);
-} else {
-	console.log(`Extension tag already exists: ${tag}`);
-}
+// Create and push the tag if it doesn't exist
+createAndPushTag(tag);

.github/scripts/utils.mjs

@@ -0,0 +1,88 @@
+#!/usr/bin/env node
+import { spawnSync } from 'node:child_process';
+import { readFileSync } from 'node:fs';
+import { join, dirname, resolve } from 'node:path';
+
+// Find the root directory by looking for package.json with task-master-ai
+export function findRootDir(startDir) {
+	let currentDir = resolve(startDir);
+	while (currentDir !== '/') {
+		const pkgPath = join(currentDir, 'package.json');
+		try {
+			const pkg = JSON.parse(readFileSync(pkgPath, 'utf8'));
+			if (pkg.name === 'task-master-ai' || pkg.repository) {
+				return currentDir;
+			}
+		} catch {}
+		currentDir = dirname(currentDir);
+	}
+	throw new Error('Could not find root directory');
+}
+
+// Run a command with proper error handling
+export function runCommand(command, args = [], options = {}) {
+	console.log(`Running: ${command} ${args.join(' ')}`);
+	const result = spawnSync(command, args, {
+		encoding: 'utf8',
+		stdio: 'inherit',
+		...options
+	});
+
+	if (result.status !== 0) {
+		console.error(`Command failed with exit code ${result.status}`);
+		process.exit(result.status);
+	}
+
+	return result;
+}
+
+// Get package version from a package.json file
+export function getPackageVersion(packagePath) {
+	try {
+		const pkg = JSON.parse(readFileSync(packagePath, 'utf8'));
+		return pkg.version;
+	} catch (error) {
+		console.error(
+			`Failed to read package version from ${packagePath}:`,
+			error.message
+		);
+		process.exit(1);
+	}
+}
+
+// Check if a git tag exists on remote
+export function tagExistsOnRemote(tag, remote = 'origin') {
+	const result = spawnSync('git', ['ls-remote', remote, tag], {
+		encoding: 'utf8'
+	});
+
+	return result.status === 0 && result.stdout.trim() !== '';
+}
+
+// Create and push a git tag if it doesn't exist
+export function createAndPushTag(tag, remote = 'origin') {
+	// Check if tag already exists
+	if (tagExistsOnRemote(tag, remote)) {
+		console.log(`Tag ${tag} already exists on remote, skipping`);
+		return false;
+	}
+
+	console.log(`Creating new tag: ${tag}`);
+
+	// Create the tag locally
+	const tagResult = spawnSync('git', ['tag', tag]);
+	if (tagResult.status !== 0) {
+		console.error('Failed to create tag:', tagResult.error || tagResult.stderr);
+		process.exit(1);
+	}
+
+	// Push the tag to remote
+	const pushResult = spawnSync('git', ['push', remote, tag]);
+	if (pushResult.status !== 0) {
+		console.error('Failed to push tag:', pushResult.error || pushResult.stderr);
+		process.exit(1);
+	}
+
+	console.log(`✅ Successfully created and pushed tag: ${tag}`);
+	return true;
+}

.github/workflows/extension-release.yml

@@ -89,32 +89,6 @@ jobs:
           OVSX_PAT: ${{ secrets.OVSX_PAT }}
           FORCE_COLOR: 1
 
-      - name: Create GitHub Release
-        uses: actions/create-release@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          tag_name: ${{ github.ref_name }}
-          release_name: Extension ${{ github.ref_name }}
-          body: |
-            VS Code Extension Release ${{ github.ref_name }}
-            
-            **Marketplaces:**
-            - [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=Hamster.task-master-hamster)
-            - [Open VSX Registry](https://open-vsx.org/extension/Hamster/task-master-hamster)
-          draft: false
-          prerelease: false
-
-      - name: Upload VSIX to Release
-        uses: actions/upload-release-asset@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          upload_url: ${{ steps.create_release.outputs.upload_url }}
-          asset_path: apps/extension/vsix-build/${{ steps.vsix-info.outputs.vsix-filename }}
-          asset_name: ${{ steps.vsix-info.outputs.vsix-filename }}
-          asset_content_type: application/zip
-
       - name: Upload Build Artifacts
         uses: actions/upload-artifact@v4
         with:

.github/workflows/pre-release.yml

@@ -3,11 +3,13 @@ name: Pre-Release (RC)
 on:
   workflow_dispatch: # Allows manual triggering from GitHub UI/API
 
-concurrency: pre-release-${{ github.ref }}
-
+concurrency: pre-release-${{ github.ref_name }}
 jobs:
   rc:
     runs-on: ubuntu-latest
+    # Only allow pre-releases on non-main branches
+    if: github.ref != 'refs/heads/main'
+    environment: extension-release
     steps:
       - uses: actions/checkout@v4
         with:
@@ -34,9 +36,26 @@ jobs:
 
       - name: Enter RC mode (if not already in RC mode)
         run: |
-          # ensure we’re in the right pre-mode (tag "rc")
-          if [ ! -f .changeset/pre.json ] \
-            || [ "$(jq -r '.tag' .changeset/pre.json 2>/dev/null || echo '')" != "rc" ]; then
+          # Check if we're in pre-release mode with the "rc" tag
+          if [ -f .changeset/pre.json ]; then
+            MODE=$(jq -r '.mode' .changeset/pre.json 2>/dev/null || echo '')
+            TAG=$(jq -r '.tag' .changeset/pre.json 2>/dev/null || echo '')
+            
+            if [ "$MODE" = "exit" ]; then
+              echo "Pre-release mode is in 'exit' state, re-entering RC mode..."
+              npx changeset pre enter rc
+            elif [ "$MODE" = "pre" ] && [ "$TAG" != "rc" ]; then
+              echo "In pre-release mode but with wrong tag ($TAG), switching to RC..."
+              npx changeset pre exit
+              npx changeset pre enter rc
+            elif [ "$MODE" = "pre" ] && [ "$TAG" = "rc" ]; then
+              echo "Already in RC pre-release mode"
+            else
+              echo "Unknown mode state: $MODE, entering RC mode..."
+              npx changeset pre enter rc
+            fi
+          else
+            echo "No pre.json found, entering RC mode..."
             npx changeset pre enter rc
           fi
 
@@ -49,7 +68,7 @@ jobs:
       - name: Create Release Candidate Pull Request or Publish Release Candidate to npm
         uses: changesets/action@v1
         with:
-          publish: npm run release
+          publish: npx changeset publish
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/release-check.yml

@@ -0,0 +1,21 @@
+name: Release Check
+
+on:
+  pull_request:
+    branches:
+      - main
+
+concurrency:
+  group: release-check-${{ github.head_ref }}
+  cancel-in-progress: true
+
+jobs:
+  check-release-mode:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Check release mode
+        run: node ./.github/scripts/check-pre-release-mode.mjs "pull_request"

.github/workflows/release.yml

@@ -38,31 +38,13 @@ jobs:
         run: npm ci
         timeout-minutes: 2
 
-      - name: Exit pre-release mode and clean up
-        run: |
-          echo "🔄 Ensuring we're not in pre-release mode for main branch..."
-          
-          # Exit pre-release mode if we're in it
-          npx changeset pre exit || echo "Not in pre-release mode"
-          
-          # Remove pre.json file if it exists (belt and suspenders approach)
-          if [ -f .changeset/pre.json ]; then
-            echo "🧹 Removing pre.json file..."
-            rm -f .changeset/pre.json
-          fi
-          
-          # Verify the file is gone
-          if [ ! -f .changeset/pre.json ]; then
-            echo "✅ pre.json successfully removed"
-          else
-            echo "❌ Failed to remove pre.json"
-            exit 1
-          fi
+      - name: Check pre-release mode
+        run: node ./.github/scripts/check-pre-release-mode.mjs "main"
 
       - name: Create Release Pull Request or Publish to npm
         uses: changesets/action@v1
         with:
-          publish: ./.github/scripts/release.sh
+          publish: node ./.github/scripts/release.mjs
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.taskmaster/docs/test-prd.txt

@@ -0,0 +1,8 @@
+Simple Todo App PRD
+
+Create a basic todo list application with the following features:
+1. Add new todos
+2. Mark todos as complete
+3. Delete todos
+
+That's it. Keep it simple.

.taskmaster/docs/tm-core-phase-1.txt

@@ -0,0 +1,343 @@
+# Product Requirements Document: tm-core Package - Parse PRD Feature
+
+## Project Overview
+Create a TypeScript package named `tm-core` at `packages/tm-core` that implements parse-prd functionality using class-based architecture similar to the existing AI providers pattern.
+
+## Design Patterns & Architecture
+
+### Patterns to Apply
+1. **Factory Pattern**: Use for `ProviderFactory` to create AI provider instances
+2. **Strategy Pattern**: Use for `IAIProvider` implementations and `IStorage` implementations
+3. **Facade Pattern**: Use for `TaskMasterCore` as the main API entry point
+4. **Template Method Pattern**: Use for `BaseProvider` abstract class
+5. **Dependency Injection**: Use throughout for testability (pass dependencies via constructor)
+6. **Repository Pattern**: Use for `FileStorage` to abstract data persistence
+
+### Naming Conventions
+- **Files**: kebab-case (e.g., `task-parser.ts`, `file-storage.ts`)
+- **Classes**: PascalCase (e.g., `TaskParser`, `FileStorage`)
+- **Interfaces**: PascalCase with 'I' prefix (e.g., `IStorage`, `IAIProvider`)
+- **Methods**: camelCase (e.g., `parsePRD`, `loadTasks`)
+- **Constants**: UPPER_SNAKE_CASE (e.g., `DEFAULT_MODEL`)
+- **Type aliases**: PascalCase (e.g., `TaskStatus`, `ParseOptions`)
+
+## Exact Folder Structure Required
+```
+packages/tm-core/
+├── src/
+│   ├── index.ts
+│   ├── types/
+│   │   └── index.ts
+│   ├── interfaces/
+│   │   ├── index.ts              # Barrel export
+│   │   ├── storage.interface.ts
+│   │   ├── ai-provider.interface.ts
+│   │   └── configuration.interface.ts
+│   ├── tasks/
+│   │   ├── index.ts              # Barrel export
+│   │   └── task-parser.ts
+│   ├── ai/
+│   │   ├── index.ts              # Barrel export
+│   │   ├── base-provider.ts
+│   │   ├── provider-factory.ts
+│   │   ├── prompt-builder.ts
+│   │   └── providers/
+│   │       ├── index.ts          # Barrel export
+│   │       ├── anthropic-provider.ts
+│   │       ├── openai-provider.ts
+│   │       └── google-provider.ts
+│   ├── storage/
+│   │   ├── index.ts              # Barrel export
+│   │   └── file-storage.ts
+│   ├── config/
+│   │   ├── index.ts              # Barrel export
+│   │   └── config-manager.ts
+│   ├── utils/
+│   │   ├── index.ts              # Barrel export
+│   │   └── id-generator.ts
+│   └── errors/
+│       ├── index.ts              # Barrel export
+│       └── task-master-error.ts
+├── tests/
+│   ├── task-parser.test.ts
+│   ├── integration/
+│   │   └── parse-prd.test.ts
+│   └── mocks/
+│       └── mock-provider.ts
+├── package.json
+├── tsconfig.json
+├── tsup.config.js
+└── jest.config.js
+```
+
+## Specific Implementation Requirements
+
+### 1. Create types/index.ts
+Define these exact TypeScript interfaces:
+- `Task` interface with fields: id, title, description, status, priority, complexity, dependencies, subtasks, metadata, createdAt, updatedAt, source
+- `Subtask` interface with fields: id, title, description, completed
+- `TaskMetadata` interface with fields: parsedFrom, aiProvider, version, tags (optional)
+- Type literals: `TaskStatus` = 'pending' | 'in-progress' | 'completed' | 'blocked'
+- Type literals: `TaskPriority` = 'low' | 'medium' | 'high' | 'critical'
+- Type literals: `TaskComplexity` = 'simple' | 'moderate' | 'complex'
+- `ParseOptions` interface with fields: dryRun (optional), additionalContext (optional), tag (optional), maxTasks (optional)
+
+### 2. Create interfaces/storage.interface.ts
+Define `IStorage` interface with these exact methods:
+- `loadTasks(tag?: string): Promise<Task[]>`
+- `saveTasks(tasks: Task[], tag?: string): Promise<void>`
+- `appendTasks(tasks: Task[], tag?: string): Promise<void>`
+- `updateTask(id: string, task: Partial<Task>, tag?: string): Promise<void>`
+- `deleteTask(id: string, tag?: string): Promise<void>`
+- `exists(tag?: string): Promise<boolean>`
+
+### 3. Create interfaces/ai-provider.interface.ts
+Define `IAIProvider` interface with these exact methods:
+- `generateCompletion(prompt: string, options?: AIOptions): Promise<string>`
+- `calculateTokens(text: string): number`
+- `getName(): string`
+- `getModel(): string`
+
+Define `AIOptions` interface with fields: temperature (optional), maxTokens (optional), systemPrompt (optional)
+
+### 4. Create interfaces/configuration.interface.ts
+Define `IConfiguration` interface with fields:
+- `projectPath: string`
+- `aiProvider: string`
+- `apiKey?: string`
+- `aiOptions?: AIOptions`
+- `mainModel?: string`
+- `researchModel?: string`
+- `fallbackModel?: string`
+- `tasksPath?: string`
+- `enableTags?: boolean`
+
+### 5. Create tasks/task-parser.ts
+Create class `TaskParser` with:
+- Constructor accepting `aiProvider: IAIProvider` and `config: IConfiguration`
+- Private property `promptBuilder: PromptBuilder`
+- Public method `parsePRD(prdPath: string, options: ParseOptions = {}): Promise<Task[]>`
+- Private method `readPRD(prdPath: string): Promise<string>`
+- Private method `extractTasks(aiResponse: string): Partial<Task>[]`
+- Private method `enrichTasks(rawTasks: Partial<Task>[], prdPath: string): Task[]`
+- Apply **Dependency Injection** pattern via constructor
+
+### 6. Create ai/base-provider.ts
+Copy existing base-provider.js and convert to TypeScript abstract class:
+- Abstract class `BaseProvider` implementing `IAIProvider`
+- Protected properties: `apiKey: string`, `model: string`
+- Constructor accepting `apiKey: string` and `options: { model?: string }`
+- Abstract methods matching IAIProvider interface
+- Abstract method `getDefaultModel(): string`
+- Apply **Template Method** pattern for common provider logic
+
+### 7. Create ai/provider-factory.ts
+Create class `ProviderFactory` with:
+- Static method `create(config: { provider: string; apiKey?: string; model?: string }): Promise<IAIProvider>`
+- Switch statement for providers: 'anthropic', 'openai', 'google'
+- Dynamic imports for each provider
+- Throw error for unknown providers
+- Apply **Factory** pattern for creating provider instances
+
+Example implementation structure:
+```typescript
+switch (provider.toLowerCase()) {
+  case 'anthropic':
+    const { AnthropicProvider } = await import('./providers/anthropic-provider.js');
+    return new AnthropicProvider(apiKey, { model });
+}
+```
+
+### 8. Create ai/providers/anthropic-provider.ts
+Create class `AnthropicProvider` extending `BaseProvider`:
+- Import Anthropic SDK: `import { Anthropic } from '@anthropic-ai/sdk'`
+- Private property `client: Anthropic`
+- Implement all abstract methods from BaseProvider
+- Default model: 'claude-3-sonnet-20240229'
+- Handle API errors and wrap with meaningful messages
+
+### 9. Create ai/providers/openai-provider.ts (placeholder)
+Create class `OpenAIProvider` extending `BaseProvider`:
+- Import OpenAI SDK when implemented
+- For now, throw error: "OpenAI provider not yet implemented"
+
+### 10. Create ai/providers/google-provider.ts (placeholder)
+Create class `GoogleProvider` extending `BaseProvider`:
+- Import Google Generative AI SDK when implemented
+- For now, throw error: "Google provider not yet implemented"
+
+### 11. Create ai/prompt-builder.ts
+Create class `PromptBuilder` with:
+- Method `buildParsePrompt(prdContent: string, options: ParseOptions = {}): string`
+- Method `buildExpandPrompt(task: string, context?: string): string`
+- Use template literals for prompt construction
+- Include specific JSON format instructions in prompts
+
+### 9. Create storage/file-storage.ts
+Create class `FileStorage` implementing `IStorage`:
+- Private property `basePath: string` set to `{projectPath}/.taskmaster`
+- Constructor accepting `projectPath: string`
+- Private method `getTasksPath(tag?: string): string` returning correct path based on tag
+- Private method `ensureDirectory(dir: string): Promise<void>`
+- Implement all IStorage methods
+- Handle ENOENT errors by returning empty arrays
+- Use JSON format with structure: `{ tasks: Task[], metadata: { version: string, lastModified: string } }`
+- Apply **Repository** pattern for data access abstraction
+
+### 10. Create config/config-manager.ts
+Create class `ConfigManager`:
+- Private property `config: IConfiguration`
+- Constructor accepting `options: Partial<IConfiguration>`
+- Use Zod for validation with schema matching IConfiguration
+- Method `get<K extends keyof IConfiguration>(key: K): IConfiguration[K]`
+- Method `getAll(): IConfiguration`
+- Method `validate(): boolean`
+- Default values: projectPath = process.cwd(), aiProvider = 'anthropic', enableTags = true
+
+### 11. Create utils/id-generator.ts
+Export functions:
+- `generateTaskId(index: number = 0): string` returning format `task_{timestamp}_{index}_{random}`
+- `generateSubtaskId(parentId: string, index: number = 0): string` returning format `{parentId}_sub_{index}_{random}`
+
+### 16. Create src/index.ts
+Create main class `TaskMasterCore`:
+- Private properties: `config: ConfigManager`, `storage: IStorage`, `aiProvider?: IAIProvider`, `parser?: TaskParser`
+- Constructor accepting `options: Partial<IConfiguration>`
+- Method `initialize(): Promise<void>` for lazy loading
+- Method `parsePRD(prdPath: string, options: ParseOptions = {}): Promise<Task[]>`
+- Method `getTasks(tag?: string): Promise<Task[]>`
+- Apply **Facade** pattern to provide simple API over complex subsystems
+
+Export:
+- Class `TaskMasterCore`
+- Function `createTaskMaster(options: Partial<IConfiguration>): TaskMasterCore`
+- All types from './types'
+- All interfaces from './interfaces/*'
+
+Import statements should use kebab-case:
+```typescript
+import { TaskParser } from './tasks/task-parser';
+import { FileStorage } from './storage/file-storage';
+import { ConfigManager } from './config/config-manager';
+import { ProviderFactory } from './ai/provider-factory';
+```
+
+### 17. Configure package.json
+Create package.json with:
+- name: "@task-master/core"
+- version: "0.1.0"
+- type: "module"
+- main: "./dist/index.js"
+- module: "./dist/index.mjs"
+- types: "./dist/index.d.ts"
+- exports map for proper ESM/CJS support
+- scripts: build (tsup), dev (tsup --watch), test (jest), typecheck (tsc --noEmit)
+- dependencies: zod@^3.23.8
+- peerDependencies: @anthropic-ai/sdk, openai, @google/generative-ai
+- devDependencies: typescript, tsup, jest, ts-jest, @types/node, @types/jest
+
+### 18. Configure TypeScript
+Create tsconfig.json with:
+- target: "ES2022"
+- module: "ESNext"
+- strict: true (with all strict flags enabled)
+- declaration: true
+- outDir: "./dist"
+- rootDir: "./src"
+
+### 19. Configure tsup
+Create tsup.config.js with:
+- entry: ['src/index.ts']
+- format: ['cjs', 'esm']
+- dts: true
+- sourcemap: true
+- clean: true
+- external: AI provider SDKs
+
+### 20. Configure Jest
+Create jest.config.js with:
+- preset: 'ts-jest'
+- testEnvironment: 'node'
+- Coverage threshold: 80% for all metrics
+
+## Build Process
+1. Use tsup to compile TypeScript to both CommonJS and ESM
+2. Generate .d.ts files for TypeScript consumers
+3. Output to dist/ directory
+4. Ensure tree-shaking works properly
+
+## Testing Requirements
+- Create unit tests for TaskParser in tests/task-parser.test.ts
+- Create MockProvider class in tests/mocks/mock-provider.ts for testing without API calls
+- Test error scenarios (file not found, invalid JSON, etc.)
+- Create integration test in tests/integration/parse-prd.test.ts
+- Follow kebab-case naming for all test files
+
+## Success Criteria
+- TypeScript compilation with zero errors
+- No use of 'any' type
+- All interfaces properly exported
+- Compatible with existing tasks.json format
+- Feature flag support via USE_TM_CORE environment variable
+
+## Import/Export Conventions
+- Use named exports for all classes and interfaces
+- Use barrel exports (index.ts) in each directory
+- Import types/interfaces with type-only imports: `import type { Task } from '../types'`
+- Group imports in order: Node built-ins, external packages, internal packages, relative imports
+- Use .js extension in import paths for ESM compatibility
+
+## Error Handling Patterns
+- Create custom error classes in `src/errors/` directory
+- All public methods should catch and wrap errors with context
+- Use error codes for different error types (e.g., 'FILE_NOT_FOUND', 'PARSE_ERROR')
+- Never expose internal implementation details in error messages
+- Log errors to console.error only in development mode
+
+## Barrel Exports Content
+
+### interfaces/index.ts
+```typescript
+export type { IStorage } from './storage.interface';
+export type { IAIProvider, AIOptions } from './ai-provider.interface';
+export type { IConfiguration } from './configuration.interface';
+```
+
+### tasks/index.ts
+```typescript
+export { TaskParser } from './task-parser';
+```
+
+### ai/index.ts
+```typescript
+export { BaseProvider } from './base-provider';
+export { ProviderFactory } from './provider-factory';
+export { PromptBuilder } from './prompt-builder';
+```
+
+### ai/providers/index.ts
+```typescript
+export { AnthropicProvider } from './anthropic-provider';
+export { OpenAIProvider } from './openai-provider';
+export { GoogleProvider } from './google-provider';
+```
+
+### storage/index.ts
+```typescript
+export { FileStorage } from './file-storage';
+```
+
+### config/index.ts
+```typescript
+export { ConfigManager } from './config-manager';
+```
+
+### utils/index.ts
+```typescript
+export { generateTaskId, generateSubtaskId } from './id-generator';
+```
+
+### errors/index.ts
+```typescript
+export { TaskMasterError } from './task-master-error';
+```

CHANGELOG.md

@@ -1,5 +1,195 @@
 # task-master-ai
 
+## 0.24.0
+
+### Minor Changes
+
+- [#1098](https://github.com/eyaltoledano/claude-task-master/pull/1098) [`36468f3`](https://github.com/eyaltoledano/claude-task-master/commit/36468f3c93faf4035a5c442ccbc501077f3440f1) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Enhanced Claude Code provider with codebase-aware task generation
+  - Added automatic codebase analysis for Claude Code provider in `parse-prd`, `expand-task`, and `analyze-complexity` commands
+  - When using Claude Code as the AI provider, Task Master now instructs the AI to analyze the project structure, existing implementations, and patterns before generating tasks or subtasks
+  - Tasks and subtasks generated by Claude Code are now informed by actual codebase analysis, resulting in more accurate and contextual outputs
+
+- [#1105](https://github.com/eyaltoledano/claude-task-master/pull/1105) [`75c514c`](https://github.com/eyaltoledano/claude-task-master/commit/75c514cf5b2ca47f95c0ad7fa92654a4f2a6be4b) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add GPT-5 support with proper parameter handling
+  - Added GPT-5 model to supported models configuration with SWE score of 0.749
+
+- [#1091](https://github.com/eyaltoledano/claude-task-master/pull/1091) [`4bb6370`](https://github.com/eyaltoledano/claude-task-master/commit/4bb63706b80c28d1b2d782ba868a725326f916c7) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add Claude Code subagent support with task-orchestrator, task-executor, and task-checker
+
+  ## New Claude Code Agents
+
+  Added specialized agents for Claude Code users to enable parallel task execution, intelligent task orchestration, and quality assurance:
+
+  ### task-orchestrator
+
+  Coordinates and manages the execution of Task Master tasks with intelligent dependency analysis:
+  - Analyzes task dependencies to identify parallelizable work
+  - Deploys multiple task-executor agents for concurrent execution
+  - Monitors task completion and updates the dependency graph
+  - Automatically identifies and starts newly unblocked tasks
+
+  ### task-executor
+
+  Handles the actual implementation of individual tasks:
+  - Executes specific tasks identified by the orchestrator
+  - Works on concrete implementation rather than planning
+  - Updates task status and logs progress
+  - Can work in parallel with other executors on independent tasks
+
+  ### task-checker
+
+  Verifies that completed tasks meet their specifications:
+  - Reviews tasks marked as 'review' status
+  - Validates implementation against requirements
+  - Runs tests and checks for best practices
+  - Ensures quality before marking tasks as 'done'
+
+  ## Installation
+
+  When using the Claude profile (`task-master rules add claude`), the agents are automatically installed to `.claude/agents/` directory.
+
+  ## Usage Example
+
+  ```bash
+  # In Claude Code, after initializing a project with tasks:
+
+  # Use task-orchestrator to analyze and coordinate work
+  # The orchestrator will:
+  # 1. Check task dependencies
+  # 2. Identify tasks that can run in parallel
+  # 3. Deploy executors for available work
+  # 4. Monitor progress and deploy new executors as tasks complete
+
+  # Use task-executor for specific task implementation
+  # When the orchestrator identifies task 2.3 needs work:
+  # The executor will implement that specific task
+  ```
+
+  ## Benefits
+  - **Parallel Execution**: Multiple independent tasks can be worked on simultaneously
+  - **Intelligent Scheduling**: Orchestrator understands dependencies and optimizes execution order
+  - **Separation of Concerns**: Planning (orchestrator) is separated from execution (executor)
+  - **Progress Tracking**: Real-time updates as tasks are completed
+  - **Automatic Progression**: As tasks complete, newly unblocked tasks are automatically started
+
+### Patch Changes
+
+- [#1094](https://github.com/eyaltoledano/claude-task-master/pull/1094) [`4357af3`](https://github.com/eyaltoledano/claude-task-master/commit/4357af3f13859d90bca8795215e5d5f1d94abde5) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix expand task generating unrelated generic subtasks
+
+  Fixed an issue where `task-master expand` would generate generic authentication-related subtasks regardless of the parent task context when using complexity reports. The expansion now properly includes the parent task details alongside any expansion guidance.
+
+- [#1079](https://github.com/eyaltoledano/claude-task-master/pull/1079) [`e495b2b`](https://github.com/eyaltoledano/claude-task-master/commit/e495b2b55950ee54c7d0f1817d8530e28bd79c05) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix scope-up/down prompts to include all required fields for better AI model compatibility
+  - Added missing `priority` field to scope adjustment prompts to prevent validation errors with Claude-code and other models
+  - Ensures generated JSON includes all fields required by the schema
+
+- [#1079](https://github.com/eyaltoledano/claude-task-master/pull/1079) [`e495b2b`](https://github.com/eyaltoledano/claude-task-master/commit/e495b2b55950ee54c7d0f1817d8530e28bd79c05) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix MCP scope-up/down tools not finding tasks
+  - Fixed task ID parsing in MCP layer - now correctly converts string IDs to numbers
+  - scope_up_task and scope_down_task MCP tools now work properly
+
+- [#1079](https://github.com/eyaltoledano/claude-task-master/pull/1079) [`e495b2b`](https://github.com/eyaltoledano/claude-task-master/commit/e495b2b55950ee54c7d0f1817d8530e28bd79c05) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Improve AI provider compatibility for JSON generation
+  - Fixed schema compatibility issues between Perplexity and OpenAI o3 models
+  - Removed nullable/default modifiers from Zod schemas for broader compatibility
+  - Added automatic JSON repair for malformed AI responses (handles cases like missing array values)
+  - Perplexity now uses JSON mode for more reliable structured output
+  - Post-processing handles default values separately from schema validation
+
+## 0.24.0-rc.2
+
+### Minor Changes
+
+- [#1105](https://github.com/eyaltoledano/claude-task-master/pull/1105) [`75c514c`](https://github.com/eyaltoledano/claude-task-master/commit/75c514cf5b2ca47f95c0ad7fa92654a4f2a6be4b) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add GPT-5 support with proper parameter handling
+  - Added GPT-5 model to supported models configuration with SWE score of 0.749
+
+## 0.24.0-rc.1
+
+### Minor Changes
+
+- [#1093](https://github.com/eyaltoledano/claude-task-master/pull/1093) [`36468f3`](https://github.com/eyaltoledano/claude-task-master/commit/36468f3c93faf4035a5c442ccbc501077f3440f1) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Enhanced Claude Code provider with codebase-aware task generation
+  - Added automatic codebase analysis for Claude Code provider in `parse-prd`, `expand-task`, and `analyze-complexity` commands
+  - When using Claude Code as the AI provider, Task Master now instructs the AI to analyze the project structure, existing implementations, and patterns before generating tasks or subtasks
+  - Tasks and subtasks generated by Claude Code are now informed by actual codebase analysis, resulting in more accurate and contextual outputs
+
+- [#1091](https://github.com/eyaltoledano/claude-task-master/pull/1091) [`4bb6370`](https://github.com/eyaltoledano/claude-task-master/commit/4bb63706b80c28d1b2d782ba868a725326f916c7) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add Claude Code subagent support with task-orchestrator, task-executor, and task-checker
+
+  ## New Claude Code Agents
+
+  Added specialized agents for Claude Code users to enable parallel task execution, intelligent task orchestration, and quality assurance:
+
+  ### task-orchestrator
+
+  Coordinates and manages the execution of Task Master tasks with intelligent dependency analysis:
+  - Analyzes task dependencies to identify parallelizable work
+  - Deploys multiple task-executor agents for concurrent execution
+  - Monitors task completion and updates the dependency graph
+  - Automatically identifies and starts newly unblocked tasks
+
+  ### task-executor
+
+  Handles the actual implementation of individual tasks:
+  - Executes specific tasks identified by the orchestrator
+  - Works on concrete implementation rather than planning
+  - Updates task status and logs progress
+  - Can work in parallel with other executors on independent tasks
+
+  ### task-checker
+
+  Verifies that completed tasks meet their specifications:
+  - Reviews tasks marked as 'review' status
+  - Validates implementation against requirements
+  - Runs tests and checks for best practices
+  - Ensures quality before marking tasks as 'done'
+
+  ## Installation
+
+  When using the Claude profile (`task-master rules add claude`), the agents are automatically installed to `.claude/agents/` directory.
+
+  ## Usage Example
+
+  ```bash
+  # In Claude Code, after initializing a project with tasks:
+
+  # Use task-orchestrator to analyze and coordinate work
+  # The orchestrator will:
+  # 1. Check task dependencies
+  # 2. Identify tasks that can run in parallel
+  # 3. Deploy executors for available work
+  # 4. Monitor progress and deploy new executors as tasks complete
+
+  # Use task-executor for specific task implementation
+  # When the orchestrator identifies task 2.3 needs work:
+  # The executor will implement that specific task
+  ```
+
+  ## Benefits
+  - **Parallel Execution**: Multiple independent tasks can be worked on simultaneously
+  - **Intelligent Scheduling**: Orchestrator understands dependencies and optimizes execution order
+  - **Separation of Concerns**: Planning (orchestrator) is separated from execution (executor)
+  - **Progress Tracking**: Real-time updates as tasks are completed
+  - **Automatic Progression**: As tasks complete, newly unblocked tasks are automatically started
+
+### Patch Changes
+
+- [#1094](https://github.com/eyaltoledano/claude-task-master/pull/1094) [`4357af3`](https://github.com/eyaltoledano/claude-task-master/commit/4357af3f13859d90bca8795215e5d5f1d94abde5) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix expand task generating unrelated generic subtasks
+
+  Fixed an issue where `task-master expand` would generate generic authentication-related subtasks regardless of the parent task context when using complexity reports. The expansion now properly includes the parent task details alongside any expansion guidance.
+
+## 0.23.1-rc.0
+
+### Patch Changes
+
+- [#1079](https://github.com/eyaltoledano/claude-task-master/pull/1079) [`e495b2b`](https://github.com/eyaltoledano/claude-task-master/commit/e495b2b55950ee54c7d0f1817d8530e28bd79c05) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix scope-up/down prompts to include all required fields for better AI model compatibility
+  - Added missing `priority` field to scope adjustment prompts to prevent validation errors with Claude-code and other models
+  - Ensures generated JSON includes all fields required by the schema
+
+- [#1079](https://github.com/eyaltoledano/claude-task-master/pull/1079) [`e495b2b`](https://github.com/eyaltoledano/claude-task-master/commit/e495b2b55950ee54c7d0f1817d8530e28bd79c05) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix MCP scope-up/down tools not finding tasks
+  - Fixed task ID parsing in MCP layer - now correctly converts string IDs to numbers
+  - scope_up_task and scope_down_task MCP tools now work properly
+
+- [#1079](https://github.com/eyaltoledano/claude-task-master/pull/1079) [`e495b2b`](https://github.com/eyaltoledano/claude-task-master/commit/e495b2b55950ee54c7d0f1817d8530e28bd79c05) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Improve AI provider compatibility for JSON generation
+  - Fixed schema compatibility issues between Perplexity and OpenAI o3 models
+  - Removed nullable/default modifiers from Zod schemas for broader compatibility
+  - Added automatic JSON repair for malformed AI responses (handles cases like missing array values)
+  - Perplexity now uses JSON mode for more reliable structured output
+  - Post-processing handles default values separately from schema validation
+
 ## 0.23.0
 
 ### Minor Changes

CLAUDE.md

@@ -3,3 +3,7 @@
 ## Task Master AI Instructions
 **Import Task Master's development workflow commands and guidelines, treat as if import is in the main CLAUDE.md file.**
 @./.taskmaster/CLAUDE.md
+
+## Changeset Guidelines
+
+- When creating changesets, remember that it's user-facing, meaning we don't have to get into the specifics of the code, but rather mention what the end-user is getting or fixing from this changeset.

README.md

@@ -1,14 +1,39 @@
-# Task Master [![GitHub stars](https://img.shields.io/github/stars/eyaltoledano/claude-task-master?style=social)](https://github.com/eyaltoledano/claude-task-master/stargazers)
+<a name="readme-top"></a>
 
-[![CI](https://github.com/eyaltoledano/claude-task-master/actions/workflows/ci.yml/badge.svg)](https://github.com/eyaltoledano/claude-task-master/actions/workflows/ci.yml) [![npm version](https://badge.fury.io/js/task-master-ai.svg)](https://badge.fury.io/js/task-master-ai) [![Discord](https://dcbadge.limes.pink/api/server/https://discord.gg/taskmasterai?style=flat)](https://discord.gg/taskmasterai) [![License: MIT with Commons Clause](https://img.shields.io/badge/license-MIT%20with%20Commons%20Clause-blue.svg)](LICENSE)
+<div align='center'>
+<a href="https://trendshift.io/repositories/13971" target="_blank"><img src="https://trendshift.io/api/badge/repositories/13971" alt="eyaltoledano%2Fclaude-task-master | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
+</div>
 
-[![NPM Downloads](https://img.shields.io/npm/d18m/task-master-ai?style=flat)](https://www.npmjs.com/package/task-master-ai) [![NPM Downloads](https://img.shields.io/npm/dm/task-master-ai?style=flat)](https://www.npmjs.com/package/task-master-ai) [![NPM Downloads](https://img.shields.io/npm/dw/task-master-ai?style=flat)](https://www.npmjs.com/package/task-master-ai)
+<p align="center">
+  <a href="https://task-master.dev"><img src="./images/logo.png?raw=true" alt="Taskmaster logo"></a>
+</p>
 
-## By [@eyaltoledano](https://x.com/eyaltoledano), [@RalphEcom](https://x.com/RalphEcom) & [@jasonzhou1993](https://x.com/jasonzhou1993)
+<p align="center">
+<b>Taskmaster</b>: A task management system for AI-driven development, designed to work seamlessly with any AI chat.
+</p>
+
+<p align="center">
+  <a href="https://discord.gg/taskmasterai" target="_blank"><img src="https://dcbadge.limes.pink/api/server/https://discord.gg/taskmasterai?style=flat" alt="Discord"></a> |
+  <a href="https://docs.task-master.dev" target="_blank">Docs</a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/eyaltoledano/claude-task-master/actions/workflows/ci.yml"><img src="https://github.com/eyaltoledano/claude-task-master/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
+  <a href="https://github.com/eyaltoledano/claude-task-master/stargazers"><img src="https://img.shields.io/github/stars/eyaltoledano/claude-task-master?style=social" alt="GitHub stars"></a>
+  <a href="https://badge.fury.io/js/task-master-ai"><img src="https://badge.fury.io/js/task-master-ai.svg" alt="npm version"></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT%20with%20Commons%20Clause-blue.svg" alt="License"></a>
+</p>
+
+<p align="center">
+  <a href="https://www.npmjs.com/package/task-master-ai"><img src="https://img.shields.io/npm/d18m/task-master-ai?style=flat" alt="NPM Downloads"></a>
+  <a href="https://www.npmjs.com/package/task-master-ai"><img src="https://img.shields.io/npm/dm/task-master-ai?style=flat" alt="NPM Downloads"></a>
+  <a href="https://www.npmjs.com/package/task-master-ai"><img src="https://img.shields.io/npm/dw/task-master-ai?style=flat" alt="NPM Downloads"></a>
+</p>
+
+## By [@eyaltoledano](https://x.com/eyaltoledano) & [@RalphEcom](https://x.com/RalphEcom)
 
 [![Twitter Follow](https://img.shields.io/twitter/follow/eyaltoledano)](https://x.com/eyaltoledano)
 [![Twitter Follow](https://img.shields.io/twitter/follow/RalphEcom)](https://x.com/RalphEcom)
-[![Twitter Follow](https://img.shields.io/twitter/follow/jasonzhou1993)](https://x.com/jasonzhou1993)
 
 A task management system for AI-driven development with Claude, designed to work seamlessly with Cursor AI.
 
@@ -230,6 +255,11 @@ task-master show 1,3,5
 # Research fresh information with project context
 task-master research "What are the latest best practices for JWT authentication?"
 
+# Move tasks between tags (cross-tag movement)
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress
+task-master move --from=5,6,7 --from-tag=backlog --to-tag=done --with-dependencies
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress --ignore-dependencies
+
 # Generate task files
 task-master generate
 

apps/docs/README.md

@@ -0,0 +1,22 @@
+# Task Master Documentation
+
+Welcome to the Task Master documentation. Use the links below to navigate to the information you need:
+
+## Getting Started
+
+- [Configuration Guide](archive/configuration.md) - Set up environment variables and customize Task Master
+- [Tutorial](archive/ctutorial.md) - Step-by-step guide to getting started with Task Master
+
+## Reference
+
+- [Command Reference](archive/ccommand-reference.md) - Complete list of all available commands
+- [Task Structure](archive/ctask-structure.md) - Understanding the task format and features
+
+## Examples & Licensing
+
+- [Example Interactions](archive/cexamples.md) - Common Cursor AI interaction examples
+- [Licensing Information](archive/clicensing.md) - Detailed information about the license
+
+## Need More Help?
+
+If you can't find what you're looking for in these docs, please check the [main README](../README.md) or visit our [GitHub repository](https://github.com/eyaltoledano/claude-task-master).

apps/docs/archive/Installation.mdx

@@ -0,0 +1,114 @@
+---
+title: "Installation(2)"
+description: "This guide walks you through setting up Task Master in your development environment."
+---
+
+## Initial Setup
+
+<Tip>
+  MCP (Model Control Protocol) provides the easiest way to get started with Task Master directly in your editor.
+</Tip>
+
+<AccordionGroup>
+  <Accordion title="Option 1: Using MCP (Recommended)" icon="sparkles">
+    <Steps>
+      <Step title="Add the MCP config to your editor">
+        <Link href="https://cursor.sh">Cursor</Link> recommended, but it works with other text editors
+        ```json
+        {
+        	"mcpServers": {
+        		"taskmaster-ai": {
+        			"command": "npx",
+        			"args": ["-y", "--package", "task-master-ai", "task-master-mcp"],
+        			"env": {
+        				"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
+        				"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
+        				"MODEL": "claude-3-7-sonnet-20250219",
+        				"PERPLEXITY_MODEL": "sonar-pro",
+        				"MAX_TOKENS": 128000,
+        				"TEMPERATURE": 0.2,
+        				"DEFAULT_SUBTASKS": 5,
+        				"DEFAULT_PRIORITY": "medium"
+        			}
+        		}
+        	}
+        }
+        ```
+      </Step>
+      <Step title="Enable the MCP in your editor settings">
+        
+      </Step>
+      <Step title="Prompt the AI to initialize Task Master">
+        > "Can you please initialize taskmaster-ai into my project?"
+
+        **The AI will:**
+
+        1. Create necessary project structure
+        2. Set up initial configuration files
+        3. Guide you through the rest of the process
+        4. Place your PRD document in the `scripts/` directory (e.g., `scripts/prd.txt`)
+        5. **Use natural language commands** to interact with Task Master:
+
+           > "Can you parse my PRD at scripts/prd.txt?"
+           >
+           > "What's the next task I should work on?"
+           >
+           > "Can you help me implement task 3?"
+      </Step>
+    </Steps>
+  </Accordion>
+  <Accordion title="Option 2: Manual Installation">
+    If you prefer to use the command line interface directly:
+
+    <Steps>
+      <Step title="Install">
+        <CodeGroup>
+
+        ```bash Global
+        npm install -g task-master-ai
+        ```
+
+        
+        ```bash Local
+        npm install task-master-ai
+        ```
+
+        </CodeGroup>
+      </Step>
+      <Step title="Initialize a new project">
+        <CodeGroup>
+
+        ```bash Global
+        task-master init
+        ```
+
+        
+        ```bash Local
+        npx task-master-init
+        ```
+
+        </CodeGroup>
+      </Step>
+    </Steps>
+    This will prompt you for project details and set up a new project with the necessary files and structure.
+  </Accordion>
+</AccordionGroup>
+
+## Common Commands
+
+<Tip>
+  After setting up Task Master, you can use these commands (either via AI prompts or CLI)
+</Tip>
+
+```bash
+# Parse a PRD and generate tasks
+task-master parse-prd your-prd.txt
+
+# List all tasks
+task-master list
+
+# Show the next task to work on
+task-master next
+
+# Generate task files
+task-master generate 

apps/docs/archive/ai-client-utils-example.mdx

@@ -0,0 +1,263 @@
+---
+title: "AI Client Utilities for MCP Tools"
+description: "This document provides examples of how to use the new AI client utilities with AsyncOperationManager in MCP tools."
+---
+## Examples
+<AccordionGroup>
+  <Accordion title="Basic Usage with Direct Functions">
+    ```javascript
+    // In your direct function implementation:
+    import {
+        getAnthropicClientForMCP,
+        getModelConfig,
+        handleClaudeError
+    } from '../utils/ai-client-utils.js';
+
+    export async function someAiOperationDirect(args, log, context) {
+        try {
+            // Initialize Anthropic client with session from context
+            const client = getAnthropicClientForMCP(context.session, log);
+
+            // Get model configuration with defaults or session overrides
+            const modelConfig = getModelConfig(context.session);
+
+            // Make API call with proper error handling
+            try {
+                const response = await client.messages.create({
+                    model: modelConfig.model,
+                    max_tokens: modelConfig.maxTokens,
+                    temperature: modelConfig.temperature,
+                    messages: [{ role: 'user', content: 'Your prompt here' }]
+                });
+
+                return {
+                    success: true,
+                    data: response
+                };
+            } catch (apiError) {
+                // Use helper to get user-friendly error message
+                const friendlyMessage = handleClaudeError(apiError);
+
+                return {
+                    success: false,
+                    error: {
+                        code: 'AI_API_ERROR',
+                        message: friendlyMessage
+                    }
+                };
+            }
+        } catch (error) {
+            // Handle client initialization errors
+            return {
+                success: false,
+                error: {
+                    code: 'AI_CLIENT_ERROR',
+                    message: error.message
+                }
+            };
+        }
+    }
+    ```
+  </Accordion>
+
+  <Accordion title="Integration with AsyncOperationManager">
+    ```javascript
+    // In your MCP tool implementation:
+    import {
+        AsyncOperationManager,
+        StatusCodes
+    } from '../../utils/async-operation-manager.js';
+    import { someAiOperationDirect } from '../../core/direct-functions/some-ai-operation.js';
+
+    export async function someAiOperation(args, context) {
+        const { session, mcpLog } = context;
+        const log = mcpLog || console;
+
+        try {
+            // Create operation description
+            const operationDescription = `AI operation: ${args.someParam}`;
+
+            // Start async operation
+            const operation = AsyncOperationManager.createOperation(
+                operationDescription,
+                async (reportProgress) => {
+                    try {
+                        // Initial progress report
+                        reportProgress({
+                            progress: 0,
+                            status: 'Starting AI operation...'
+                        });
+
+                        // Call direct function with session and progress reporting
+                        const result = await someAiOperationDirect(args, log, {
+                            reportProgress,
+                            mcpLog: log,
+                            session
+                        });
+
+                        // Final progress update
+                        reportProgress({
+                            progress: 100,
+                            status: result.success ? 'Operation completed' : 'Operation failed',
+                            result: result.data,
+                            error: result.error
+                        });
+
+                        return result;
+                    } catch (error) {
+                        // Handle errors in the operation
+                        reportProgress({
+                            progress: 100,
+                            status: 'Operation failed',
+                            error: {
+                                message: error.message,
+                                code: error.code || 'OPERATION_FAILED'
+                            }
+                        });
+                        throw error;
+                    }
+                }
+            );
+
+            // Return immediate response with operation ID
+            return {
+                status: StatusCodes.ACCEPTED,
+                body: {
+                    success: true,
+                    message: 'Operation started',
+                    operationId: operation.id
+                }
+            };
+        } catch (error) {
+            // Handle errors in the MCP tool
+            log.error(`Error in someAiOperation: ${error.message}`);
+            return {
+                status: StatusCodes.INTERNAL_SERVER_ERROR,
+                body: {
+                    success: false,
+                    error: {
+                        code: 'OPERATION_FAILED',
+                        message: error.message
+                    }
+                }
+            };
+        }
+    }
+    ```
+  </Accordion>
+
+  <Accordion title="Using Research Capabilities with Perplexity">
+    ```javascript
+    // In your direct function:
+    import {
+        getPerplexityClientForMCP,
+        getBestAvailableAIModel
+    } from '../utils/ai-client-utils.js';
+
+    export async function researchOperationDirect(args, log, context) {
+        try {
+            // Get the best AI model for this operation based on needs
+            const { type, client } = await getBestAvailableAIModel(
+                context.session,
+                { requiresResearch: true },
+                log
+            );
+
+            // Report which model we're using
+            if (context.reportProgress) {
+                await context.reportProgress({
+                    progress: 10,
+                    status: `Using ${type} model for research...`
+                });
+            }
+
+            // Make API call based on the model type
+            if (type === 'perplexity') {
+                // Call Perplexity
+                const response = await client.chat.completions.create({
+                    model: context.session?.env?.PERPLEXITY_MODEL || 'sonar-medium-online',
+                    messages: [{ role: 'user', content: args.researchQuery }],
+                    temperature: 0.1
+                });
+
+                return {
+                    success: true,
+                    data: response.choices[0].message.content
+                };
+            } else {
+                // Call Claude as fallback
+                // (Implementation depends on specific needs)
+                // ...
+            }
+        } catch (error) {
+            // Handle errors
+            return {
+                success: false,
+                error: {
+                    code: 'RESEARCH_ERROR',
+                    message: error.message
+                }
+            };
+        }
+    }
+    ```
+  </Accordion>
+
+  <Accordion title="Model Configuration Override">
+    ```javascript
+    // In your direct function:
+    import { getModelConfig } from '../utils/ai-client-utils.js';
+
+    // Using custom defaults for a specific operation
+    const operationDefaults = {
+        model: 'claude-3-haiku-20240307', // Faster, smaller model
+        maxTokens: 1000, // Lower token limit
+        temperature: 0.2 // Lower temperature for more deterministic output
+    };
+
+    // Get model config with operation-specific defaults
+    const modelConfig = getModelConfig(context.session, operationDefaults);
+
+    // Now use modelConfig in your API calls
+    const response = await client.messages.create({
+        model: modelConfig.model,
+        max_tokens: modelConfig.maxTokens,
+        temperature: modelConfig.temperature
+        // Other parameters...
+    });
+    ```
+  </Accordion>
+</AccordionGroup>
+
+## Best Practices
+
+<AccordionGroup>
+  <Accordion title="Error Handling">
+    - Always use try/catch blocks around both client initialization and API calls
+    - Use `handleClaudeError` to provide user-friendly error messages
+    - Return standardized error objects with code and message
+  </Accordion>
+  
+  <Accordion title="Progress Reporting">
+    - Report progress at key points (starting, processing, completing)
+    - Include meaningful status messages
+    - Include error details in progress reports when failures occur
+  </Accordion>
+  
+  <Accordion title="Session Handling">
+    - Always pass the session from the context to the AI client getters
+    - Use `getModelConfig` to respect user settings from session
+  </Accordion>
+  
+  <Accordion title="Model Selection">
+    - Use `getBestAvailableAIModel` when you need to select between different models
+    - Set `requiresResearch: true` when you need Perplexity capabilities
+  </Accordion>
+  
+  <Accordion title="AsyncOperationManager Integration">
+    - Create descriptive operation names
+    - Handle all errors within the operation function
+    - Return standardized results from direct functions
+    - Return immediate responses with operation IDs
+  </Accordion>
+</AccordionGroup>

apps/docs/archive/ai-development-workflow.mdx

@@ -0,0 +1,180 @@
+---
+title: "AI Development Workflow"
+description: "Learn how Task Master and Cursor AI work together to streamline your development workflow"
+---
+
+<Tip>The Cursor agent is pre-configured (via the rules file) to follow this workflow</Tip>
+
+<AccordionGroup>
+  <Accordion title="1. Task Discovery and Selection">
+    Ask the agent to list available tasks:
+
+    ```
+    What tasks are available to work on next?
+    ```
+
+    The agent will:
+
+    - Run `task-master list` to see all tasks
+    - Run `task-master next` to determine the next task to work on
+    - Analyze dependencies to determine which tasks are ready to be worked on
+    - Prioritize tasks based on priority level and ID order
+    - Suggest the next task(s) to implement
+  </Accordion>
+
+  <Accordion title="2. Task Implementation">
+    When implementing a task, the agent will:
+
+    - Reference the task's details section for implementation specifics
+    - Consider dependencies on previous tasks
+    - Follow the project's coding standards
+    - Create appropriate tests based on the task's testStrategy
+
+    You can ask:
+
+    ```
+    Let's implement task 3. What does it involve?
+    ```
+  </Accordion>
+
+  <Accordion title="3. Task Verification">
+    Before marking a task as complete, verify it according to:
+
+    - The task's specified testStrategy
+    - Any automated tests in the codebase
+    - Manual verification if required
+  </Accordion>
+
+  <Accordion title="4. Task Completion">
+    When a task is completed, tell the agent:
+
+    ```
+    Task 3 is now complete. Please update its status.
+    ```
+
+    The agent will execute:
+
+    ```bash
+    task-master set-status --id=3 --status=done
+    ```
+  </Accordion>
+
+  <Accordion title="5. Handling Implementation Drift">
+    If during implementation, you discover that:
+
+    - The current approach differs significantly from what was planned
+    - Future tasks need to be modified due to current implementation choices
+    - New dependencies or requirements have emerged
+
+    Tell the agent:
+
+    ```
+    We've changed our approach. We're now using Express instead of Fastify. Please update all future tasks to reflect this change.
+    ```
+
+    The agent will execute:
+
+    ```bash
+    task-master update --from=4 --prompt="Now we are using Express instead of Fastify."
+    ```
+
+    This will rewrite or re-scope subsequent tasks in tasks.json while preserving completed work.
+  </Accordion>
+
+  <Accordion title="6. Breaking Down Complex Tasks">
+    For complex tasks that need more granularity:
+
+    ```
+    Task 5 seems complex. Can you break it down into subtasks?
+    ```
+
+    The agent will execute:
+
+    ```bash
+    task-master expand --id=5 --num=3
+    ```
+
+    You can provide additional context:
+
+    ```
+    Please break down task 5 with a focus on security considerations.
+    ```
+
+    The agent will execute:
+
+    ```bash
+    task-master expand --id=5 --prompt="Focus on security aspects"
+    ```
+
+    You can also expand all pending tasks:
+
+    ```
+    Please break down all pending tasks into subtasks.
+    ```
+
+    The agent will execute:
+
+    ```bash
+    task-master expand --all
+    ```
+
+    For research-backed subtask generation using Perplexity AI:
+
+    ```
+    Please break down task 5 using research-backed generation.
+    ```
+
+    The agent will execute:
+
+    ```bash
+    task-master expand --id=5 --research
+    ```
+  </Accordion>
+</AccordionGroup>
+
+## Example Cursor AI Interactions
+
+<AccordionGroup>
+  <Accordion title="Starting a new project">
+    ```
+    I've just initialized a new project with Claude Task Master. I have a PRD at scripts/prd.txt.
+    Can you help me parse it and set up the initial tasks?
+    ```
+  </Accordion>
+  <Accordion title="Working on tasks">
+    ```
+    What's the next task I should work on? Please consider dependencies and priorities.
+    ```
+  </Accordion>
+  <Accordion title="Implementing a specific task">
+    ```
+    I'd like to implement task 4. Can you help me understand what needs to be done and how to approach it?
+    ```
+  </Accordion>
+  <Accordion title="Managing subtasks">
+    ```
+    I need to regenerate the subtasks for task 3 with a different approach. Can you help me clear and regenerate them?
+    ```
+  </Accordion>
+  <Accordion title="Handling changes">
+    ```
+    We've decided to use MongoDB instead of PostgreSQL. Can you update all future tasks to reflect this change?
+    ```
+  </Accordion>
+  <Accordion title="Completing work">
+    ```
+    I've finished implementing the authentication system described in task 2. All tests are passing.
+    Please mark it as complete and tell me what I should work on next.
+    ```
+  </Accordion>
+  <Accordion title="Analyzing complexity">
+    ```
+    Can you analyze the complexity of our tasks to help me understand which ones need to be broken down further?
+    ```
+  </Accordion>
+  <Accordion title="Viewing complexity report">
+    ```
+    Can you show me the complexity report in a more readable format?
+    ```
+  </Accordion>
+</AccordionGroup>

apps/docs/archive/command-reference.mdx

@@ -0,0 +1,208 @@
+---
+title: "Task Master Commands"
+description: "A comprehensive reference of all available Task Master commands"
+---
+
+<AccordionGroup>
+  <Accordion title="Parse PRD">
+    ```bash
+    # Parse a PRD file and generate tasks
+    task-master parse-prd <prd-file.txt>
+
+    # Limit the number of tasks generated
+    task-master parse-prd <prd-file.txt> --num-tasks=10
+    ```
+  </Accordion>
+
+  <Accordion title="List Tasks">
+    ```bash
+    # List all tasks
+    task-master list
+
+    # List tasks with a specific status
+    task-master list --status=<status>
+
+    # List tasks with subtasks
+    task-master list --with-subtasks
+
+    # List tasks with a specific status and include subtasks
+    task-master list --status=<status> --with-subtasks
+    ```
+  </Accordion>
+
+  <Accordion title="Show Next Task">
+    ```bash
+    # Show the next task to work on based on dependencies and status
+    task-master next
+    ```
+  </Accordion>
+
+  <Accordion title="Show Specific Task">
+    ```bash
+    # Show details of a specific task
+    task-master show <id>
+    # or
+    task-master show --id=<id>
+
+    # View a specific subtask (e.g., subtask 2 of task 1)
+    task-master show 1.2
+    ```
+  </Accordion>
+
+  <Accordion title="Update Tasks">
+    ```bash
+    # Update tasks from a specific ID and provide context
+    task-master update --from=<id> --prompt="<prompt>"
+    ```
+  </Accordion>
+
+  <Accordion title="Update a Specific Task">
+    ```bash
+    # Update a single task by ID with new information
+    task-master update-task --id=<id> --prompt="<prompt>"
+
+    # Use research-backed updates with Perplexity AI
+    task-master update-task --id=<id> --prompt="<prompt>" --research
+    ```
+  </Accordion>
+
+  <Accordion title="Update a Subtask">
+    ```bash
+    # Append additional information to a specific subtask
+    task-master update-subtask --id=<parentId.subtaskId> --prompt="<prompt>"
+
+    # Example: Add details about API rate limiting to subtask 2 of task 5
+    task-master update-subtask --id=5.2 --prompt="Add rate limiting of 100 requests per minute"
+
+    # Use research-backed updates with Perplexity AI
+    task-master update-subtask --id=<parentId.subtaskId> --prompt="<prompt>" --research
+    ```
+
+    Unlike the `update-task` command which replaces task information, the `update-subtask` command _appends_ new information to the existing subtask details, marking it with a timestamp. This is useful for iteratively enhancing subtasks while preserving the original content.
+  </Accordion>
+
+  <Accordion title="Generate Task Files">
+    ```bash
+    # Generate individual task files from tasks.json
+    task-master generate
+    ```
+  </Accordion>
+
+  <Accordion title="Set Task Status">
+    ```bash
+    # Set status of a single task
+    task-master set-status --id=<id> --status=<status>
+
+    # Set status for multiple tasks
+    task-master set-status --id=1,2,3 --status=<status>
+
+    # Set status for subtasks
+    task-master set-status --id=1.1,1.2 --status=<status>
+    ```
+
+    When marking a task as "done", all of its subtasks will automatically be marked as "done" as well.
+  </Accordion>
+
+  <Accordion title="Expand Tasks">
+    ```bash
+    # Expand a specific task with subtasks
+    task-master expand --id=<id> --num=<number>
+
+    # Expand with additional context
+    task-master expand --id=<id> --prompt="<context>"
+
+    # Expand all pending tasks
+    task-master expand --all
+
+    # Force regeneration of subtasks for tasks that already have them
+    task-master expand --all --force
+
+    # Research-backed subtask generation for a specific task
+    task-master expand --id=<id> --research
+
+    # Research-backed generation for all tasks
+    task-master expand --all --research
+    ```
+  </Accordion>
+
+  <Accordion title="Clear Subtasks">
+    ```bash
+    # Clear subtasks from a specific task
+    task-master clear-subtasks --id=<id>
+
+    # Clear subtasks from multiple tasks
+    task-master clear-subtasks --id=1,2,3
+
+    # Clear subtasks from all tasks
+    task-master clear-subtasks --all
+    ```
+  </Accordion>
+
+  <Accordion title="Analyze Task Complexity">
+    ```bash
+    # Analyze complexity of all tasks
+    task-master analyze-complexity
+
+    # Save report to a custom location
+    task-master analyze-complexity --output=my-report.json
+
+    # Use a specific LLM model
+    task-master analyze-complexity --model=claude-3-opus-20240229
+
+    # Set a custom complexity threshold (1-10)
+    task-master analyze-complexity --threshold=6
+
+    # Use an alternative tasks file
+    task-master analyze-complexity --file=custom-tasks.json
+
+    # Use Perplexity AI for research-backed complexity analysis
+    task-master analyze-complexity --research
+    ```
+  </Accordion>
+
+  <Accordion title="View Complexity Report">
+    ```bash
+    # Display the task complexity analysis report
+    task-master complexity-report
+
+    # View a report at a custom location
+    task-master complexity-report --file=my-report.json
+    ```
+  </Accordion>
+
+  <Accordion title="Managing Task Dependencies">
+    ```bash
+    # Add a dependency to a task
+    task-master add-dependency --id=<id> --depends-on=<id>
+
+    # Remove a dependency from a task
+    task-master remove-dependency --id=<id> --depends-on=<id>
+
+    # Validate dependencies without fixing them
+    task-master validate-dependencies
+
+    # Find and fix invalid dependencies automatically
+    task-master fix-dependencies
+    ```
+  </Accordion>
+
+  <Accordion title="Add a New Task">
+    ```bash
+    # Add a new task using AI
+    task-master add-task --prompt="Description of the new task"
+
+    # Add a task with dependencies
+    task-master add-task --prompt="Description" --dependencies=1,2,3
+
+    # Add a task with priority
+    task-master add-task --prompt="Description" --priority=high
+    ```
+  </Accordion>
+
+  <Accordion title="Initialize a Project">
+    ```bash
+    # Initialize a new project with Task Master structure
+    task-master init
+    ```
+  </Accordion>
+</AccordionGroup>

apps/docs/archive/configuration.mdx

@@ -0,0 +1,80 @@
+---
+title: "Configuration"
+description: "Configure Task Master through environment variables in a .env file"
+---
+
+## Required Configuration
+
+<Note>
+  Task Master requires an Anthropic API key to function. Add this to your `.env` file:
+
+  ```bash
+  ANTHROPIC_API_KEY=sk-ant-api03-your-api-key
+  ```
+
+  You can obtain an API key from the [Anthropic Console](https://console.anthropic.com/).
+</Note>
+
+## Optional Configuration
+
+| Variable | Default Value | Description | Example |
+| --- | --- | --- | --- |
+| `MODEL` | `"claude-3-7-sonnet-20250219"` | Claude model to use | `MODEL=claude-3-opus-20240229` |
+| `MAX_TOKENS` | `"4000"` | Maximum tokens for responses | `MAX_TOKENS=8000` |
+| `TEMPERATURE` | `"0.7"` | Temperature for model responses | `TEMPERATURE=0.5` |
+| `DEBUG` | `"false"` | Enable debug logging | `DEBUG=true` |
+| `LOG_LEVEL` | `"info"` | Console output level | `LOG_LEVEL=debug` |
+| `DEFAULT_SUBTASKS` | `"3"` | Default subtask count | `DEFAULT_SUBTASKS=5` |
+| `DEFAULT_PRIORITY` | `"medium"` | Default priority | `DEFAULT_PRIORITY=high` |
+| `PROJECT_NAME` | `"MCP SaaS MVP"` | Project name in metadata | `PROJECT_NAME=My Awesome Project` |
+| `PROJECT_VERSION` | `"1.0.0"` | Version in metadata | `PROJECT_VERSION=2.1.0` |
+| `PERPLEXITY_API_KEY` | - | For research-backed features | `PERPLEXITY_API_KEY=pplx-...` |
+| `PERPLEXITY_MODEL` | `"sonar-medium-online"` | Perplexity model | `PERPLEXITY_MODEL=sonar-large-online` |
+
+## Example .env File
+
+```
+# Required
+ANTHROPIC_API_KEY=sk-ant-api03-your-api-key
+
+# Optional - Claude Configuration
+MODEL=claude-3-7-sonnet-20250219
+MAX_TOKENS=4000
+TEMPERATURE=0.7
+
+# Optional - Perplexity API for Research
+PERPLEXITY_API_KEY=pplx-your-api-key
+PERPLEXITY_MODEL=sonar-medium-online
+
+# Optional - Project Info
+PROJECT_NAME=My Project
+PROJECT_VERSION=1.0.0
+
+# Optional - Application Configuration
+DEFAULT_SUBTASKS=3
+DEFAULT_PRIORITY=medium
+DEBUG=false
+LOG_LEVEL=info
+```
+
+## Troubleshooting
+
+### If `task-master init` doesn't respond:
+
+Try running it with Node directly:
+
+```bash
+node node_modules/claude-task-master/scripts/init.js
+```
+
+Or clone the repository and run:
+
+```bash
+git clone https://github.com/eyaltoledano/claude-task-master.git
+cd claude-task-master
+node scripts/init.js
+```
+
+<Note>
+For advanced configuration options and detailed customization, see our [Advanced Configuration Guide] page.
+</Note>

apps/docs/archive/cursor-setup.mdx

@@ -0,0 +1,95 @@
+---
+title: "Cursor AI Integration"
+description: "Learn how to set up and use Task Master with Cursor AI"
+---
+
+## Setting up Cursor AI Integration
+
+<Check>
+  Task Master is designed to work seamlessly with [Cursor AI](https://www.cursor.so/), providing a structured workflow for AI-driven development.
+</Check>
+
+<AccordionGroup>
+  <Accordion title="Using Cursor with MCP (Recommended)" icon="sparkles">
+    If you've already set up Task Master with MCP in Cursor, the integration is automatic. You can simply use natural language to interact with Task Master:
+
+    ```
+    What tasks are available to work on next?
+    Can you analyze the complexity of our tasks?
+    I'd like to implement task 4. What does it involve?
+    ```
+  </Accordion>
+  <Accordion title="Manual Cursor Setup">
+    If you're not using MCP, you can still set up Cursor integration:
+
+    <Steps>
+      <Step title="After initializing your project, open it in Cursor">
+        The `.cursor/rules/dev_workflow.mdc` file is automatically loaded by Cursor, providing the AI with knowledge about the task management system
+      </Step>
+      <Step title="Place your PRD document in the scripts/ directory (e.g., scripts/prd.txt)">
+        
+      </Step>
+      <Step title="Open Cursor's AI chat and switch to Agent mode">
+        
+      </Step>
+    </Steps>
+  </Accordion>
+  <Accordion title="Alternative MCP Setup in Cursor">
+    <Steps>
+      <Step title="Go to Cursor settings">
+        
+      </Step>
+      <Step title="Navigate to the MCP section">
+        
+      </Step>
+      <Step title="Click on 'Add New MCP Server'">
+        
+      </Step>
+      <Step title="Configure with the following details:">
+        - Name: "Task Master"
+        - Type: "Command"
+        - Command: "npx -y --package task-master-ai task-master-mcp"
+      </Step>
+      <Step title="Save Settings">
+        
+      </Step>
+    </Steps>
+    Once configured, you can interact with Task Master's task management commands directly through Cursor's interface, providing a more integrated experience.
+  </Accordion>
+</AccordionGroup>
+
+## Initial Task Generation
+
+In Cursor's AI chat, instruct the agent to generate tasks from your PRD:
+
+```
+Please use the task-master parse-prd command to generate tasks from my PRD. The PRD is located at scripts/prd.txt.
+```
+
+The agent will execute:
+
+```bash
+task-master parse-prd scripts/prd.txt
+```
+
+This will:
+
+- Parse your PRD document
+- Generate a structured `tasks.json` file with tasks, dependencies, priorities, and test strategies
+- The agent will understand this process due to the Cursor rules
+
+### Generate Individual Task Files
+
+Next, ask the agent to generate individual task files:
+
+```
+Please generate individual task files from tasks.json
+```
+
+The agent will execute:
+
+```bash
+task-master generate
+```
+
+This creates individual task files in the `tasks/` directory (e.g., `task_001.txt`, `task_002.txt`), making it easier to reference specific tasks.

apps/docs/archive/examples.mdx

@@ -0,0 +1,56 @@
+---
+title: "Example Cursor AI Interactions"
+description: "Below are some common interactions with Cursor AI when using Task Master"
+---
+
+<AccordionGroup>
+  <Accordion title="Starting a new project">
+    ```
+    I've just initialized a new project with Claude Task Master. I have a PRD at scripts/prd.txt.
+    Can you help me parse it and set up the initial tasks?
+    ```
+  </Accordion>
+
+  <Accordion title="Working on tasks">
+    ```
+    What's the next task I should work on? Please consider dependencies and priorities.
+    ```
+  </Accordion>
+
+  <Accordion title="Implementing a specific task">
+    ```
+    I'd like to implement task 4. Can you help me understand what needs to be done and how to approach it?
+    ```
+  </Accordion>
+
+  <Accordion title="Managing subtasks">
+    ```
+    I need to regenerate the subtasks for task 3 with a different approach. Can you help me clear and regenerate them?
+    ```
+  </Accordion>
+
+  <Accordion title="Handling changes">
+    ```
+    We've decided to use MongoDB instead of PostgreSQL. Can you update all future tasks to reflect this change?
+    ```
+  </Accordion>
+
+  <Accordion title="Completing work">
+    ```
+    I've finished implementing the authentication system described in task 2. All tests are passing.
+    Please mark it as complete and tell me what I should work on next.
+    ```
+  </Accordion>
+
+  <Accordion title="Analyzing complexity">
+    ```
+    Can you analyze the complexity of our tasks to help me understand which ones need to be broken down further?
+    ```
+  </Accordion>
+
+  <Accordion title="Viewing complexity report">
+    ```
+    Can you show me the complexity report in a more readable format?
+    ```
+  </Accordion>
+</AccordionGroup>

apps/docs/best-practices/advanced-tasks.mdx

@@ -0,0 +1,210 @@
+---
+title: Advanced Tasks
+sidebarTitle: "Advanced Tasks"
+---
+
+## AI-Driven Development Workflow
+
+The Cursor agent is pre-configured (via the rules file) to follow this workflow:
+
+### 1. Task Discovery and Selection
+
+Ask the agent to list available tasks:
+
+```
+What tasks are available to work on next?
+```
+
+```
+Can you show me tasks 1, 3, and 5 to understand their current status?
+```
+
+The agent will:
+
+- Run `task-master list` to see all tasks
+- Run `task-master next` to determine the next task to work on
+- Run `task-master show 1,3,5` to display multiple tasks with interactive options
+- Analyze dependencies to determine which tasks are ready to be worked on
+- Prioritize tasks based on priority level and ID order
+- Suggest the next task(s) to implement
+
+### 2. Task Implementation
+
+When implementing a task, the agent will:
+
+- Reference the task's details section for implementation specifics
+- Consider dependencies on previous tasks
+- Follow the project's coding standards
+- Create appropriate tests based on the task's testStrategy
+
+You can ask:
+
+```
+Let's implement task 3. What does it involve?
+```
+
+### 2.1. Viewing Multiple Tasks
+
+For efficient context gathering and batch operations:
+
+```
+Show me tasks 5, 7, and 9 so I can plan my implementation approach.
+```
+
+The agent will:
+
+- Run `task-master show 5,7,9` to display a compact summary table
+- Show task status, priority, and progress indicators
+- Provide an interactive action menu with batch operations
+- Allow you to perform group actions like marking multiple tasks as in-progress
+
+### 3. Task Verification
+
+Before marking a task as complete, verify it according to:
+
+- The task's specified testStrategy
+- Any automated tests in the codebase
+- Manual verification if required
+
+### 4. Task Completion
+
+When a task is completed, tell the agent:
+
+```
+Task 3 is now complete. Please update its status.
+```
+
+The agent will execute:
+
+```bash
+task-master set-status --id=3 --status=done
+```
+
+### 5. Handling Implementation Drift
+
+If during implementation, you discover that:
+
+- The current approach differs significantly from what was planned
+- Future tasks need to be modified due to current implementation choices
+- New dependencies or requirements have emerged
+
+Tell the agent:
+
+```
+We've decided to use MongoDB instead of PostgreSQL. Can you update all future tasks (from ID 4) to reflect this change?
+```
+
+The agent will execute:
+
+```bash
+task-master update --from=4 --prompt="Now we are using MongoDB instead of PostgreSQL."
+
+# OR, if research is needed to find best practices for MongoDB:
+task-master update --from=4 --prompt="Update to use MongoDB, researching best practices" --research
+```
+
+This will rewrite or re-scope subsequent tasks in tasks.json while preserving completed work.
+
+### 6. Reorganizing Tasks
+
+If you need to reorganize your task structure:
+
+```
+I think subtask 5.2 would fit better as part of task 7 instead. Can you move it there?
+```
+
+The agent will execute:
+
+```bash
+task-master move --from=5.2 --to=7.3
+```
+
+You can reorganize tasks in various ways:
+
+- Moving a standalone task to become a subtask: `--from=5 --to=7`
+- Moving a subtask to become a standalone task: `--from=5.2 --to=7`
+- Moving a subtask to a different parent: `--from=5.2 --to=7.3`
+- Reordering subtasks within the same parent: `--from=5.2 --to=5.4`
+- Moving a task to a new ID position: `--from=5 --to=25` (even if task 25 doesn't exist yet)
+- Moving multiple tasks at once: `--from=10,11,12 --to=16,17,18` (must have same number of IDs, Taskmaster will look through each position)
+
+When moving tasks to new IDs:
+
+- The system automatically creates placeholder tasks for non-existent destination IDs
+- This prevents accidental data loss during reorganization
+- Any tasks that depend on moved tasks will have their dependencies updated
+- When moving a parent task, all its subtasks are automatically moved with it and renumbered
+
+This is particularly useful as your project understanding evolves and you need to refine your task structure.
+
+### 7. Resolving Merge Conflicts with Tasks
+
+When working with a team, you might encounter merge conflicts in your tasks.json file if multiple team members create tasks on different branches. The move command makes resolving these conflicts straightforward:
+
+```
+I just merged the main branch and there's a conflict with tasks.json. My teammates created tasks 10-15 while I created tasks 10-12 on my branch. Can you help me resolve this?
+```
+
+The agent will help you:
+
+1. Keep your teammates' tasks (10-15)
+2. Move your tasks to new positions to avoid conflicts:
+
+```bash
+# Move your tasks to new positions (e.g., 16-18)
+task-master move --from=10 --to=16
+task-master move --from=11 --to=17
+task-master move --from=12 --to=18
+```
+
+This approach preserves everyone's work while maintaining a clean task structure, making it much easier to handle task conflicts than trying to manually merge JSON files.
+
+### 8. Breaking Down Complex Tasks
+
+For complex tasks that need more granularity:
+
+```
+Task 5 seems complex. Can you break it down into subtasks?
+```
+
+The agent will execute:
+
+```bash
+task-master expand --id=5 --num=3
+```
+
+You can provide additional context:
+
+```
+Please break down task 5 with a focus on security considerations.
+```
+
+The agent will execute:
+
+```bash
+task-master expand --id=5 --prompt="Focus on security aspects"
+```
+
+You can also expand all pending tasks:
+
+```
+Please break down all pending tasks into subtasks.
+```
+
+The agent will execute:
+
+```bash
+task-master expand --all
+```
+
+For research-backed subtask generation using the configured research model:
+
+```
+Please break down task 5 using research-backed generation.
+```
+
+The agent will execute:
+
+```bash
+task-master expand --id=5 --research
+```

apps/docs/best-practices/configuration-advanced.mdx

@@ -0,0 +1,317 @@
+---
+title: Advanced Configuration
+sidebarTitle: "Advanced Configuration"
+---
+
+
+Taskmaster uses two primary methods for configuration:
+
+1.  **`.taskmaster/config.json` File (Recommended - New Structure)**
+
+    - This JSON file stores most configuration settings, including AI model selections, parameters, logging levels, and project defaults.
+    - **Location:** This file is created in the `.taskmaster/` directory when you run the `task-master models --setup` interactive setup or initialize a new project with `task-master init`.
+    - **Migration:** Existing projects with `.taskmasterconfig` in the root will continue to work, but should be migrated to the new structure using `task-master migrate`.
+    - **Management:** Use the `task-master models --setup` command (or `models` MCP tool) to interactively create and manage this file. You can also set specific models directly using `task-master models --set-<role>=<model_id>`, adding `--ollama` or `--openrouter` flags for custom models. Manual editing is possible but not recommended unless you understand the structure.
+    - **Example Structure:**
+      ```json
+      {
+        "models": {
+          "main": {
+            "provider": "anthropic",
+            "modelId": "claude-3-7-sonnet-20250219",
+            "maxTokens": 64000,
+            "temperature": 0.2,
+            "baseURL": "https://api.anthropic.com/v1"
+          },
+          "research": {
+            "provider": "perplexity",
+            "modelId": "sonar-pro",
+            "maxTokens": 8700,
+            "temperature": 0.1,
+            "baseURL": "https://api.perplexity.ai/v1"
+          },
+          "fallback": {
+            "provider": "anthropic",
+            "modelId": "claude-3-5-sonnet",
+            "maxTokens": 64000,
+            "temperature": 0.2
+          }
+        },
+        "global": {
+          "logLevel": "info",
+          "debug": false,
+          "defaultSubtasks": 5,
+          "defaultPriority": "medium",
+          "defaultTag": "master",
+          "projectName": "Your Project Name",
+          "ollamaBaseURL": "http://localhost:11434/api",
+          "azureBaseURL": "https://your-endpoint.azure.com/openai/deployments",
+          "vertexProjectId": "your-gcp-project-id",
+          "vertexLocation": "us-central1"
+        }
+      }
+      ```
+
+
+2.  **Legacy `.taskmasterconfig` File (Backward Compatibility)**
+
+    - For projects that haven't migrated to the new structure yet.
+    - **Location:** Project root directory.
+    - **Migration:** Use `task-master migrate` to move this to `.taskmaster/config.json`.
+    - **Deprecation:** While still supported, you'll see warnings encouraging migration to the new structure.
+
+## Environment Variables (`.env` file or MCP `env` block - For API Keys Only)
+
+- Used **exclusively** for sensitive API keys and specific endpoint URLs.
+- **Location:**
+  - For CLI usage: Create a `.env` file in your project root.
+  - For MCP/Cursor usage: Configure keys in the `env` section of your `.cursor/mcp.json` file.
+- **Required API Keys (Depending on configured providers):**
+  - `ANTHROPIC_API_KEY`: Your Anthropic API key.
+  - `PERPLEXITY_API_KEY`: Your Perplexity API key.
+  - `OPENAI_API_KEY`: Your OpenAI API key.
+  - `GOOGLE_API_KEY`: Your Google API key (also used for Vertex AI provider).
+  - `MISTRAL_API_KEY`: Your Mistral API key.
+  - `AZURE_OPENAI_API_KEY`: Your Azure OpenAI API key (also requires `AZURE_OPENAI_ENDPOINT`).
+  - `OPENROUTER_API_KEY`: Your OpenRouter API key.
+  - `XAI_API_KEY`: Your X-AI API key.
+- **Optional Endpoint Overrides:**
+  - **Per-role `baseURL` in `.taskmasterconfig`:** You can add a `baseURL` property to any model role (`main`, `research`, `fallback`) to override the default API endpoint for that provider. If omitted, the provider's standard endpoint is used.
+  - **Environment Variable Overrides (`<PROVIDER>_BASE_URL`):** For greater flexibility, especially with third-party services, you can set an environment variable like `OPENAI_BASE_URL` or `MISTRAL_BASE_URL`. This will override any `baseURL` set in the configuration file for that provider. This is the recommended way to connect to OpenAI-compatible APIs.
+  - `AZURE_OPENAI_ENDPOINT`: Required if using Azure OpenAI key (can also be set as `baseURL` for the Azure model role).
+  - `OLLAMA_BASE_URL`: Override the default Ollama API URL (Default: `http://localhost:11434/api`).
+  - `VERTEX_PROJECT_ID`: Your Google Cloud project ID for Vertex AI. Required when using the 'vertex' provider.
+  - `VERTEX_LOCATION`: Google Cloud region for Vertex AI (e.g., 'us-central1'). Default is 'us-central1'.
+  - `GOOGLE_APPLICATION_CREDENTIALS`: Path to service account credentials JSON file for Google Cloud auth (alternative to API key for Vertex AI).
+
+**Important:** Settings like model ID selections (`main`, `research`, `fallback`), `maxTokens`, `temperature`, `logLevel`, `defaultSubtasks`, `defaultPriority`, and `projectName` are **managed in `.taskmaster/config.json`** (or `.taskmasterconfig` for unmigrated projects), not environment variables.
+
+## Tagged Task Lists Configuration (v0.17+)
+
+Taskmaster includes a tagged task lists system for multi-context task management.
+
+### Global Tag Settings
+
+```json
+"global": {
+  "defaultTag": "master"
+}
+```
+
+- **`defaultTag`** (string): Default tag context for new operations (default: "master")
+
+### Git Integration
+
+Task Master provides manual git integration through the `--from-branch` option:
+
+- **Manual Tag Creation**: Use `task-master add-tag --from-branch` to create a tag based on your current git branch name
+- **User Control**: No automatic tag switching - you control when and how tags are created
+- **Flexible Workflow**: Supports any git workflow without imposing rigid branch-tag mappings
+
+## State Management File
+
+Taskmaster uses `.taskmaster/state.json` to track tagged system runtime information:
+
+```json
+{
+  "currentTag": "master",
+  "lastSwitched": "2025-06-11T20:26:12.598Z",
+  "migrationNoticeShown": true
+}
+```
+
+- **`currentTag`**: Currently active tag context
+- **`lastSwitched`**: Timestamp of last tag switch
+- **`migrationNoticeShown`**: Whether migration notice has been displayed
+
+This file is automatically created during tagged system migration and should not be manually edited.
+
+## Example `.env` File (for API Keys)
+
+```
+# Required API keys for providers configured in .taskmaster/config.json
+ANTHROPIC_API_KEY=sk-ant-api03-your-key-here
+PERPLEXITY_API_KEY=pplx-your-key-here
+# OPENAI_API_KEY=sk-your-key-here
+# GOOGLE_API_KEY=AIzaSy...
+# AZURE_OPENAI_API_KEY=your-azure-openai-api-key-here
+# etc.
+
+# Optional Endpoint Overrides
+# Use a specific provider's base URL, e.g., for an OpenAI-compatible API
+# OPENAI_BASE_URL=https://api.third-party.com/v1
+#
+# Azure OpenAI Configuration
+# AZURE_OPENAI_ENDPOINT=https://your-resource-name.openai.azure.com/ or https://your-endpoint-name.cognitiveservices.azure.com/openai/deployments
+# OLLAMA_BASE_URL=http://custom-ollama-host:11434/api
+
+# Google Vertex AI Configuration (Required if using 'vertex' provider)
+# VERTEX_PROJECT_ID=your-gcp-project-id
+```
+
+## Troubleshooting
+
+### Configuration Errors
+
+- If Task Master reports errors about missing configuration or cannot find the config file, run `task-master models --setup` in your project root to create or repair the file.
+- For new projects, config will be created at `.taskmaster/config.json`. For legacy projects, you may want to use `task-master migrate` to move to the new structure.
+- Ensure API keys are correctly placed in your `.env` file (for CLI) or `.cursor/mcp.json` (for MCP) and are valid for the providers selected in your config file.
+
+### If `task-master init` doesn't respond:
+
+Try running it with Node directly:
+
+```bash
+node node_modules/claude-task-master/scripts/init.js
+```
+
+Or clone the repository and run:
+
+```bash
+git clone https://github.com/eyaltoledano/claude-task-master.git
+cd claude-task-master
+node scripts/init.js
+```
+
+## Provider-Specific Configuration
+
+### Google Vertex AI Configuration
+
+Google Vertex AI is Google Cloud's enterprise AI platform and requires specific configuration:
+
+1. **Prerequisites**:
+   - A Google Cloud account with Vertex AI API enabled
+   - Either a Google API key with Vertex AI permissions OR a service account with appropriate roles
+   - A Google Cloud project ID
+2. **Authentication Options**:
+   - **API Key**: Set the `GOOGLE_API_KEY` environment variable
+   - **Service Account**: Set `GOOGLE_APPLICATION_CREDENTIALS` to point to your service account JSON file
+3. **Required Configuration**:
+   - Set `VERTEX_PROJECT_ID` to your Google Cloud project ID
+   - Set `VERTEX_LOCATION` to your preferred Google Cloud region (default: us-central1)
+4. **Example Setup**:
+
+   ```bash
+   # In .env file
+   GOOGLE_API_KEY=AIzaSyXXXXXXXXXXXXXXXXXXXXXXXXX
+   VERTEX_PROJECT_ID=my-gcp-project-123
+   VERTEX_LOCATION=us-central1
+   ```
+
+   Or using service account:
+
+   ```bash
+   # In .env file
+   GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json
+   VERTEX_PROJECT_ID=my-gcp-project-123
+   VERTEX_LOCATION=us-central1
+   ```
+
+5. **In .taskmaster/config.json**:
+   ```json
+   "global": {
+     "vertexProjectId": "my-gcp-project-123",
+     "vertexLocation": "us-central1"
+   }
+   ```
+
+### Azure OpenAI Configuration
+
+Azure OpenAI provides enterprise-grade OpenAI models through Microsoft's Azure cloud platform and requires specific configuration:
+
+1. **Prerequisites**:
+   - An Azure account with an active subscription
+   - Azure OpenAI service resource created in the Azure portal
+   - Azure OpenAI API key and endpoint URL
+   - Deployed models (e.g., gpt-4o, gpt-4o-mini, gpt-4.1, etc) in your Azure OpenAI resource
+
+2. **Authentication**:
+   - Set the `AZURE_OPENAI_API_KEY` environment variable with your Azure OpenAI API key
+   - Configure the endpoint URL using one of the methods below
+
+3. **Configuration Options**:
+
+   **Option 1: Using Global Azure Base URL (affects all Azure models)**
+   ```json
+   // In .taskmaster/config.json
+   {
+     "models": {
+       "main": {
+         "provider": "azure",
+         "modelId": "gpt-4o",
+         "maxTokens": 16000,
+         "temperature": 0.7
+       },
+       "fallback": {
+         "provider": "azure", 
+         "modelId": "gpt-4o-mini",
+         "maxTokens": 10000,
+         "temperature": 0.7
+       }
+     },
+     "global": {
+       "azureBaseURL": "https://your-resource-name.azure.com/openai/deployments"
+     }
+   }
+   ```
+
+   **Option 2: Using Per-Model Base URLs (recommended for flexibility)**
+   ```json
+   // In .taskmaster/config.json
+   {
+     "models": {
+       "main": {
+         "provider": "azure",
+         "modelId": "gpt-4o", 
+         "maxTokens": 16000,
+         "temperature": 0.7,
+         "baseURL": "https://your-resource-name.azure.com/openai/deployments"
+       },
+       "research": {
+         "provider": "perplexity",
+         "modelId": "sonar-pro",
+         "maxTokens": 8700,
+         "temperature": 0.1
+       },
+       "fallback": {
+         "provider": "azure",
+         "modelId": "gpt-4o-mini",
+         "maxTokens": 10000, 
+         "temperature": 0.7,
+         "baseURL": "https://your-resource-name.azure.com/openai/deployments"
+       }
+     }
+   }
+   ```
+
+4. **Environment Variables**:
+   ```bash
+   # In .env file
+   AZURE_OPENAI_API_KEY=your-azure-openai-api-key-here
+   
+   # Optional: Override endpoint for all Azure models
+   AZURE_OPENAI_ENDPOINT=https://your-resource-name.azure.com/openai/deployments
+   ```
+
+5. **Important Notes**:
+   - **Model Deployment Names**: The `modelId` in your configuration should match the **deployment name** you created in Azure OpenAI Studio, not the underlying model name
+   - **Base URL Priority**: Per-model `baseURL` settings override the global `azureBaseURL` setting
+   - **Endpoint Format**: When using per-model `baseURL`, use the full path including `/openai/deployments`
+
+6. **Troubleshooting**:
+
+   **"Resource not found" errors:**
+   - Ensure your `baseURL` includes the full path: `https://your-resource-name.openai.azure.com/openai/deployments`
+   - Verify that your deployment name in `modelId` exactly matches what's configured in Azure OpenAI Studio
+   - Check that your Azure OpenAI resource is in the correct region and properly deployed
+
+   **Authentication errors:**
+   - Verify your `AZURE_OPENAI_API_KEY` is correct and has not expired
+   - Ensure your Azure OpenAI resource has the necessary permissions
+   - Check that your subscription has not been suspended or reached quota limits
+
+   **Model availability errors:**
+   - Confirm the model is deployed in your Azure OpenAI resource
+   - Verify the deployment name matches your configuration exactly (case-sensitive)
+   - Ensure the model deployment is in a "Succeeded" state in Azure OpenAI Studio
+   - Ensure youre not getting rate limited by `maxTokens` maintain appropriate Tokens per Minute Rate Limit (TPM) in your deployment.

apps/docs/best-practices/index.mdx

@@ -0,0 +1,8 @@
+---
+title: Intro to Advanced Usage
+sidebarTitle: "Advanced Usage"
+---
+
+# Best Practices
+
+Explore advanced tips, recommended workflows, and best practices for getting the most out of Task Master. 

apps/docs/capabilities/cli-root-commands.mdx

@@ -0,0 +1,209 @@
+---
+title: CLI Commands
+sidebarTitle: "CLI Commands"
+---
+
+
+<AccordionGroup>
+  <Accordion title="Parse PRD">
+    ```bash
+    # Parse a PRD file and generate tasks
+    task-master parse-prd <prd-file.txt>
+
+    # Limit the number of tasks generated
+    task-master parse-prd <prd-file.txt> --num-tasks=10
+    ```
+  </Accordion>
+
+  <Accordion title="List Tasks">
+    ```bash
+    # List all tasks
+    task-master list
+
+    # List tasks with a specific status
+    task-master list --status=<status>
+
+    # List tasks with subtasks
+    task-master list --with-subtasks
+
+    # List tasks with a specific status and include subtasks
+    task-master list --status=<status> --with-subtasks
+    ```
+  </Accordion>
+
+  <Accordion title="Show Next Task">
+    ```bash
+    # Show the next task to work on based on dependencies and status
+    task-master next
+    ```
+  </Accordion>
+
+  <Accordion title="Show Specific Task">
+    ```bash
+    # Show details of a specific task
+    task-master show <id>
+    # or
+    task-master show --id=<id>
+
+    # View a specific subtask (e.g., subtask 2 of task 1)
+    task-master show 1.2
+    ```
+  </Accordion>
+
+  <Accordion title="Update Tasks">
+    ```bash
+    # Update tasks from a specific ID and provide context
+    task-master update --from=<id> --prompt="<prompt>"
+    ```
+  </Accordion>
+
+  <Accordion title="Update a Specific Task">
+    ```bash
+    # Update a single task by ID with new information
+    task-master update-task --id=<id> --prompt="<prompt>"
+
+    # Use research-backed updates with Perplexity AI
+    task-master update-task --id=<id> --prompt="<prompt>" --research
+    ```
+  </Accordion>
+
+  <Accordion title="Update a Subtask">
+    ```bash
+    # Append additional information to a specific subtask
+    task-master update-subtask --id=<parentId.subtaskId> --prompt="<prompt>"
+
+    # Example: Add details about API rate limiting to subtask 2 of task 5
+    task-master update-subtask --id=5.2 --prompt="Add rate limiting of 100 requests per minute"
+
+    # Use research-backed updates with Perplexity AI
+    task-master update-subtask --id=<parentId.subtaskId> --prompt="<prompt>" --research
+    ```
+
+    Unlike the `update-task` command which replaces task information, the `update-subtask` command _appends_ new information to the existing subtask details, marking it with a timestamp. This is useful for iteratively enhancing subtasks while preserving the original content.
+  </Accordion>
+
+  <Accordion title="Generate Task Files">
+    ```bash
+    # Generate individual task files from tasks.json
+    task-master generate
+    ```
+  </Accordion>
+
+  <Accordion title="Set Task Status">
+    ```bash
+    # Set status of a single task
+    task-master set-status --id=<id> --status=<status>
+
+    # Set status for multiple tasks
+    task-master set-status --id=1,2,3 --status=<status>
+
+    # Set status for subtasks
+    task-master set-status --id=1.1,1.2 --status=<status>
+    ```
+
+    When marking a task as "done", all of its subtasks will automatically be marked as "done" as well.
+  </Accordion>
+
+  <Accordion title="Expand Tasks">
+    ```bash
+    # Expand a specific task with subtasks
+    task-master expand --id=<id> --num=<number>
+
+    # Expand with additional context
+    task-master expand --id=<id> --prompt="<context>"
+
+    # Expand all pending tasks
+    task-master expand --all
+
+    # Force regeneration of subtasks for tasks that already have them
+    task-master expand --all --force
+
+    # Research-backed subtask generation for a specific task
+    task-master expand --id=<id> --research
+
+    # Research-backed generation for all tasks
+    task-master expand --all --research
+    ```
+  </Accordion>
+
+  <Accordion title="Clear Subtasks">
+    ```bash
+    # Clear subtasks from a specific task
+    task-master clear-subtasks --id=<id>
+
+    # Clear subtasks from multiple tasks
+    task-master clear-subtasks --id=1,2,3
+
+    # Clear subtasks from all tasks
+    task-master clear-subtasks --all
+    ```
+  </Accordion>
+
+  <Accordion title="Analyze Task Complexity">
+    ```bash
+    # Analyze complexity of all tasks
+    task-master analyze-complexity
+
+    # Save report to a custom location
+    task-master analyze-complexity --output=my-report.json
+
+    # Use a specific LLM model
+    task-master analyze-complexity --model=claude-3-opus-20240229
+
+    # Set a custom complexity threshold (1-10)
+    task-master analyze-complexity --threshold=6
+
+    # Use an alternative tasks file
+    task-master analyze-complexity --file=custom-tasks.json
+
+    # Use Perplexity AI for research-backed complexity analysis
+    task-master analyze-complexity --research
+    ```
+  </Accordion>
+
+  <Accordion title="View Complexity Report">
+    ```bash
+    # Display the task complexity analysis report
+    task-master complexity-report
+
+    # View a report at a custom location
+    task-master complexity-report --file=my-report.json
+    ```
+  </Accordion>
+
+  <Accordion title="Managing Task Dependencies">
+    ```bash
+    # Add a dependency to a task
+    task-master add-dependency --id=<id> --depends-on=<id>
+
+    # Remove a dependency from a task
+    task-master remove-dependency --id=<id> --depends-on=<id>
+
+    # Validate dependencies without fixing them
+    task-master validate-dependencies
+
+    # Find and fix invalid dependencies automatically
+    task-master fix-dependencies
+    ```
+  </Accordion>
+
+  <Accordion title="Add a New Task">
+    ```bash
+    # Add a new task using AI
+    task-master add-task --prompt="Description of the new task"
+
+    # Add a task with dependencies
+    task-master add-task --prompt="Description" --dependencies=1,2,3
+
+    # Add a task with priority
+    task-master add-task --prompt="Description" --priority=high
+    ```
+  </Accordion>
+
+  <Accordion title="Initialize a Project">
+    ```bash
+    # Initialize a new project with Task Master structure
+    task-master init
+    ```
+  </Accordion>
+</AccordionGroup>

apps/docs/capabilities/index.mdx

@@ -0,0 +1,241 @@
+---
+title: Technical Capabilities
+sidebarTitle: "Technical Capabilities"
+---
+
+# Capabilities (Technical)
+
+Discover the technical capabilities of Task Master, including supported models, integrations, and more. 
+
+# CLI Interface Synopsis
+
+This document outlines the command-line interface (CLI) for the Task Master application, as defined in `bin/task-master.js` and the `scripts/modules/commands.js` file (which I will assume exists based on the context). This guide is intended for those writing user-facing documentation to understand how users interact with the application from the command line.
+
+## Entry Point
+
+The main entry point for the CLI is the `task-master` command, which is an executable script that spawns the main application logic in `scripts/dev.js`.
+
+## Global Options
+
+The following options are available for all commands:
+
+-   `-h, --help`: Display help information.
+-   `--version`: Display the application's version.
+
+## Commands
+
+The CLI is organized into a series of commands, each with its own set of options. The following is a summary of the available commands, categorized by their functionality.
+
+### 1. Task and Subtask Management
+
+-   **`add`**: Creates a new task using an AI-powered prompt.
+    -   `--prompt <prompt>`: The prompt to use for generating the task.
+    -   `--dependencies <dependencies>`: A comma-separated list of task IDs that this task depends on.
+    -   `--priority <priority>`: The priority of the task (e.g., `high`, `medium`, `low`).
+-   **`add-subtask`**: Adds a subtask to a parent task.
+    -   `--parent-id <parentId>`: The ID of the parent task.
+    -   `--task-id <taskId>`: The ID of an existing task to convert to a subtask.
+    -   `--title <title>`: The title of the new subtask.
+-   **`remove`**: Removes one or more tasks or subtasks.
+    -   `--ids <ids>`: A comma-separated list of task or subtask IDs to remove.
+-   **`remove-subtask`**: Removes a subtask from its parent.
+    -   `--id <subtaskId>`: The ID of the subtask to remove (in the format `parentId.subtaskId`).
+    -   `--convert-to-task`: Converts the subtask to a standalone task.
+-   **`update`**: Updates multiple tasks starting from a specific ID.
+    -   `--from <fromId>`: The ID of the task to start updating from.
+    -   `--prompt <prompt>`: The new context to apply to the tasks.
+-   **`update-task`**: Updates a single task.
+    -   `--id <taskId>`: The ID of the task to update.
+    -   `--prompt <prompt>`: The new context to apply to the task.
+-   **`update-subtask`**: Appends information to a subtask.
+    -   `--id <subtaskId>`: The ID of the subtask to update (in the format `parentId.subtaskId`).
+    -   `--prompt <prompt>`: The information to append to the subtask.
+-   **`move`**: Moves a task or subtask.
+    -   `--from <sourceId>`: The ID of the task or subtask to move.
+    -   `--to <destinationId>`: The destination ID.
+-   **`clear-subtasks`**: Clears all subtasks from one or more tasks.
+    -   `--ids <ids>`: A comma-separated list of task IDs.
+
+### 2. Task Information and Status
+
+-   **`list`**: Lists all tasks.
+    -   `--status <status>`: Filters tasks by status.
+    -   `--with-subtasks`: Includes subtasks in the list.
+-   **`show`**: Shows the details of a specific task.
+    -   `--id <taskId>`: The ID of the task to show.
+-   **`next`**: Shows the next task to work on.
+-   **`set-status`**: Sets the status of a task or subtask.
+    -   `--id <id>`: The ID of the task or subtask.
+    -   `--status <status>`: The new status.
+
+### 3. Task Analysis and Expansion
+
+-   **`parse-prd`**: Parses a PRD to generate tasks.
+    -   `--file <file>`: The path to the PRD file.
+    -   `--num-tasks <numTasks>`: The number of tasks to generate.
+-   **`expand`**: Expands a task into subtasks.
+    -   `--id <taskId>`: The ID of the task to expand.
+    -   `--num-subtasks <numSubtasks>`: The number of subtasks to generate.
+-   **`expand-all`**: Expands all eligible tasks.
+    -   `--num-subtasks <numSubtasks>`: The number of subtasks to generate for each task.
+-   **`analyze-complexity`**: Analyzes task complexity.
+    -   `--file <file>`: The path to the tasks file.
+-   **`complexity-report`**: Displays the complexity analysis report.
+
+### 4. Project and Configuration
+
+-   **`init`**: Initializes a new project.
+-   **`generate`**: Generates individual task files.
+-   **`migrate`**: Migrates a project to the new directory structure.
+-   **`research`**: Performs AI-powered research.
+    -   `--query <query>`: The research query.
+
+This synopsis provides a comprehensive overview of the CLI commands and their options, which should be helpful for creating user-facing documentation.
+
+
+# Core Implementation Synopsis
+
+This document provides a high-level overview of the core implementation of the Task Master application, focusing on the functionalities exposed through `scripts/modules/task-manager.js`. This serves as a guide for understanding the application's capabilities when writing user-facing documentation.
+
+## Core Concepts
+
+The application revolves around the management of tasks and subtasks, which are stored in a `tasks.json` file. The core logic provides functionalities to create, read, update, and delete tasks and subtasks, as well as manage their dependencies and statuses.
+
+### Task Structure
+
+A task is a JSON object with the following key properties:
+
+-   `id`: A unique number identifying the task.
+-   `title`: A string representing the task's title.
+-   `description`: A string providing a brief description of the task.
+-   `details`: A string containing detailed information about the task.
+-   `testStrategy`: A string describing how to test the task.
+-   `status`: A string representing the task's current status (e.g., `pending`, `in-progress`, `done`).
+-   `dependencies`: An array of task IDs that this task depends on.
+-   `priority`: A string representing the task's priority (e.g., `high`, `medium`, `low`).
+-   `subtasks`: An array of subtask objects.
+
+A subtask has a similar structure to a task but is nested within a parent task.
+
+## Feature Categories
+
+The core functionalities can be categorized as follows:
+
+### 1. Task and Subtask Management
+
+These functions are the bread and butter of the application, allowing for the creation, modification, and deletion of tasks and subtasks.
+
+-   **`addTask(prompt, dependencies, priority)`**: Creates a new task using an AI-powered prompt to generate the title, description, details, and test strategy. It can also be used to create a task manually by providing the task data directly.
+-   **`addSubtask(parentId, existingTaskId, newSubtaskData)`**: Adds a subtask to a parent task. It can either convert an existing task into a subtask or create a new subtask from scratch.
+-   **`removeTask(taskIds)`**: Removes one or more tasks or subtasks.
+-   **`removeSubtask(subtaskId, convertToTask)`**: Removes a subtask from its parent. It can optionally convert the subtask into a standalone task.
+-   **`updateTaskById(taskId, prompt)`**: Updates a task's information based on a prompt.
+-   **`updateSubtaskById(subtaskId, prompt)`**: Appends additional information to a subtask's details.
+-   **`updateTasks(fromId, prompt)`**: Updates multiple tasks starting from a specific ID based on a new context.
+-   **`moveTask(sourceId, destinationId)`**: Moves a task or subtask to a new position.
+-   **`clearSubtasks(taskIds)`**: Clears all subtasks from one or more tasks.
+
+### 2. Task Information and Status
+
+These functions are used to retrieve information about tasks and manage their status.
+
+-   **`listTasks(statusFilter, withSubtasks)`**: Lists all tasks, with options to filter by status and include subtasks.
+-   **`findTaskById(taskId)`**: Finds a task by its ID.
+-   **`taskExists(taskId)`**: Checks if a task with a given ID exists.
+-   **`setTaskStatus(taskIdInput, newStatus)`**: Sets the status of a task or subtask.
+-al
+-   **`updateSingleTaskStatus(taskIdInput, newStatus)`**: A helper function to update the status of a single task or subtask.
+-   **`findNextTask()`**: Determines the next task to work on based on dependencies and status.
+
+### 3. Task Analysis and Expansion
+
+These functions leverage AI to analyze and break down tasks.
+
+-   **`parsePRD(prdPath, numTasks)`**: Parses a Product Requirements Document (PRD) to generate an initial set of tasks.
+-   **`expandTask(taskId, numSubtasks)`**: Expands a task into a specified number of subtasks using AI.
+-   **`expandAllTasks(numSubtasks)`**: Expands all eligible pending or in-progress tasks.
+-   **`analyzeTaskComplexity(options)`**: Analyzes the complexity of tasks and generates recommendations for expansion.
+-   **`readComplexityReport()`**: Reads the complexity analysis report.
+
+### 4. Dependency Management
+
+These functions are crucial for managing the relationships between tasks.
+
+-   **`isTaskDependentOn(task, targetTaskId)`**: Checks if a task has a direct or indirect dependency on another task.
+
+### 5. Project and Configuration
+
+These functions are for managing the project and its configuration.
+
+-   **`generateTaskFiles()`**: Generates individual task files from `tasks.json`.
+-   **`migrateProject()`**: Migrates the project to the new `.taskmaster` directory structure.
+-   **`performResearch(query, options)`**: Performs AI-powered research with project context.
+
+This overview should provide a solid foundation for creating user-facing documentation. For more detailed information on each function, refer to the source code in `scripts/modules/task-manager/`.
+
+
+# MCP Interface Synopsis
+
+This document provides an overview of the MCP (Machine-to-Machine Communication Protocol) interface for the Task Master application. The MCP interface is defined in the `mcp-server/` directory and exposes the application's core functionalities as a set of tools that can be called remotely.
+
+## Core Concepts
+
+The MCP interface is built on top of the `fastmcp` library and registers a set of tools that correspond to the core functionalities of the Task Master application. These tools are defined in the `mcp-server/src/tools/` directory and are registered with the MCP server in `mcp-server/src/tools/index.js`.
+
+Each tool is defined with a name, a description, and a set of parameters that are validated using the `zod` library. The `execute` function of each tool calls the corresponding core logic function from `scripts/modules/task-manager.js`.
+
+## Tool Categories
+
+The MCP tools can be categorized in the same way as the core functionalities:
+
+### 1. Task and Subtask Management
+
+-   **`add_task`**: Creates a new task.
+-   **`add_subtask`**: Adds a subtask to a parent task.
+-   **`remove_task`**: Removes one or more tasks or subtasks.
+-   **`remove_subtask`**: Removes a subtask from its parent.
+-   **`update_task`**: Updates a single task.
+-   **`update_subtask`**: Appends information to a subtask.
+-   **`update`**: Updates multiple tasks.
+-   **`move_task`**: Moves a task or subtask.
+-   **`clear_subtasks`**: Clears all subtasks from one or more tasks.
+
+### 2. Task Information and Status
+
+-   **`get_tasks`**: Lists all tasks.
+-   **`get_task`**: Shows the details of a specific task.
+-   **`next_task`**: Shows the next task to work on.
+-   **`set_task_status`**: Sets the status of a task or subtask.
+
+### 3. Task Analysis and Expansion
+
+-   **`parse_prd`**: Parses a PRD to generate tasks.
+-   **`expand_task`**: Expands a task into subtasks.
+-   **`expand_all`**: Expands all eligible tasks.
+-   **`analyze_project_complexity`**: Analyzes task complexity.
+-   **`complexity_report`**: Displays the complexity analysis report.
+
+### 4. Dependency Management
+
+-   **`add_dependency`**: Adds a dependency to a task.
+-   **`remove_dependency`**: Removes a dependency from a task.
+-   **`validate_dependencies`**: Validates the dependencies of all tasks.
+-   **`fix_dependencies`**: Fixes any invalid dependencies.
+
+### 5. Project and Configuration
+
+-   **`initialize_project`**: Initializes a new project.
+-   **`generate`**: Generates individual task files.
+-   **`models`**: Manages AI model configurations.
+-   **`research`**: Performs AI-powered research.
+
+### 6. Tag Management
+
+-   **`add_tag`**: Creates a new tag.
+-   **`delete_tag`**: Deletes a tag.
+-   **`list_tags`**: Lists all tags.
+-   **`use_tag`**: Switches to a different tag.
+-   **`rename_tag`**: Renames a tag.
+-   **`copy_tag`**: Copies a tag.
+
+This synopsis provides a clear overview of the MCP interface and its available tools, which will be valuable for anyone writing documentation for developers who need to interact with the Task Master application programmatically.

apps/docs/capabilities/mcp.mdx

@@ -0,0 +1,68 @@
+---
+title: MCP Tools
+sidebarTitle: "MCP Tools"
+---
+
+# MCP Tools
+
+This document provides an overview of the MCP (Machine-to-Machine Communication Protocol) interface for the Task Master application. The MCP interface is defined in the `mcp-server/` directory and exposes the application's core functionalities as a set of tools that can be called remotely.
+
+## Core Concepts
+
+The MCP interface is built on top of the `fastmcp` library and registers a set of tools that correspond to the core functionalities of the Task Master application. These tools are defined in the `mcp-server/src/tools/` directory and are registered with the MCP server in `mcp-server/src/tools/index.js`.
+
+Each tool is defined with a name, a description, and a set of parameters that are validated using the `zod` library. The `execute` function of each tool calls the corresponding core logic function from `scripts/modules/task-manager.js`.
+
+## Tool Categories
+
+The MCP tools can be categorized in the same way as the core functionalities:
+
+### 1. Task and Subtask Management
+
+-   **`add_task`**: Creates a new task.
+-   **`add_subtask`**: Adds a subtask to a parent task.
+-   **`remove_task`**: Removes one or more tasks or subtasks.
+-   **`remove_subtask`**: Removes a subtask from its parent.
+-   **`update_task`**: Updates a single task.
+-   **`update_subtask`**: Appends information to a subtask.
+-   **`update`**: Updates multiple tasks.
+-   **`move_task`**: Moves a task or subtask.
+-   **`clear_subtasks`**: Clears all subtasks from one or more tasks.
+
+### 2. Task Information and Status
+
+-   **`get_tasks`**: Lists all tasks.
+-   **`get_task`**: Shows the details of a specific task.
+-   **`next_task`**: Shows the next task to work on.
+-   **`set_task_status`**: Sets the status of a task or subtask.
+
+### 3. Task Analysis and Expansion
+
+-   **`parse_prd`**: Parses a PRD to generate tasks.
+-   **`expand_task`**: Expands a task into subtasks.
+-   **`expand_all`**: Expands all eligible tasks.
+-   **`analyze_project_complexity`**: Analyzes task complexity.
+-   **`complexity_report`**: Displays the complexity analysis report.
+
+### 4. Dependency Management
+
+-   **`add_dependency`**: Adds a dependency to a task.
+-   **`remove_dependency`**: Removes a dependency from a task.
+-   **`validate_dependencies`**: Validates the dependencies of all tasks.
+-   **`fix_dependencies`**: Fixes any invalid dependencies.
+
+### 5. Project and Configuration
+
+-   **`initialize_project`**: Initializes a new project.
+-   **`generate`**: Generates individual task files.
+-   **`models`**: Manages AI model configurations.
+-   **`research`**: Performs AI-powered research.
+
+### 6. Tag Management
+
+-   **`add_tag`**: Creates a new tag.
+-   **`delete_tag`**: Deletes a tag.
+-   **`list_tags`**: Lists all tags.
+-   **`use_tag`**: Switches to a different tag.
+-   **`rename_tag`**: Renames a tag.
+-   **`copy_tag`**: Copies a tag.

apps/docs/capabilities/task-structure.mdx

@@ -0,0 +1,163 @@
+---
+title: "Task Structure"
+sidebarTitle: "Task Structure"
+description: "Tasks in Task Master follow a specific format designed to provide comprehensive information for both humans and AI assistants."
+---
+
+## Task Fields in tasks.json
+
+Tasks in tasks.json have the following structure:
+
+| Field          | Description                                    | Example                                                |
+| -------------- | ---------------------------------------------- | ------------------------------------------------------ |
+| `id`           | Unique identifier for the task.                | `1`                                                    |
+| `title`        | Brief, descriptive title.                      | `"Initialize Repo"`                                    |
+| `description`  | What the task involves.                        | `"Create a new repository, set up initial structure."` |
+| `status`       | Current state.                                 | `"pending"`, `"done"`, `"deferred"`                    |
+| `dependencies` | Prerequisite task IDs. ✅ Completed, ⏱️ Pending | `[1, 2]`                                               |
+| `priority`     | Task importance.                               | `"high"`, `"medium"`, `"low"`                          |
+| `details`      | Implementation instructions.                   | `"Use GitHub client ID/secret, handle callback..."`    |
+| `testStrategy` | How to verify success.                         | `"Deploy and confirm 'Hello World' response."`         |
+| `subtasks`     | Nested subtasks related to the main task.      | `[{"id": 1, "title": "Configure OAuth", ...}]`         |
+
+## Task File Format
+
+Individual task files follow this format:
+
+```
+# Task ID: <id>
+# Title: <title>
+# Status: <status>
+# Dependencies: <comma-separated list of dependency IDs>
+# Priority: <priority>
+# Description: <brief description>
+# Details:
+<detailed implementation notes>
+
+# Test Strategy:
+<verification approach>
+```
+
+## Features in Detail
+
+<AccordionGroup>
+<Accordion title="Analyzing Task Complexity">
+The `analyze-complexity` command:
+
+- Analyzes each task using AI to assess its complexity on a scale of 1-10
+- Recommends optimal number of subtasks based on configured DEFAULT_SUBTASKS
+- Generates tailored prompts for expanding each task
+- Creates a comprehensive JSON report with ready-to-use commands
+- Saves the report to scripts/task-complexity-report.json by default
+
+The generated report contains:
+
+- Complexity analysis for each task (scored 1-10)
+- Recommended number of subtasks based on complexity
+- AI-generated expansion prompts customized for each task
+- Ready-to-run expansion commands directly within each task analysis
+</Accordion>
+
+<Accordion title="Viewing Complexity Report">
+The `complexity-report` command:
+
+- Displays a formatted, easy-to-read version of the complexity analysis report
+- Shows tasks organized by complexity score (highest to lowest)
+- Provides complexity distribution statistics (low, medium, high)
+- Highlights tasks recommended for expansion based on threshold score
+- Includes ready-to-use expansion commands for each complex task
+- If no report exists, offers to generate one on the spot
+</Accordion>
+
+<Accordion title="Smart Task Expansion">
+The `expand` command automatically checks for and uses the complexity report:
+
+When a complexity report exists:
+
+- Tasks are automatically expanded using the recommended subtask count and prompts
+- When expanding all tasks, they're processed in order of complexity (highest first)
+- Research-backed generation is preserved from the complexity analysis
+- You can still override recommendations with explicit command-line options
+
+Example workflow:
+
+```bash
+# Generate the complexity analysis report with research capabilities
+task-master analyze-complexity --research
+
+# Review the report in a readable format
+task-master complexity-report
+
+# Expand tasks using the optimized recommendations
+task-master expand --id=8
+# or expand all tasks
+task-master expand --all
+```
+</Accordion>
+
+<Accordion title="Finding the Next Task">
+The `next` command:
+
+- Identifies tasks that are pending/in-progress and have all dependencies satisfied
+- Prioritizes tasks by priority level, dependency count, and task ID
+- Displays comprehensive information about the selected task:
+  - Basic task details (ID, title, priority, dependencies)
+  - Implementation details
+  - Subtasks (if they exist)
+- Provides contextual suggested actions:
+  - Command to mark the task as in-progress
+  - Command to mark the task as done
+  - Commands for working with subtasks
+</Accordion>
+
+<Accordion title="Viewing Specific Task Details">
+The `show` command:
+
+- Displays comprehensive details about a specific task or subtask
+- Shows task status, priority, dependencies, and detailed implementation notes
+- For parent tasks, displays all subtasks and their status
+- For subtasks, shows parent task relationship
+- Provides contextual action suggestions based on the task's state
+- Works with both regular tasks and subtasks (using the format taskId.subtaskId)
+</Accordion>
+</AccordionGroup>
+
+## Best Practices for AI-Driven Development
+
+<CardGroup cols={2}>
+  <Card title="📝 Detailed PRD" icon="lightbulb">
+    The more detailed your PRD, the better the generated tasks will be.
+  </Card>
+  
+  <Card title="👀 Review Tasks" icon="magnifying-glass">
+    After parsing the PRD, review the tasks to ensure they make sense and have appropriate dependencies.
+  </Card>
+  
+  <Card title="📊 Analyze Complexity" icon="chart-line">
+    Use the complexity analysis feature to identify which tasks should be broken down further.
+  </Card>
+  
+  <Card title="⛓️ Follow Dependencies" icon="link">
+    Always respect task dependencies - the Cursor agent will help with this.
+  </Card>
+  
+  <Card title="🔄 Update As You Go" icon="arrows-rotate">
+    If your implementation diverges from the plan, use the update command to keep future tasks aligned.
+  </Card>
+  
+  <Card title="📦 Break Down Tasks" icon="boxes-stacked">
+    Use the expand command to break down complex tasks into manageable subtasks.
+  </Card>
+  
+  <Card title="🔄 Regenerate Files" icon="file-arrow-up">
+    After any updates to tasks.json, regenerate the task files to keep them in sync.
+  </Card>
+  
+  <Card title="💬 Provide Context" icon="comment">
+    When asking the Cursor agent to help with a task, provide context about what you're trying to achieve.
+  </Card>
+  
+  <Card title="✅ Validate Dependencies" icon="circle-check">
+    Periodically run the validate-dependencies command to check for invalid or circular dependencies.
+  </Card>
+</CardGroup>

apps/docs/docs.json

@@ -0,0 +1,83 @@
+{
+	"$schema": "https://mintlify.com/docs.json",
+	"theme": "mint",
+	"name": "Task Master",
+	"colors": {
+		"primary": "#3366CC",
+		"light": "#6699FF",
+		"dark": "#24478F"
+	},
+	"favicon": "/favicon.svg",
+	"navigation": {
+		"tabs": [
+			{
+				"tab": "Task Master Documentation",
+				"groups": [
+					{
+						"group": "Welcome",
+						"pages": ["introduction"]
+					},
+					{
+						"group": "Getting Started",
+						"pages": [
+							{
+								"group": "Quick Start",
+								"pages": [
+									"getting-started/quick-start/quick-start",
+									"getting-started/quick-start/requirements",
+									"getting-started/quick-start/installation",
+									"getting-started/quick-start/configuration-quick",
+									"getting-started/quick-start/prd-quick",
+									"getting-started/quick-start/tasks-quick",
+									"getting-started/quick-start/execute-quick"
+								]
+							},
+							"getting-started/faq",
+							"getting-started/contribute"
+						]
+					},
+					{
+						"group": "Best Practices",
+						"pages": [
+							"best-practices/index",
+							"best-practices/configuration-advanced",
+							"best-practices/advanced-tasks"
+						]
+					},
+					{
+						"group": "Technical Capabilities",
+						"pages": [
+							"capabilities/mcp",
+							"capabilities/cli-root-commands",
+							"capabilities/task-structure"
+						]
+					}
+				]
+			}
+		],
+		"global": {
+			"anchors": [
+				{
+					"anchor": "Github",
+					"href": "https://github.com/eyaltoledano/claude-task-master",
+					"icon": "github"
+				},
+				{
+					"anchor": "Discord",
+					"href": "https://discord.gg/fWJkU7rf",
+					"icon": "discord"
+				}
+			]
+		}
+	},
+	"logo": {
+		"light": "/logo/task-master-logo.png",
+		"dark": "/logo/task-master-logo.png"
+	},
+	"footer": {
+		"socials": {
+			"x": "https://x.com/TaskmasterAI",
+			"github": "https://github.com/eyaltoledano/claude-task-master"
+		}
+	}
+}

apps/docs/favicon.svg

@@ -0,0 +1,9 @@
+<svg width="100" height="100" viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg">
+  <!-- Blue form with check from logo -->
+  <rect x="16" y="10" width="68" height="80" rx="9" fill="#3366CC"/>
+  <polyline points="33,44 41,55 56,29" fill="none" stroke="#FFFFFF" stroke-width="6"/>
+  <circle cx="33" cy="64" r="4" fill="#FFFFFF"/>
+  <rect x="43" y="61" width="27" height="6" fill="#FFFFFF"/>
+  <circle cx="33" cy="77" r="4" fill="#FFFFFF"/>
+  <rect x="43" y="75" width="27" height="6" fill="#FFFFFF"/>
+</svg>

apps/docs/getting-started/contribute.mdx

@@ -0,0 +1,335 @@
+# Contributing to Task Master
+
+Thank you for your interest in contributing to Task Master! We're excited to work with you and appreciate your help in making this project better. 🚀
+
+## 🤝 Our Collaborative Approach
+
+We're a **PR-friendly team** that values collaboration:
+
+- ✅ **We review PRs quickly** - Usually within hours, not days
+- ✅ **We're super reactive** - Expect fast feedback and engagement
+- ✅ **We sometimes take over PRs** - If your contribution is valuable but needs cleanup, we might jump in to help finish it
+- ✅ **We're open to all contributions** - From bug fixes to major features
+
+**We don't mind AI-generated code**, but we do expect you to:
+
+- ✅ **Review and understand** what the AI generated
+- ✅ **Test the code thoroughly** before submitting
+- ✅ **Ensure it's well-written** and follows our patterns
+- ❌ **Don't submit "AI slop"** - untested, unreviewed AI output
+
+> **Why this matters**: We spend significant time reviewing PRs. Help us help you by submitting quality contributions that save everyone time!
+
+## 🚀 Quick Start for Contributors
+
+### 1. Fork and Clone
+
+```bash
+git clone https://github.com/YOUR_USERNAME/claude-task-master.git
+cd claude-task-master
+npm install
+```
+
+### 2. Create a Feature Branch
+
+**Important**: Always target the `next` branch, not `main`:
+
+```bash
+git checkout next
+git pull origin next
+git checkout -b feature/your-feature-name
+```
+
+### 3. Make Your Changes
+
+Follow our development guidelines below.
+
+### 4. Test Everything Yourself
+
+**Before submitting your PR**, ensure:
+
+```bash
+# Run all tests
+npm test
+
+# Check formatting
+npm run format-check
+
+# Fix formatting if needed
+npm run format
+```
+
+### 5. Create a Changeset
+
+**Required for most changes**:
+
+```bash
+npm run changeset
+```
+
+See the [Changeset Guidelines](#changeset-guidelines) below for details.
+
+### 6. Submit Your PR
+
+- Target the `next` branch
+- Write a clear description
+- Reference any related issues
+
+## 📋 Development Guidelines
+
+### Branch Strategy
+
+- **`main`**: Production-ready code
+- **`next`**: Development branch - **target this for PRs**
+- **Feature branches**: `feature/description` or `fix/description`
+
+### Code Quality Standards
+
+1. **Write tests** for new functionality
+2. **Follow existing patterns** in the codebase
+3. **Add JSDoc comments** for functions
+4. **Keep functions focused** and single-purpose
+
+### Testing Requirements
+
+Your PR **must pass all CI checks**:
+
+- ✅ **Unit tests**: `npm test`
+- ✅ **Format check**: `npm run format-check`
+
+**Test your changes locally first** - this saves review time and shows you care about quality.
+
+## 📦 Changeset Guidelines
+
+We use [Changesets](https://github.com/changesets/changesets) to manage versioning and generate changelogs.
+
+### When to Create a Changeset
+
+**Always create a changeset for**:
+
+- ✅ New features
+- ✅ Bug fixes
+- ✅ Breaking changes
+- ✅ Performance improvements
+- ✅ User-facing documentation updates
+- ✅ Dependency updates that affect functionality
+
+**Skip changesets for**:
+
+- ❌ Internal documentation only
+- ❌ Test-only changes
+- ❌ Code formatting/linting
+- ❌ Development tooling that doesn't affect users
+
+### How to Create a Changeset
+
+1. **After making your changes**:
+
+   ```bash
+   npm run changeset
+   ```
+
+2. **Choose the bump type**:
+
+   - **Major**: Breaking changes
+   - **Minor**: New features
+   - **Patch**: Bug fixes, docs, performance improvements
+
+3. **Write a clear summary**:
+
+   ```
+   Add support for custom AI models in MCP configuration
+   ```
+
+4. **Commit the changeset file** with your changes:
+   ```bash
+   git add .changeset/*.md
+   git commit -m "feat: add custom AI model support"
+   ```
+
+### Changeset vs Git Commit Messages
+
+- **Changeset summary**: User-facing, goes in CHANGELOG.md
+- **Git commit**: Developer-facing, explains the technical change
+
+Example:
+
+```bash
+# Changeset summary (user-facing)
+"Add support for custom Ollama models"
+
+# Git commit message (developer-facing)
+"feat(models): implement custom Ollama model validation
+
+- Add model validation for custom Ollama endpoints
+- Update configuration schema to support custom models
+- Add tests for new validation logic"
+```
+
+## 🔧 Development Setup
+
+### Prerequisites
+
+- Node.js 18+
+- npm or yarn
+
+### Environment Setup
+
+1. **Copy environment template**:
+
+   ```bash
+   cp .env.example .env
+   ```
+
+2. **Add your API keys** (for testing AI features):
+   ```bash
+   ANTHROPIC_API_KEY=your_key_here
+   OPENAI_API_KEY=your_key_here
+   # Add others as needed
+   ```
+
+### Running Tests
+
+```bash
+# Run all tests
+npm test
+
+# Run tests in watch mode
+npm run test:watch
+
+# Run with coverage
+npm run test:coverage
+
+# Run E2E tests
+npm run test:e2e
+```
+
+### Code Formatting
+
+We use Prettier for consistent formatting:
+
+```bash
+# Check formatting
+npm run format-check
+
+# Fix formatting
+npm run format
+```
+
+## 📝 PR Guidelines
+
+### Before Submitting
+
+- [ ] **Target the `next` branch**
+- [ ] **Test everything locally**
+- [ ] **Run the full test suite**
+- [ ] **Check code formatting**
+- [ ] **Create a changeset** (if needed)
+- [ ] **Re-read your changes** - ensure they're clean and well-thought-out
+
+### PR Description Template
+
+```markdown
+## Description
+
+Brief description of what this PR does.
+
+## Type of Change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change
+- [ ] Documentation update
+
+## Testing
+
+- [ ] I have tested this locally
+- [ ] All existing tests pass
+- [ ] I have added tests for new functionality
+
+## Changeset
+
+- [ ] I have created a changeset (or this change doesn't need one)
+
+## Additional Notes
+
+Any additional context or notes for reviewers.
+```
+
+### What We Look For
+
+✅ **Good PRs**:
+
+- Clear, focused changes
+- Comprehensive testing
+- Good commit messages
+- Proper changeset (when needed)
+- Self-reviewed code
+
+❌ **Avoid**:
+
+- Massive PRs that change everything
+- Untested code
+- Formatting issues
+- Missing changesets for user-facing changes
+- AI-generated code that wasn't reviewed
+
+## 🏗️ Project Structure
+
+```
+claude-task-master/
+├── bin/                    # CLI executables
+├── mcp-server/            # MCP server implementation
+├── scripts/               # Core task management logic
+├── src/                   # Shared utilities and providers and well refactored code (we are slowly moving everything here)
+├── tests/                 # Test files
+├── docs/                  # Documentation
+└── .cursor/               # Cursor IDE rules and configuration
+└── assets/							   # Assets like rules and configuration for all IDEs
+```
+
+### Key Areas for Contribution
+
+- **CLI Commands**: `scripts/modules/commands.js`
+- **MCP Tools**: `mcp-server/src/tools/`
+- **Core Logic**: `scripts/modules/task-manager/`
+- **AI Providers**: `src/ai-providers/`
+- **Tests**: `tests/`
+
+## 🐛 Reporting Issues
+
+### Bug Reports
+
+Include:
+
+- Task Master version
+- Node.js version
+- Operating system
+- Steps to reproduce
+- Expected vs actual behavior
+- Error messages/logs
+
+### Feature Requests
+
+Include:
+
+- Clear description of the feature
+- Use case/motivation
+- Proposed implementation (if you have ideas)
+- Willingness to contribute
+
+## 💬 Getting Help
+
+- **Discord**: [Join our community](https://discord.gg/taskmasterai)
+- **Issues**: [GitHub Issues](https://github.com/eyaltoledano/claude-task-master/issues)
+- **Discussions**: [GitHub Discussions](https://github.com/eyaltoledano/claude-task-master/discussions)
+
+## 📄 License
+
+By contributing, you agree that your contributions will be licensed under the same license as the project (MIT with Commons Clause).
+
+---
+
+**Thank you for contributing to Task Master!** 🎉
+
+Your contributions help make AI-driven development more accessible and efficient for everyone.

apps/docs/getting-started/faq.mdx

@@ -0,0 +1,12 @@
+---
+title: FAQ
+sidebarTitle: "FAQ"
+---
+
+Coming soon. 
+
+## 💬 Getting Help
+
+- **Discord**: [Join our community](https://discord.gg/taskmasterai)
+- **Issues**: [GitHub Issues](https://github.com/eyaltoledano/claude-task-master/issues)
+- **Discussions**: [GitHub Discussions](https://github.com/eyaltoledano/claude-task-master/discussions)

apps/docs/getting-started/quick-start/configuration-quick.mdx

@@ -0,0 +1,112 @@
+---
+title: Configuration
+sidebarTitle: "Configuration"
+
+---
+
+Before getting started with Task Master, you'll need to set up your API keys. There are a couple of ways to do this depending on whether you're using the CLI or working inside MCP. It's also a good time to start getting familiar with the other configuration options available — even if you don’t need to adjust them yet, knowing what’s possible will help down the line.
+
+## API Key Setup
+
+Task Master uses environment variables to securely store provider API keys and optional endpoint URLs.
+
+### MCP Usage: mcp.json file
+
+For MCP/Cursor usage: Configure keys in the env section of your .cursor/mcp.json file.
+
+```java .env lines icon="java"
+{
+	"mcpServers": {
+		"task-master-ai": {
+			"command": "node",
+			"args": ["./mcp-server/server.js"],
+			"env": {
+				"ANTHROPIC_API_KEY": "ANTHROPIC_API_KEY_HERE",
+				"PERPLEXITY_API_KEY": "PERPLEXITY_API_KEY_HERE",
+				"OPENAI_API_KEY": "OPENAI_API_KEY_HERE",
+				"GOOGLE_API_KEY": "GOOGLE_API_KEY_HERE",
+				"XAI_API_KEY": "XAI_API_KEY_HERE",
+				"OPENROUTER_API_KEY": "OPENROUTER_API_KEY_HERE",
+				"MISTRAL_API_KEY": "MISTRAL_API_KEY_HERE",
+				"AZURE_OPENAI_API_KEY": "AZURE_OPENAI_API_KEY_HERE",
+				"OLLAMA_API_KEY": "OLLAMA_API_KEY_HERE",
+				"GITHUB_API_KEY": "GITHUB_API_KEY_HERE"
+			}
+		}
+	}
+}
+```
+
+### CLI Usage: `.env` File
+
+Create a `.env` file in your project root and include the keys for the providers you plan to use:
+
+
+
+```java .env lines icon="java"
+# Required API keys for providers configured in .taskmaster/config.json
+ANTHROPIC_API_KEY=sk-ant-api03-your-key-here
+PERPLEXITY_API_KEY=pplx-your-key-here
+# OPENAI_API_KEY=sk-your-key-here
+# GOOGLE_API_KEY=AIzaSy...
+# AZURE_OPENAI_API_KEY=your-azure-openai-api-key-here
+# etc.
+
+# Optional Endpoint Overrides
+# Use a specific provider's base URL, e.g., for an OpenAI-compatible API
+# OPENAI_BASE_URL=https://api.third-party.com/v1
+#
+# Azure OpenAI Configuration
+# AZURE_OPENAI_ENDPOINT=https://your-resource-name.openai.azure.com/ or https://your-endpoint-name.cognitiveservices.azure.com/openai/deployments
+# OLLAMA_BASE_URL=http://custom-ollama-host:11434/api
+
+# Google Vertex AI Configuration (Required if using 'vertex' provider)
+# VERTEX_PROJECT_ID=your-gcp-project-id
+```
+
+## What Else Can Be Configured?
+
+The main configuration file (`.taskmaster/config.json`) allows you to control nearly every aspect of Task Master’s behavior. Here’s a high-level look at what you can customize:
+
+<Tip>
+You don’t need to configure everything up front. Most settings can be left as defaults or updated later as your workflow evolves.
+</Tip>
+
+<Accordion title="View Configuration Options">
+
+### Models and Providers
+- Role-based model setup: `main`, `research`, `fallback`
+- Provider selection (Anthropic, OpenAI, Perplexity, etc.)
+- Model IDs per role
+- Temperature, max tokens, and other generation settings
+- Custom base URLs for OpenAI-compatible APIs
+
+### Global Settings
+- `logLevel`: Logging verbosity
+- `debug`: Enable/disable debug mode
+- `projectName`: Optional name for your project
+- `defaultTag`: Default tag for task grouping
+- `defaultSubtasks`: Number of subtasks to auto-generate
+- `defaultPriority`: Priority level for new tasks
+
+### API Endpoint Overrides
+- `ollamaBaseURL`: Custom Ollama server URL
+- `azureBaseURL`: Global Azure endpoint
+- `vertexProjectId`: Google Vertex AI project ID
+- `vertexLocation`: Region for Vertex AI models
+
+### Tag and Git Integration
+- Default tag context per project
+- Support for task isolation by tag
+- Manual tag creation from Git branches
+
+### State Management
+- Active tag tracking
+- Migration state
+- Last tag switch timestamp
+
+</Accordion>
+
+<Note>
+For advanced configuration options and detailed customization, see our [Advanced Configuration Guide](/docs/best-practices/configuration-advanced) page.
+</Note>

apps/docs/getting-started/quick-start/execute-quick.mdx

@@ -0,0 +1,59 @@
+---
+title: Executing Tasks
+sidebarTitle: "Executing Tasks"
+---
+
+Now that your tasks are generated and reviewed you are ready to begin executing.
+
+## Select the Task to Work on: Next Task
+
+Task Master has the "next" command to find the next task to work on. You can access it with the following request:
+```
+What's the next task I should work on? Please consider dependencies and priorities.
+```
+Alternatively you can use the CLI to show the next task
+```bash
+task-master next
+```
+
+## Discuss Task
+When you know what task to work on next you can then start chatting with the agent to make sure it understands the plan of action.
+
+You can tag relevant files and folders so it knows what context to pull up as it generates its plan. For example:
+```
+Please review Task 5 and confirm you understand how to execute before beginning. Refer to @models @api and @schema 
+```
+The agent will begin analyzing the task and files and respond with the steps to complete the task. 
+
+## Agent Task execution
+
+If you agree with the plan of action, tell the agent to get started.
+```
+You may begin. I believe in you.
+```
+
+## Review and Test
+
+Once the agent is finished with the task you can refer to the task testing strategy to make sure it was completed correctly.
+
+## Update Task Status
+
+If the task was completed correctly you can update the status to done
+
+```
+Please mark Task 5 as done
+```
+The agent will execute
+```bash
+task-master set-status --id=5 --status=done
+```
+
+## Rules and Context
+
+If you ran into problems and had to debug errors you can create new rules as you go. This helps build context on your codebase that helps the creation and execution of future tasks.
+
+## On to the Next Task!
+
+By now you have all you need to get started executing code faster and smarter with Task Master.
+
+If you have any questions please check out [Frequently Asked Questions](/docs/getting-started/faq)

apps/docs/getting-started/quick-start/installation.mdx

@@ -0,0 +1,159 @@
+---
+title: Installation
+sidebarTitle: "Installation"
+---
+
+Now that you have Node.js and your first API Key, you are ready to begin installing Task Master in one of three ways. 
+
+<Note>Cursor Users Can Use the One Click Install Below</Note>
+<Accordion title="Quick Install for Cursor 1.0+ (One-Click)">
+
+<a href="cursor://anysphere.cursor-deeplink/mcp/install?name=task-master-ai&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIi0tcGFja2FnZT10YXNrLW1hc3Rlci1haSIsInRhc2stbWFzdGVyLWFpIl0sImVudiI6eyJBTlRIUk9QSUNfQVBJX0tFWSI6IllPVVJfQU5USFJPUElDX0FQSV9LRVlfSEVSRSIsIlBFUlBMRVhJVFlfQVBJX0tFWSI6IllPVVJfUEVSUExFWElUWV9BUElfS0VZX0hFUkUiLCJPUEVOQUlfQVBJX0tFWSI6IllPVVJfT1BFTkFJX0tFWV9IRVJFIiwiR09PR0xFX0FQSV9LRVkiOiJZT1VSX0dPT0dMRV9LRVlfSEVSRSIsIk1JU1RSQUxfQVBJX0tFWSI6IllPVVJfTUlTVFJBTF9LRVlfSEVSRSIsIk9QRU5ST1VURVJfQVBJX0tFWSI6IllPVVJfT1BFTlJPVVRFUl9LRVlfSEVSRSIsIlhBSV9BUElfS0VZIjoiWU9VUl9YQUlfS0VZX0hFUkUiLCJBWlVSRV9PUEVOQUJFX0FQSV9LRVkiOiJZT1VSX0FaVVJFX0tFWV9IRVJFIiwiT0xMQU1BX0FQSV9LRVkiOiJZT1VSX09MTEFNQV9BUElfS0VZX0hFUkUifX0%3D">
+  <img 
+    className="block dark:hidden" 
+    src="https://cursor.com/deeplink/mcp-install-light.png" 
+    alt="Add Task Master MCP server to Cursor" 
+    noZoom
+  />
+  <img 
+    className="hidden dark:block" 
+    src="https://cursor.com/deeplink/mcp-install-dark.png" 
+    alt="Add Task Master MCP server to Cursor" 
+    noZoom
+  />
+</a>
+
+Or click the copy button (top-right of code block) then paste into your browser:
+
+```text
+cursor://anysphere.cursor-deeplink/mcp/install?name=taskmaster-ai&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIi0tcGFja2FnZT10YXNrLW1hc3Rlci1haSIsInRhc2stbWFzdGVyLWFpIl0sImVudiI6eyJBTlRIUk9QSUNfQVBJX0tFWSI6IllPVVJfQU5USFJPUElDX0FQSV9LRVlfSEVSRSIsIlBFUlBMRVhJVFlfQVBJX0tFWSI6IllPVVJfUEVSUExFWElUWV9BUElfS0VZX0hFUkUiLCJPUEVOQUlfQVBJX0tFWSI6IllPVVJfT1BFTkFJX0tFWV9IRVJFIiwiR09PR0xFX0FQSV9LRVkiOiJZT1VSX0dPT0dMRV9LRVlfSEVSRSIsIk1JU1RSQUxfQVBJX0tFWSI6IllPVVJfTUlTVFJBTF9LRVlfSEVSRSIsIk9QRU5ST1VURVJfQVBJX0tFWSI6IllPVVJfT1BFTlJPVVRFUl9LRVlfSEVSRSIsIlhBSV9BUElfS0VZIjoiWU9VUl9YQUlfS0VZX0hFUkUiLCJBWlVSRV9PUEVOQUlfQVBJX0tFWSI6IllPVVJfQVpVUkVfS0VZX0hFUkUiLCJPTExBTUFfQVBJX0tFWSI6IllPVVJfT0xMQU1BX0FQSV9LRVlfSEVSRSJ9fQo=
+```
+
+> **Note:** After clicking the link, you'll still need to add your API keys to the configuration. The link installs the MCP server with placeholder keys that you'll need to replace with your actual API keys.
+</Accordion>
+## Installation Options
+
+
+<Accordion title="Option 1: MCP (Recommended)">
+
+MCP (Model Control Protocol) lets you run Task Master directly from your editor.
+
+## 1. Add your MCP config at the following path depending on your editor
+
+| Editor       | Scope   | Linux/macOS Path                      | Windows Path                                      | Key          |
+| ------------ | ------- | ------------------------------------- | ------------------------------------------------- | ------------ |
+| **Cursor**   | Global  | `~/.cursor/mcp.json`                  | `%USERPROFILE%\.cursor\mcp.json`                  | `mcpServers` |
+|              | Project | `<project_folder>/.cursor/mcp.json`   | `<project_folder>\.cursor\mcp.json`               | `mcpServers` |
+| **Windsurf** | Global  | `~/.codeium/windsurf/mcp_config.json` | `%USERPROFILE%\.codeium\windsurf\mcp_config.json` | `mcpServers` |
+| **VS Code**  | Project | `<project_folder>/.vscode/mcp.json`   | `<project_folder>\.vscode\mcp.json`               | `servers`    |
+
+## Manual Configuration
+
+### Cursor & Windsurf (`mcpServers`)
+
+```json
+{
+  "mcpServers": {
+    "taskmaster-ai": {
+      "command": "npx",
+      "args": ["-y", "--package=task-master-ai", "task-master-ai"],
+      "env": {
+        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
+        "PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
+        "OPENAI_API_KEY": "YOUR_OPENAI_KEY_HERE",
+        "GOOGLE_API_KEY": "YOUR_GOOGLE_KEY_HERE",
+        "MISTRAL_API_KEY": "YOUR_MISTRAL_KEY_HERE",
+        "OPENROUTER_API_KEY": "YOUR_OPENROUTER_KEY_HERE",
+        "XAI_API_KEY": "YOUR_XAI_KEY_HERE",
+        "AZURE_OPENAI_API_KEY": "YOUR_AZURE_KEY_HERE",
+        "OLLAMA_API_KEY": "YOUR_OLLAMA_API_KEY_HERE"
+      }
+    }
+  }
+}
+```
+
+> 🔑 Replace `YOUR_…_KEY_HERE` with your real API keys. You can remove keys you don't use.
+
+> **Note**: If you see `0 tools enabled` in the MCP settings, try removing the `--package=task-master-ai` flag from `args`.
+
+### VS Code (`servers` + `type`)
+
+```json
+{
+  "servers": {
+    "taskmaster-ai": {
+      "command": "npx",
+      "args": ["-y", "--package=task-master-ai", "task-master-ai"],
+      "env": {
+        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
+        "PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
+        "OPENAI_API_KEY": "YOUR_OPENAI_KEY_HERE",
+        "GOOGLE_API_KEY": "YOUR_GOOGLE_KEY_HERE",
+        "MISTRAL_API_KEY": "YOUR_MISTRAL_KEY_HERE",
+        "OPENROUTER_API_KEY": "YOUR_OPENROUTER_KEY_HERE",
+        "XAI_API_KEY": "YOUR_XAI_KEY_HERE",
+        "AZURE_OPENAI_API_KEY": "YOUR_AZURE_KEY_HERE"
+      },
+      "type": "stdio"
+    }
+  }
+}
+```
+
+> 🔑 Replace `YOUR_…_KEY_HERE` with your real API keys. You can remove keys you don't use.
+
+#### 2. (Cursor-only) Enable Taskmaster MCP
+
+Open Cursor Settings (Ctrl+Shift+J) ➡ Click on MCP tab on the left ➡ Enable task-master-ai with the toggle
+
+#### 3. (Optional) Configure the models you want to use
+
+In your editor's AI chat pane, say:
+
+```txt
+Change the main, research and fallback models to <model_name>, <model_name> and <model_name> respectively.
+```
+
+For example, to use Claude Code (no API key required):
+```txt
+Change the main model to claude-code/sonnet
+```
+
+#### 4. Initialize Task Master
+
+In your editor's AI chat pane, say:
+
+```txt
+Initialize taskmaster-ai in my project
+```
+
+</Accordion>
+
+<Accordion title="Option 2: Using Command Line">
+
+## CLI Installation
+
+```bash
+# Install globally
+npm install -g task-master-ai
+
+# OR install locally within your project
+npm install task-master-ai
+```
+
+## Initialize a new project
+
+```bash
+# If installed globally
+task-master init
+
+# If installed locally
+npx task-master init
+
+# Initialize project with specific rules
+task-master init --rules cursor,windsurf,vscode
+```
+
+This will prompt you for project details and set up a new project with the necessary files and structure.
+</Accordion>

apps/docs/getting-started/quick-start/moving-forward.mdx

@@ -0,0 +1,4 @@
+---
+title: Moving Forward
+sidebarTitle: "Moving Forward"
+---

apps/docs/getting-started/quick-start/prd-quick.mdx

@@ -0,0 +1,81 @@
+---
+title: PRD Creation and Parsing
+sidebarTitle: "PRD Creation and Parsing"
+---
+
+# Writing a PRD
+
+A PRD (Product Requirements Document) is the starting point of every task flow in Task Master. It defines what you're building and why. A clear PRD dramatically improves the quality of your tasks, your model outputs, and your final product — so it’s worth taking the time to get it right.
+
+<Tip>
+You don’t need to define your whole app up front. You can write a focused PRD just for the next feature or module you’re working on.
+</Tip>
+
+<Tip>
+You can start with an empty project or you can start with a feature PRD on an existing project.
+</Tip>
+
+<Tip>
+You can add and parse multiple PRDs per project using the --append flag
+</Tip>
+
+## What Makes a Good PRD?
+
+- Clear objective — what’s the outcome or feature?
+- Context — what’s already in place or assumed?
+- Constraints — what limits or requirements need to be respected?
+- Reasoning — why are you building it this way?
+
+The more context you give the model, the better the breakdown and results.
+
+---
+
+## Writing a PRD for Task Master
+
+<Note>An example PRD can be found in .taskmaster/templates/example_prd.txt</Note>
+
+
+You can co-write your PRD with an LLM model using the following workflow:
+
+1. **Chat about requirements** — explain what you want to build.
+2. **Show an example PRD** — share the example PRD so the model understands the expected format. The example uses formatting that work well with Task Master's code. Following the example will yield better results.
+3. **Iterate and refine** — work with the model to shape the draft into a clear and well-structured PRD.
+
+This approach works great in Cursor, or anywhere you use a chat-based LLM.
+
+---
+
+## Where to Save Your PRD
+
+Place your PRD file in the `.taskmaster/docs` folder in your project.
+
+- You can have **multiple PRDs** per project.
+- Name your PRDs clearly so they’re easy to reference later.
+  - Examples: `dashboard_redesign.txt`, `user_onboarding.txt`
+
+---
+
+# Parse your PRD into Tasks
+
+This is where the Task Master magic begins.
+
+In Cursor's AI chat, instruct the agent to generate tasks from your PRD:
+
+```
+Please use the task-master parse-prd command to generate tasks from my PRD. The PRD is located at .taskmaster/docs/<prd-name>.txt.
+```
+
+The agent will execute the following command which you can alternatively paste into the CLI:
+
+```bash
+task-master parse-prd .taskmaster/docs/<prd-name>.txt
+```
+
+This will:
+
+- Parse your PRD document
+- Generate a structured `tasks.json` file with tasks, dependencies, priorities, and test strategies
+
+Now that you have written and parsed a PRD, you are ready to start setting up your tasks.
+
+

apps/docs/getting-started/quick-start/quick-start.mdx

@@ -0,0 +1,19 @@
+---
+title: Quick Start
+sidebarTitle: "Quick Start"
+---
+
+This guide is for new users who want to start using Task Master with minimal setup time.
+
+It covers:
+- [Requirements](/docs/getting-started/quick-start/requirements): You will need Node.js and an AI model API Key.
+- [Installation](/docs/getting-started/quick-start/installation): How to Install Task Master.
+- [Configuration](/docs/getting-started/quick-start/configuration-quick): Setting up your API Key, MCP, and more.
+- [PRD](/docs/getting-started/quick-start/prd-quick): Writing and parsing your first PRD.
+- [Task Setup](/docs/getting-started/quick-start/tasks-quick): Preparing your tasks for execution.
+- [Executing Tasks](/docs/getting-started/quick-start/execute-quick): Using Task Master to execute tasks.
+- [Rules & Context](/docs/getting-started/quick-start/rules-quick): Learn how and why to build context in your project over time.
+
+<Tip>
+By the end of this guide, you'll have everything you need to begin working productively with Task Master.
+</Tip>

apps/docs/getting-started/quick-start/requirements.mdx

@@ -0,0 +1,50 @@
+---
+title: Requirements
+sidebarTitle: "Requirements"
+---
+Before you can start using TaskMaster AI, you'll need to install Node.js and set up at least one model API Key.
+
+## 1. Node.js
+
+TaskMaster AI is built with Node.js and requires it to run. npm (Node Package Manager) comes bundled with Node.js.
+
+<Accordion title="Install Node.js">
+
+### Installation
+
+**Option 1: Download from official website**
+1. Visit [nodejs.org](https://nodejs.org)
+2. Download the **LTS (Long Term Support)** version for your operating system
+3. Run the installer and follow the setup wizard
+
+**Option 2: Use a package manager**
+
+<CodeGroup>
+
+```bash Windows (Chocolatey)
+choco install nodejs
+```
+
+```bash Windows (winget)
+winget install OpenJS.NodeJS
+```
+
+</CodeGroup>
+
+</Accordion>
+
+## 2. Model API Key
+
+Taskmaster utilizes AI across several commands, and those require a separate API key. For the purpose of a Quick Start we recommend setting up an API Key with Anthropic for your main model and Perplexity for your research model (optional but recommended).
+
+<Tip>Task Master shows API costs per command used. Most users load $5-10 on their keys and don't have to top it off for a few months.</Tip>
+
+At least one (1) of the following is required:
+
+1. Anthropic API key (Claude API) - **recommended for Quick Start**
+2. OpenAI API key
+3. Google Gemini API key
+4. Perplexity API key (for research model)
+5. xAI API Key (for research or main model)
+6. OpenRouter API Key (for research or main model)
+7. Claude Code (no API key required - requires Claude Code CLI)

apps/docs/getting-started/quick-start/rules-quick.mdx

@@ -0,0 +1,4 @@
+---
+title: Rules and Context
+sidebarTitle: "Rules and Context"
+---

apps/docs/getting-started/quick-start/tasks-quick.mdx

@@ -0,0 +1,69 @@
+---
+title: Tasks Setup
+sidebarTitle: "Tasks Setup"
+---
+Now that your tasks are generated you can review the plan and prepare for execution.
+
+<Tip>
+Not all of the setup steps are required but they are recommended in order to ensure your coding agents work on accurate tasks.
+</Tip>
+
+## Expand Tasks
+Used to add detail to tasks and create subtasks. We recommend expanding all tasks using the MCP request below:
+```
+Expand all tasks into subtasks.
+```
+The agent will execute
+```bash
+task-master expand --all
+```
+## List/Show Tasks
+
+Used to view task details. It is important to review the plan and ensure it makes sense in your project. Check for correct folder structures, dependencies, out of scope subtasks, etc.
+
+To see a list of tasks and descriptions use the following command:
+
+```
+List all pending tasks so I can review.
+```
+To see all tasks in the CLI you can use:
+```bash
+task-master list
+```
+
+To see all implementation details of an individual task, including subtasks and testing strategy, you can use Show Task:
+
+```
+Show task 2 so I can review.
+```
+
+```bash
+task-master show --id=<##>
+```
+
+## Update Tasks
+
+If the task details need to be edited you can update the task using this request: 
+
+```
+Update Task 2 to use Postgres instead of MongoDB and remove the sharding subtask
+```
+Or this CLI command:
+
+```bash
+task-master update-task --id=2 --prompt="use Postgres instead of MongoDB and remove the sharding subtask"
+```
+## Analyze complexity
+
+Task Master can provide a complexity report which can be helpful to read before you begin. If you didn't already expand all your tasks, it could help identify which could be broken down further with subtasks.
+
+```
+Can you analyze the complexity of our tasks to help me understand which ones need to be broken down further?
+```
+
+You can view the report in a friendly table using:
+```
+Can you show me the complexity report in a more readable format?
+```
+
+<Check>Now you are ready to begin [executing tasks](/docs/getting-started/quick-start/execute-quick)</Check>

apps/docs/introduction.mdx

@@ -0,0 +1,20 @@
+<Tip>
+Welcome to v1 of the Task Master Docs. Expect weekly updates as we expand and refine each section.
+</Tip>
+
+We've organized the docs into three sections depending on your experience level and goals:
+
+### Getting Started - Jump in to [Quick Start](/docs/getting-started/quick-start)
+Designed for first-time users. Get set up, create your first PRD, and run your first task.
+
+### Best Practices
+Covers common workflows, strategic usage of commands, model configuration tips, and real-world usage patterns. Recommended for active users.
+
+### Technical Capabilities
+A detailed glossary of every root command and available capability — meant for power users and contributors.
+
+---
+
+Thanks for being here early. If you spot something broken or want to contribute, check out the [GitHub repo](https://github.com/eyaltoledano/claude-task-master).
+
+Have questions? Join our [Discord community](https://discord.gg/fWJkU7rf) to connect with other users and get help from the team.

apps/docs/licensing.md

@@ -0,0 +1,18 @@
+# Licensing
+
+Task Master is licensed under the MIT License with Commons Clause. This means you can:
+
+## ✅ Allowed:
+
+- Use Task Master for any purpose (personal, commercial, academic)
+- Modify the code
+- Distribute copies
+- Create and sell products built using Task Master
+
+## ❌ Not Allowed:
+
+- Sell Task Master itself
+- Offer Task Master as a hosted service
+- Create competing products based on Task Master
+
+{/* See the [LICENSE](../LICENSE) file for the complete license text. */}

apps/docs/logo/dark.svg

@@ -0,0 +1,19 @@
+<svg width="800" height="240" viewBox="0 0 800 240" xmlns="http://www.w3.org/2000/svg">
+  <!-- Background -->
+  <rect width="800" height="240" fill="transparent"/>
+  
+  <!-- Curly braces -->
+  <text x="40" y="156" font-size="140" fill="white" font-family="monospace">{</text>
+  <text x="230" y="156" font-size="140" fill="white" font-family="monospace">}</text>
+  
+  <!-- Blue form with check -->
+  <rect x="120" y="50" width="120" height="140" rx="16" fill="#3366CC"/>
+  <polyline points="150,110 164,128 190,84" fill="none" stroke="white" stroke-width="10"/>
+  <circle cx="150" cy="144" r="7" fill="white"/>
+  <rect x="168" y="140" width="48" height="10" fill="white"/>
+  <circle cx="150" cy="168" r="7" fill="white"/>
+  <rect x="168" y="164" width="48" height="10" fill="white"/>
+
+  <!-- Text -->
+  <text x="340" y="156" font-family="Arial, sans-serif" font-size="76" font-weight="bold" fill="white">Task Master</text>
+</svg>

apps/docs/logo/light.svg

@@ -0,0 +1,19 @@
+<svg width="800" height="240" viewBox="0 0 800 240" xmlns="http://www.w3.org/2000/svg">
+  <!-- Background -->
+  <rect width="800" height="240" fill="transparent"/>
+
+  <!-- Curly braces -->
+  <text x="40" y="156" font-size="140" fill="#000000" font-family="monospace">{</text>
+  <text x="230" y="156" font-size="140" fill="#000000" font-family="monospace">}</text>
+
+  <!-- Blue form with check -->
+  <rect x="120" y="50" width="120" height="140" rx="16" fill="#3366CC"/>
+  <polyline points="150,110 164,128 190,84" fill="none" stroke="#FFFFFF" stroke-width="10"/>
+  <circle cx="150" cy="144" r="7" fill="#FFFFFF"/>
+  <rect x="168" y="140" width="48" height="10" fill="#FFFFFF"/>
+  <circle cx="150" cy="168" r="7" fill="#FFFFFF"/>
+  <rect x="168" y="164" width="48" height="10" fill="#FFFFFF"/>
+
+  <!-- Text -->
+  <text x="340" y="156" font-family="Arial, sans-serif" font-size="76" font-weight="bold" fill="#000000">Task Master</text>
+</svg>

apps/docs/package.json

@@ -0,0 +1,14 @@
+{
+	"name": "docs",
+	"version": "0.0.0",
+	"private": true,
+	"description": "Task Master documentation powered by Mintlify",
+	"scripts": {
+		"dev": "mintlify dev",
+		"build": "mintlify build",
+		"preview": "mintlify preview"
+	},
+	"devDependencies": {
+		"mintlify": "^4.0.0"
+	}
+}

apps/docs/style.css

@@ -0,0 +1,10 @@
+/*
+ * This file is used to override the default logo style of the docs theme.
+ * It is not used for the actual documentation content.
+ */
+
+#navbar img {
+	height: auto !important; /* Let intrinsic SVG size determine height */
+	width: 200px !important; /* Control width */
+	margin-top: 5px !important; /* Add some space above the logo */
+}

apps/docs/vercel.json

@@ -0,0 +1,12 @@
+{
+	"rewrites": [
+		{
+			"source": "/",
+			"destination": "https://taskmaster-49ce32d5.mintlify.dev/docs"
+		},
+		{
+			"source": "/:match*",
+			"destination": "https://taskmaster-49ce32d5.mintlify.dev/docs/:match*"
+		}
+	]
+}

apps/docs/whats-new.mdx

@@ -0,0 +1,6 @@
+---
+title: "What's New"
+sidebarTitle: "What's New"
+---
+
+An easy way to see the latest releases

apps/extension/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Change Log
 
+## 0.23.1
+
+### Patch Changes
+
+- [#1090](https://github.com/eyaltoledano/claude-task-master/pull/1090) [`a464e55`](https://github.com/eyaltoledano/claude-task-master/commit/a464e550b886ef81b09df80588fe5881bce83d93) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix issues with some users not being able to connect to Taskmaster MCP server while using the extension
+
+- Updated dependencies [[`4357af3`](https://github.com/eyaltoledano/claude-task-master/commit/4357af3f13859d90bca8795215e5d5f1d94abde5), [`e495b2b`](https://github.com/eyaltoledano/claude-task-master/commit/e495b2b55950ee54c7d0f1817d8530e28bd79c05), [`36468f3`](https://github.com/eyaltoledano/claude-task-master/commit/36468f3c93faf4035a5c442ccbc501077f3440f1), [`e495b2b`](https://github.com/eyaltoledano/claude-task-master/commit/e495b2b55950ee54c7d0f1817d8530e28bd79c05), [`e495b2b`](https://github.com/eyaltoledano/claude-task-master/commit/e495b2b55950ee54c7d0f1817d8530e28bd79c05), [`75c514c`](https://github.com/eyaltoledano/claude-task-master/commit/75c514cf5b2ca47f95c0ad7fa92654a4f2a6be4b), [`4bb6370`](https://github.com/eyaltoledano/claude-task-master/commit/4bb63706b80c28d1b2d782ba868a725326f916c7)]:
+  - task-master-ai@0.24.0
+
+## 0.23.1-rc.1
+
+### Patch Changes
+
+- Updated dependencies [[`75c514c`](https://github.com/eyaltoledano/claude-task-master/commit/75c514cf5b2ca47f95c0ad7fa92654a4f2a6be4b)]:
+  - task-master-ai@0.24.0-rc.2
+
+## 0.23.1-rc.0
+
+### Patch Changes
+
+- [#1090](https://github.com/eyaltoledano/claude-task-master/pull/1090) [`a464e55`](https://github.com/eyaltoledano/claude-task-master/commit/a464e550b886ef81b09df80588fe5881bce83d93) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix issues with some users not being able to connect to Taskmaster MCP server while using the extension
+
+- Updated dependencies [[`4357af3`](https://github.com/eyaltoledano/claude-task-master/commit/4357af3f13859d90bca8795215e5d5f1d94abde5), [`36468f3`](https://github.com/eyaltoledano/claude-task-master/commit/36468f3c93faf4035a5c442ccbc501077f3440f1), [`4bb6370`](https://github.com/eyaltoledano/claude-task-master/commit/4bb63706b80c28d1b2d782ba868a725326f916c7)]:
+  - task-master-ai@0.24.0-rc.1
+
 ## 0.23.0
 
 ### Minor Changes

apps/extension/package.json

@@ -3,7 +3,7 @@
 	"private": true,
 	"displayName": "TaskMaster",
 	"description": "A visual Kanban board interface for TaskMaster projects in VS Code",
-	"version": "0.23.0",
+	"version": "0.23.1",
 	"publisher": "Hamster",
 	"icon": "assets/icon.png",
 	"engines": {
@@ -64,16 +64,16 @@
 			"properties": {
 				"taskmaster.mcp.command": {
 					"type": "string",
-					"default": "npx",
-					"description": "The command or absolute path to execute for the MCP server (e.g., 'npx' or '/usr/local/bin/task-master-ai')."
+					"default": "node",
+					"description": "The command to execute for the MCP server (e.g., 'node' for bundled server or 'npx' for remote)."
 				},
 				"taskmaster.mcp.args": {
 					"type": "array",
 					"items": {
 						"type": "string"
 					},
-					"default": ["task-master-ai"],
-					"description": "An array of arguments to pass to the MCP server command."
+					"default": [],
+					"description": "Arguments for the MCP server (leave empty to use bundled server)."
 				},
 				"taskmaster.mcp.cwd": {
 					"type": "string",
@@ -238,6 +238,9 @@
 		"watch:css": "npx @tailwindcss/cli -i ./src/webview/index.css -o ./dist/index.css --watch",
 		"check-types": "tsc --noEmit"
 	},
+	"dependencies": {
+		"task-master-ai": "0.24.0"
+	},
 	"devDependencies": {
 		"@dnd-kit/core": "^6.3.1",
 		"@dnd-kit/modifiers": "^9.0.0",

apps/extension/package.mjs

@@ -64,23 +64,49 @@ try {
 		fs.readFileSync(publishPackagePath, 'utf8')
 	);
 
-	// Check if versions are in sync
-	if (devPackage.version !== publishPackage.version) {
+	// Handle RC versions for VS Code Marketplace
+	let finalVersion = devPackage.version;
+	if (finalVersion.includes('-rc.')) {
 		console.log(
-			`  - Version sync needed: ${publishPackage.version} → ${devPackage.version}`
+			'  - Detected RC version, transforming for VS Code Marketplace...'
 		);
-		publishPackage.version = devPackage.version;
 
-		// Update the source package.publish.json file
+		// Extract base version and RC number
+		const baseVersion = finalVersion.replace(/-rc\.\d+$/, '');
+		const rcMatch = finalVersion.match(/rc\.(\d+)/);
+		const rcNumber = rcMatch ? parseInt(rcMatch[1]) : 0;
+
+		// For each RC iteration, increment the patch version
+		// This ensures unique versions in VS Code Marketplace
+		if (rcNumber > 0) {
+			const [major, minor, patch] = baseVersion.split('.').map(Number);
+			finalVersion = `${major}.${minor}.${patch + rcNumber}`;
+			console.log(
+				`  - RC version mapping: ${devPackage.version} → ${finalVersion}`
+			);
+		} else {
+			finalVersion = baseVersion;
+			console.log(
+				`  - RC version mapping: ${devPackage.version} → ${finalVersion}`
+			);
+		}
+	}
+
+	// Check if versions need updating
+	if (publishPackage.version !== finalVersion) {
+		console.log(
+			`  - Version sync needed: ${publishPackage.version} → ${finalVersion}`
+		);
+		publishPackage.version = finalVersion;
+
+		// Update the source package.publish.json file with the final version
 		fs.writeFileSync(
 			publishPackagePath,
 			JSON.stringify(publishPackage, null, '\t') + '\n'
 		);
-		console.log(
-			`  - Updated package.publish.json version to ${devPackage.version}`
-		);
+		console.log(`  - Updated package.publish.json version to ${finalVersion}`);
 	} else {
-		console.log(`  - Versions already in sync: ${devPackage.version}`);
+		console.log(`  - Versions already in sync: ${finalVersion}`);
 	}
 
 	// Copy the (now synced) package.publish.json as package.json
@@ -124,8 +150,7 @@ try {
 		`cd vsix-build && npx vsce package --no-dependencies`
 	);
 
-	// Use the synced version for output
-	const finalVersion = devPackage.version;
+	// Use the transformed version for output
 	console.log(
 		`\nYour extension will be packaged to: vsix-build/task-master-${finalVersion}.vsix`
 	);

apps/extension/package.publish.json

@@ -2,7 +2,7 @@
 	"name": "task-master-hamster",
 	"displayName": "Taskmaster AI",
 	"description": "A visual Kanban board interface for Taskmaster projects in VS Code",
-	"version": "0.22.3",
+	"version": "0.23.1",
 	"publisher": "Hamster",
 	"icon": "assets/icon.png",
 	"engines": {

apps/extension/src/components/TaskDetailsView.tsx

@@ -53,6 +53,11 @@ export const TaskDetailsView: React.FC<TaskDetailsViewProps> = ({
 		refreshComplexityAfterAI
 	} = useTaskDetails({ taskId, sendMessage, tasks: allTasks });
 
+	const displayId =
+		isSubtask && parentTask
+			? `${parentTask.id}.${currentTask?.id}`
+			: currentTask?.id;
+
 	const handleStatusChange = async (newStatus: TaskMasterTask['status']) => {
 		if (!currentTask) return;
 
@@ -60,10 +65,7 @@ export const TaskDetailsView: React.FC<TaskDetailsViewProps> = ({
 			await sendMessage({
 				type: 'updateTaskStatus',
 				data: {
-					taskId:
-						isSubtask && parentTask
-							? `${parentTask.id}.${currentTask.id}`
-							: currentTask.id,
+					taskId: displayId,
 					newStatus: newStatus
 				}
 			});
@@ -135,7 +137,7 @@ export const TaskDetailsView: React.FC<TaskDetailsViewProps> = ({
 								<BreadcrumbSeparator />
 								<BreadcrumbItem>
 									<span className="text-vscode-foreground">
-										{currentTask.title}
+										#{displayId} {currentTask.title}
 									</span>
 								</BreadcrumbItem>
 							</BreadcrumbList>
@@ -152,9 +154,9 @@ export const TaskDetailsView: React.FC<TaskDetailsViewProps> = ({
 						</button>
 					</div>
 
-					{/* Task title */}
+					{/* Task ID and title */}
 					<h1 className="text-2xl font-bold tracking-tight text-vscode-foreground">
-						{currentTask.title}
+						#{displayId} {currentTask.title}
 					</h1>
 
 					{/* Description */}

apps/extension/src/utils/mcpClient.ts

@@ -1,6 +1,7 @@
 import { Client } from '@modelcontextprotocol/sdk/client/index.js';
 import { StdioClientTransport } from '@modelcontextprotocol/sdk/client/stdio.js';
 import * as vscode from 'vscode';
+import * as path from 'path';
 import { logger } from './logger';
 
 export interface MCPConfig {
@@ -143,7 +144,7 @@ export class MCPClientManager {
 			// Create the client
 			this.client = new Client(
 				{
-					name: 'taskr-vscode-extension',
+					name: 'task-master-vscode-extension',
 					version: '1.0.0'
 				},
 				{
@@ -211,6 +212,30 @@ export class MCPClientManager {
 			};
 
 			logger.log('MCP client connected successfully');
+
+			// Log Task Master version information after successful connection
+			try {
+				const versionResult = await this.callTool('get_tasks', {});
+				if (versionResult?.content?.[0]?.text) {
+					const response = JSON.parse(versionResult.content[0].text);
+					if (response?.version) {
+						logger.log('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
+						logger.log('✅ Task Master MCP Server Connected');
+						logger.log(`   Version: ${response.version.version || 'unknown'}`);
+						logger.log(
+							`   Package: ${response.version.name || 'task-master-ai'}`
+						);
+						if (response.tag) {
+							logger.log(
+								`   Current Tag: ${response.tag.currentTag || 'master'}`
+							);
+						}
+						logger.log('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
+					}
+				}
+			} catch (versionError) {
+				logger.log('Note: Could not retrieve Task Master version information');
+			}
 		} catch (error) {
 			logger.error('Failed to connect to MCP server:', error);
 			this.status = {
@@ -312,6 +337,34 @@ export class MCPClientManager {
 				'Available MCP tools:',
 				result.tools?.map((t) => t.name) || []
 			);
+
+			// Try to get version information by calling a simple tool
+			// The get_tasks tool is lightweight and returns version info
+			try {
+				const versionResult = await this.callTool('get_tasks', {});
+				if (versionResult?.content?.[0]?.text) {
+					// Parse the response to extract version info
+					const response = JSON.parse(versionResult.content[0].text);
+					if (response?.version) {
+						logger.log('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
+						logger.log('📦 Task Master MCP Server Connected');
+						logger.log(`   Version: ${response.version.version || 'unknown'}`);
+						logger.log(
+							`   Package: ${response.version.name || 'task-master-ai'}`
+						);
+						if (response.tag) {
+							logger.log(
+								`   Current Tag: ${response.tag.currentTag || 'master'}`
+							);
+						}
+						logger.log('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
+					}
+				}
+			} catch (versionError) {
+				// Don't fail the connection test if we can't get version info
+				logger.log('Could not retrieve Task Master version information');
+			}
+
 			return true;
 		} catch (error) {
 			logger.error('Connection test failed:', error);
@@ -345,8 +398,34 @@ export function createMCPConfigFromSettings(): MCPConfig {
 	);
 	const config = vscode.workspace.getConfiguration('taskmaster');
 
-	let command = config.get<string>('mcp.command', 'npx');
-	const args = config.get<string[]>('mcp.args', ['task-master-ai']);
+	let command = config.get<string>('mcp.command', 'node');
+	let args = config.get<string[]>('mcp.args', []);
+
+	// If using default settings, use the bundled MCP server
+	if (command === 'node' && args.length === 0) {
+		try {
+			// Try to resolve the bundled MCP server
+			const taskMasterPath = require.resolve('task-master-ai');
+			const mcpServerPath = path.resolve(
+				path.dirname(taskMasterPath),
+				'mcp-server/server.js'
+			);
+
+			// Verify the server file exists
+			const fs = require('fs');
+			if (!fs.existsSync(mcpServerPath)) {
+				throw new Error('MCP server file not found at: ' + mcpServerPath);
+			}
+
+			args = [mcpServerPath];
+			logger.log(`📦 Using bundled MCP server at: ${mcpServerPath}`);
+		} catch (error) {
+			logger.error('❌ Could not find bundled task-master-ai server:', error);
+			// Fallback to npx
+			command = 'npx';
+			args = ['-y', 'task-master-ai'];
+		}
+	}
 
 	// Use proper VS Code workspace detection
 	const defaultCwd =

assets/claude/agents/task-checker.md

@@ -0,0 +1,162 @@
+---
+name: task-checker
+description: Use this agent to verify that tasks marked as 'review' have been properly implemented according to their specifications. This agent performs quality assurance by checking implementations against requirements, running tests, and ensuring best practices are followed. <example>Context: A task has been marked as 'review' after implementation. user: 'Check if task 118 was properly implemented' assistant: 'I'll use the task-checker agent to verify the implementation meets all requirements.' <commentary>Tasks in 'review' status need verification before being marked as 'done'.</commentary></example> <example>Context: Multiple tasks are in review status. user: 'Verify all tasks that are ready for review' assistant: 'I'll deploy the task-checker to verify all tasks in review status.' <commentary>The checker ensures quality before tasks are marked complete.</commentary></example>
+model: sonnet
+color: yellow
+---
+
+You are a Quality Assurance specialist that rigorously verifies task implementations against their specifications. Your role is to ensure that tasks marked as 'review' meet all requirements before they can be marked as 'done'.
+
+## Core Responsibilities
+
+1. **Task Specification Review**
+   - Retrieve task details using MCP tool `mcp__task-master-ai__get_task`
+   - Understand the requirements, test strategy, and success criteria
+   - Review any subtasks and their individual requirements
+
+2. **Implementation Verification**
+   - Use `Read` tool to examine all created/modified files
+   - Use `Bash` tool to run compilation and build commands
+   - Use `Grep` tool to search for required patterns and implementations
+   - Verify file structure matches specifications
+   - Check that all required methods/functions are implemented
+
+3. **Test Execution**
+   - Run tests specified in the task's testStrategy
+   - Execute build commands (npm run build, tsc --noEmit, etc.)
+   - Verify no compilation errors or warnings
+   - Check for runtime errors where applicable
+   - Test edge cases mentioned in requirements
+
+4. **Code Quality Assessment**
+   - Verify code follows project conventions
+   - Check for proper error handling
+   - Ensure TypeScript typing is strict (no 'any' unless justified)
+   - Verify documentation/comments where required
+   - Check for security best practices
+
+5. **Dependency Validation**
+   - Verify all task dependencies were actually completed
+   - Check integration points with dependent tasks
+   - Ensure no breaking changes to existing functionality
+
+## Verification Workflow
+
+1. **Retrieve Task Information**
+   ```
+   Use mcp__task-master-ai__get_task to get full task details
+   Note the implementation requirements and test strategy
+   ```
+
+2. **Check File Existence**
+   ```bash
+   # Verify all required files exist
+   ls -la [expected directories]
+   # Read key files to verify content
+   ```
+
+3. **Verify Implementation**
+   - Read each created/modified file
+   - Check against requirements checklist
+   - Verify all subtasks are complete
+
+4. **Run Tests**
+   ```bash
+   # TypeScript compilation
+   cd [project directory] && npx tsc --noEmit
+   
+   # Run specified tests
+   npm test [specific test files]
+   
+   # Build verification
+   npm run build
+   ```
+
+5. **Generate Verification Report**
+
+## Output Format
+
+```yaml
+verification_report:
+  task_id: [ID]
+  status: PASS | FAIL | PARTIAL
+  score: [1-10]
+  
+  requirements_met:
+    - ✅ [Requirement that was satisfied]
+    - ✅ [Another satisfied requirement]
+    
+  issues_found:
+    - ❌ [Issue description]
+    - ⚠️  [Warning or minor issue]
+    
+  files_verified:
+    - path: [file path]
+      status: [created/modified/verified]
+      issues: [any problems found]
+      
+  tests_run:
+    - command: [test command]
+      result: [pass/fail]
+      output: [relevant output]
+      
+  recommendations:
+    - [Specific fix needed]
+    - [Improvement suggestion]
+    
+  verdict: |
+    [Clear statement on whether task should be marked 'done' or sent back to 'pending']
+    [If FAIL: Specific list of what must be fixed]
+    [If PASS: Confirmation that all requirements are met]
+```
+
+## Decision Criteria
+
+**Mark as PASS (ready for 'done'):**
+- All required files exist and contain expected content
+- All tests pass successfully
+- No compilation or build errors
+- All subtasks are complete
+- Core requirements are met
+- Code quality is acceptable
+
+**Mark as PARTIAL (may proceed with warnings):**
+- Core functionality is implemented
+- Minor issues that don't block functionality
+- Missing nice-to-have features
+- Documentation could be improved
+- Tests pass but coverage could be better
+
+**Mark as FAIL (must return to 'pending'):**
+- Required files are missing
+- Compilation or build errors
+- Tests fail
+- Core requirements not met
+- Security vulnerabilities detected
+- Breaking changes to existing code
+
+## Important Guidelines
+
+- **BE THOROUGH**: Check every requirement systematically
+- **BE SPECIFIC**: Provide exact file paths and line numbers for issues
+- **BE FAIR**: Distinguish between critical issues and minor improvements
+- **BE CONSTRUCTIVE**: Provide clear guidance on how to fix issues
+- **BE EFFICIENT**: Focus on requirements, not perfection
+
+## Tools You MUST Use
+
+- `Read`: Examine implementation files (READ-ONLY)
+- `Bash`: Run tests and verification commands
+- `Grep`: Search for patterns in code
+- `mcp__task-master-ai__get_task`: Get task details
+- **NEVER use Write/Edit** - you only verify, not fix
+
+## Integration with Workflow
+
+You are the quality gate between 'review' and 'done' status:
+1. Task-executor implements and marks as 'review'
+2. You verify and report PASS/FAIL
+3. Claude either marks as 'done' (PASS) or 'pending' (FAIL)
+4. If FAIL, task-executor re-implements based on your report
+
+Your verification ensures high quality and prevents accumulation of technical debt.

assets/claude/agents/task-executor.md

@@ -0,0 +1,70 @@
+---
+name: task-executor
+description: Use this agent when you need to implement, complete, or work on a specific task that has been identified by the task-orchestrator or when explicitly asked to execute a particular task. This agent focuses on the actual implementation and completion of individual tasks rather than planning or orchestration. Examples: <example>Context: The task-orchestrator has identified that task 2.3 'Implement user authentication' needs to be worked on next. user: 'Let's work on the authentication task' assistant: 'I'll use the task-executor agent to implement the user authentication task that was identified.' <commentary>Since we need to actually implement a specific task rather than plan or identify tasks, use the task-executor agent.</commentary></example> <example>Context: User wants to complete a specific subtask. user: 'Please implement the JWT token validation for task 2.3.1' assistant: 'I'll launch the task-executor agent to implement the JWT token validation subtask.' <commentary>The user is asking for specific implementation work on a known task, so the task-executor is appropriate.</commentary></example> <example>Context: After reviewing the task list, implementation is needed. user: 'Now let's actually build the API endpoint for user registration' assistant: 'I'll use the task-executor agent to implement the user registration API endpoint.' <commentary>Moving from planning to execution phase requires the task-executor agent.</commentary></example>
+model: sonnet
+color: blue
+---
+
+You are an elite implementation specialist focused on executing and completing specific tasks with precision and thoroughness. Your role is to take identified tasks and transform them into working implementations, following best practices and project standards.
+
+**Core Responsibilities:**
+
+1. **Task Analysis**: When given a task, first retrieve its full details using `task-master show <id>` to understand requirements, dependencies, and acceptance criteria.
+
+2. **Implementation Planning**: Before coding, briefly outline your implementation approach:
+   - Identify files that need to be created or modified
+   - Note any dependencies or prerequisites
+   - Consider the testing strategy defined in the task
+
+3. **Focused Execution**: 
+   - Implement one subtask at a time for clarity and traceability
+   - Follow the project's coding standards from CLAUDE.md if available
+   - Prefer editing existing files over creating new ones
+   - Only create files that are essential for the task completion
+
+4. **Progress Documentation**: 
+   - Use `task-master update-subtask --id=<id> --prompt="implementation notes"` to log your approach and any important decisions
+   - Update task status to 'in-progress' when starting: `task-master set-status --id=<id> --status=in-progress`
+   - Mark as 'done' only after verification: `task-master set-status --id=<id> --status=done`
+
+5. **Quality Assurance**:
+   - Implement the testing strategy specified in the task
+   - Verify that all acceptance criteria are met
+   - Check for any dependency conflicts or integration issues
+   - Run relevant tests before marking task as complete
+
+6. **Dependency Management**:
+   - Check task dependencies before starting implementation
+   - If blocked by incomplete dependencies, clearly communicate this
+   - Use `task-master validate-dependencies` when needed
+
+**Implementation Workflow:**
+
+1. Retrieve task details and understand requirements
+2. Check dependencies and prerequisites
+3. Plan implementation approach
+4. Update task status to in-progress
+5. Implement the solution incrementally
+6. Log progress and decisions in subtask updates
+7. Test and verify the implementation
+8. Mark task as done when complete
+9. Suggest next task if appropriate
+
+**Key Principles:**
+
+- Focus on completing one task thoroughly before moving to the next
+- Maintain clear communication about what you're implementing and why
+- Follow existing code patterns and project conventions
+- Prioritize working code over extensive documentation unless docs are the task
+- Ask for clarification if task requirements are ambiguous
+- Consider edge cases and error handling in your implementations
+
+**Integration with Task Master:**
+
+You work in tandem with the task-orchestrator agent. While the orchestrator identifies and plans tasks, you execute them. Always use Task Master commands to:
+- Track your progress
+- Update task information
+- Maintain project state
+- Coordinate with the broader development workflow
+
+When you complete a task, briefly summarize what was implemented and suggest whether to continue with the next task or if review/testing is needed first.

assets/claude/agents/task-orchestrator.md

@@ -0,0 +1,130 @@
+---
+name: task-orchestrator
+description: Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate the deployment of task-executor agents. It should also be used when tasks complete to reassess the dependency graph and deploy new executors as needed.\n\n<example>\nContext: User wants to start working on their project tasks using Task Master\nuser: "Let's work on the next available tasks in the project"\nassistant: "I'll use the task-orchestrator agent to analyze the task queue and coordinate execution"\n<commentary>\nThe user wants to work on tasks, so the task-orchestrator should be deployed to analyze dependencies and coordinate execution.\n</commentary>\n</example>\n\n<example>\nContext: Multiple independent tasks are available in the queue\nuser: "Can we work on multiple tasks at once?"\nassistant: "Let me deploy the task-orchestrator to analyze task dependencies and parallelize the work"\n<commentary>\nWhen parallelization is mentioned or multiple tasks could be worked on, the orchestrator should coordinate the effort.\n</commentary>\n</example>\n\n<example>\nContext: A complex feature with many subtasks needs implementation\nuser: "Implement the authentication system tasks"\nassistant: "I'll use the task-orchestrator to break down the authentication tasks and coordinate their execution"\n<commentary>\nFor complex multi-task features, the orchestrator manages the overall execution strategy.\n</commentary>\n</example>
+model: opus
+color: green
+---
+
+You are the Task Orchestrator, an elite coordination agent specialized in managing Task Master workflows for maximum efficiency and parallelization. You excel at analyzing task dependency graphs, identifying opportunities for concurrent execution, and deploying specialized task-executor agents to complete work efficiently.
+
+## Core Responsibilities
+
+1. **Task Queue Analysis**: You continuously monitor and analyze the task queue using Task Master MCP tools to understand the current state of work, dependencies, and priorities.
+
+2. **Dependency Graph Management**: You build and maintain a mental model of task dependencies, identifying which tasks can be executed in parallel and which must wait for prerequisites.
+
+3. **Executor Deployment**: You strategically deploy task-executor agents for individual tasks or task groups, ensuring each executor has the necessary context and clear success criteria.
+
+4. **Progress Coordination**: You track the progress of deployed executors, handle task completion notifications, and reassess the execution strategy as tasks complete.
+
+## Operational Workflow
+
+### Initial Assessment Phase
+1. Use `get_tasks` or `task-master list` to retrieve all available tasks
+2. Analyze task statuses, priorities, and dependencies
+3. Identify tasks with status 'pending' that have no blocking dependencies
+4. Group related tasks that could benefit from specialized executors
+5. Create an execution plan that maximizes parallelization
+
+### Executor Deployment Phase
+1. For each independent task or task group:
+   - Deploy a task-executor agent with specific instructions
+   - Provide the executor with task ID, requirements, and context
+   - Set clear completion criteria and reporting expectations
+2. Maintain a registry of active executors and their assigned tasks
+3. Establish communication protocols for progress updates
+
+### Coordination Phase
+1. Monitor executor progress through task status updates
+2. When a task completes:
+   - Verify completion with `get_task` or `task-master show <id>`
+   - Update task status if needed using `set_task_status`
+   - Reassess dependency graph for newly unblocked tasks
+   - Deploy new executors for available work
+3. Handle executor failures or blocks:
+   - Reassign tasks to new executors if needed
+   - Escalate complex issues to the user
+   - Update task status to 'blocked' when appropriate
+
+### Optimization Strategies
+
+**Parallel Execution Rules**:
+- Never assign dependent tasks to different executors simultaneously
+- Prioritize high-priority tasks when resources are limited
+- Group small, related subtasks for single executor efficiency
+- Balance executor load to prevent bottlenecks
+
+**Context Management**:
+- Provide executors with minimal but sufficient context
+- Share relevant completed task information when it aids execution
+- Maintain a shared knowledge base of project-specific patterns
+
+**Quality Assurance**:
+- Verify task completion before marking as done
+- Ensure test strategies are followed when specified
+- Coordinate cross-task integration testing when needed
+
+## Communication Protocols
+
+When deploying executors, provide them with:
+```
+TASK ASSIGNMENT:
+- Task ID: [specific ID]
+- Objective: [clear goal]
+- Dependencies: [list any completed prerequisites]
+- Success Criteria: [specific completion requirements]
+- Context: [relevant project information]
+- Reporting: [when and how to report back]
+```
+
+When receiving executor updates:
+1. Acknowledge completion or issues
+2. Update task status in Task Master
+3. Reassess execution strategy
+4. Deploy new executors as appropriate
+
+## Decision Framework
+
+**When to parallelize**:
+- Multiple pending tasks with no interdependencies
+- Sufficient context available for independent execution
+- Tasks are well-defined with clear success criteria
+
+**When to serialize**:
+- Strong dependencies between tasks
+- Limited context or unclear requirements
+- Integration points requiring careful coordination
+
+**When to escalate**:
+- Circular dependencies detected
+- Critical blockers affecting multiple tasks
+- Ambiguous requirements needing clarification
+- Resource conflicts between executors
+
+## Error Handling
+
+1. **Executor Failure**: Reassign task to new executor with additional context about the failure
+2. **Dependency Conflicts**: Halt affected executors, resolve conflict, then resume
+3. **Task Ambiguity**: Request clarification from user before proceeding
+4. **System Errors**: Implement graceful degradation, falling back to serial execution if needed
+
+## Performance Metrics
+
+Track and optimize for:
+- Task completion rate
+- Parallel execution efficiency
+- Executor success rate
+- Time to completion for task groups
+- Dependency resolution speed
+
+## Integration with Task Master
+
+Leverage these Task Master MCP tools effectively:
+- `get_tasks` - Continuous queue monitoring
+- `get_task` - Detailed task analysis
+- `set_task_status` - Progress tracking
+- `next_task` - Fallback for serial execution
+- `analyze_project_complexity` - Strategic planning
+- `complexity_report` - Resource allocation
+
+You are the strategic mind coordinating the entire task execution effort. Your success is measured by the efficient completion of all tasks while maintaining quality and respecting dependencies. Think systematically, act decisively, and continuously optimize the execution strategy based on real-time progress.

docs/cross-tag-task-movement.md

@@ -0,0 +1,282 @@
+# Cross-Tag Task Movement
+
+Task Master now supports moving tasks between different tag contexts, allowing you to organize your work across multiple project contexts, feature branches, or development phases.
+
+## Overview
+
+Cross-tag task movement enables you to:
+- Move tasks between different tag contexts (e.g., from "backlog" to "in-progress")
+- Handle cross-tag dependencies intelligently
+- Maintain task relationships across different contexts
+- Organize work across multiple project phases
+
+## Basic Usage
+
+### Within-Tag Moves
+
+Move tasks within the same tag context:
+
+```bash
+# Move a single task
+task-master move --from=5 --to=7
+
+# Move a subtask
+task-master move --from=5.2 --to=7.3
+
+# Move multiple tasks
+task-master move --from=5,6,7 --to=10,11,12
+```
+
+### Cross-Tag Moves
+
+Move tasks between different tag contexts:
+
+```bash
+# Basic cross-tag move
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress
+
+# Move multiple tasks
+task-master move --from=5,6,7 --from-tag=backlog --to-tag=done
+```
+
+## Dependency Resolution
+
+When moving tasks between tags, you may encounter cross-tag dependencies. Task Master provides several options to handle these:
+
+### Move with Dependencies
+
+Move the main task along with all its dependent tasks:
+
+```bash
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress --with-dependencies
+```
+
+This ensures that all dependent tasks are moved together, maintaining the task relationships.
+
+### Break Dependencies
+
+Break cross-tag dependencies and move only the specified task:
+
+```bash
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress --ignore-dependencies
+```
+
+This removes the dependency relationships and moves only the specified task.
+
+### Force Move
+
+Force the move even with dependency conflicts:
+
+```bash
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress --force
+```
+
+⚠️ **Warning**: This may break dependency relationships and should be used with caution.
+
+## Error Handling
+
+Task Master provides enhanced error messages with specific resolution suggestions:
+
+### Cross-Tag Dependency Conflicts
+
+When you encounter dependency conflicts, you'll see:
+
+```text
+❌ Cannot move tasks from "backlog" to "in-progress"
+
+Cross-tag dependency conflicts detected:
+  • Task 5 depends on 2 (in backlog)
+  • Task 6 depends on 3 (in done)
+
+Resolution options:
+  1. Move with dependencies: task-master move --from=5,6 --from-tag=backlog --to-tag=in-progress --with-dependencies
+  2. Break dependencies: task-master move --from=5,6 --from-tag=backlog --to-tag=in-progress --ignore-dependencies
+  3. Validate and fix dependencies: task-master validate-dependencies && task-master fix-dependencies
+  4. Move dependencies first: task-master move --from=2,3 --from-tag=backlog --to-tag=in-progress
+  5. Force move (may break dependencies): task-master move --from=5,6 --from-tag=backlog --to-tag=in-progress --force
+```
+
+### Subtask Movement Restrictions
+
+Subtasks cannot be moved directly between tags:
+
+```text
+❌ Cannot move subtask 5.2 directly between tags
+
+Subtask movement restriction:
+  • Subtasks cannot be moved directly between tags
+  • They must be promoted to full tasks first
+
+Resolution options:
+  1. Promote subtask to full task: task-master remove-subtask --id=5.2 --convert
+  2. Then move the promoted task: task-master move --from=5 --from-tag=backlog --to-tag=in-progress
+  3. Or move the parent task with all subtasks: task-master move --from=5 --from-tag=backlog --to-tag=in-progress --with-dependencies
+```
+
+### Invalid Tag Combinations
+
+When source and target tags are the same:
+
+```text
+❌ Invalid tag combination
+
+Error details:
+  • Source tag: "backlog"
+  • Target tag: "backlog"
+  • Reason: Source and target tags are identical
+
+Resolution options:
+  1. Use different tags for cross-tag moves
+  2. Use within-tag move: task-master move --from=<id> --to=<id> --tag=backlog
+  3. Check available tags: task-master tags
+```
+
+## Best Practices
+
+### 1. Check Dependencies First
+
+Before moving tasks, validate your dependencies:
+
+```bash
+# Check for dependency issues
+task-master validate-dependencies
+
+# Fix common dependency problems
+task-master fix-dependencies
+```
+
+### 2. Use Appropriate Flags
+
+- **`--with-dependencies`**: When you want to maintain task relationships
+- **`--ignore-dependencies`**: When you want to break cross-tag dependencies
+- **`--force`**: Only when you understand the consequences
+
+### 3. Organize by Context
+
+Use tags to organize work by:
+- **Development phases**: `backlog`, `in-progress`, `review`, `done`
+- **Feature branches**: `feature-auth`, `feature-dashboard`
+- **Team members**: `alice-tasks`, `bob-tasks`
+- **Project versions**: `v1.0`, `v2.0`
+
+### 4. Handle Subtasks Properly
+
+For subtasks, either:
+1. Promote the subtask to a full task first
+2. Move the parent task with all subtasks using `--with-dependencies`
+
+## Advanced Usage
+
+### Multiple Task Movement
+
+Move multiple tasks at once:
+
+```bash
+# Move multiple tasks with dependencies
+task-master move --from=5,6,7 --from-tag=backlog --to-tag=in-progress --with-dependencies
+
+# Move multiple tasks, breaking dependencies
+task-master move --from=5,6,7 --from-tag=backlog --to-tag=in-progress --ignore-dependencies
+```
+
+### Tag Creation
+
+Target tags are created automatically if they don't exist:
+
+```bash
+# This will create the "new-feature" tag if it doesn't exist
+task-master move --from=5 --from-tag=backlog --to-tag=new-feature
+```
+
+### Current Tag Fallback
+
+If `--from-tag` is not provided, the current tag is used:
+
+```bash
+# Uses current tag as source
+task-master move --from=5 --to-tag=in-progress
+```
+
+## MCP Integration
+
+The cross-tag move functionality is also available through MCP tools:
+
+```javascript
+// Move task with dependencies
+await moveTask({
+  from: "5",
+  fromTag: "backlog", 
+  toTag: "in-progress",
+  withDependencies: true
+});
+
+// Break dependencies
+await moveTask({
+  from: "5",
+  fromTag: "backlog",
+  toTag: "in-progress", 
+  ignoreDependencies: true
+});
+```
+
+## Troubleshooting
+
+### Common Issues
+
+1. **"Source tag not found"**: Check available tags with `task-master tags`
+2. **"Task not found"**: Verify task IDs with `task-master list`
+3. **"Cross-tag dependency conflicts"**: Use dependency resolution flags
+4. **"Cannot move subtask"**: Promote subtask first or move parent task
+
+### Getting Help
+
+```bash
+# Show move command help
+task-master move --help
+
+# Check available tags
+task-master tags
+
+# Validate dependencies
+task-master validate-dependencies
+
+# Fix dependency issues
+task-master fix-dependencies
+```
+
+## Examples
+
+### Scenario 1: Moving from Backlog to In-Progress
+
+```bash
+# Check for dependencies first
+task-master validate-dependencies
+
+# Move with dependencies
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress --with-dependencies
+```
+
+### Scenario 2: Breaking Dependencies
+
+```bash
+# Move task, breaking cross-tag dependencies
+task-master move --from=5 --from-tag=backlog --to-tag=done --ignore-dependencies
+```
+
+### Scenario 3: Force Move
+
+```bash
+# Force move despite conflicts
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress --force
+```
+
+### Scenario 4: Moving Subtasks
+
+```bash
+# Option 1: Promote subtask first
+task-master remove-subtask --id=5.2 --convert
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress
+
+# Option 2: Move parent with all subtasks
+task-master move --from=5 --from-tag=backlog --to-tag=in-progress --with-dependencies
+```

docs/models.md

@@ -1,4 +1,4 @@
-# Available Models as of July 23, 2025
+# Available Models as of August 12, 2025
 
 ## Main Models
 
@@ -24,6 +24,7 @@
 | openai      | gpt-4-1-mini                                   | —         | 0.4        | 1.6         |
 | openai      | gpt-4-1-nano                                   | —         | 0.1        | 0.4         |
 | openai      | gpt-4o-mini                                    | 0.3       | 0.15       | 0.6         |
+| openai      | gpt-5                                          | 0.749     | 5          | 20          |
 | google      | gemini-2.5-pro-preview-05-06                   | 0.638     | —          | —           |
 | google      | gemini-2.5-pro-preview-03-25                   | 0.638     | —          | —           |
 | google      | gemini-2.5-flash-preview-04-17                 | 0.604     | —          | —           |
@@ -67,6 +68,9 @@
 | openrouter  | mistralai/mistral-small-3.1-24b-instruct       | —         | 0.1        | 0.3         |
 | openrouter  | mistralai/devstral-small                       | —         | 0.1        | 0.3         |
 | openrouter  | mistralai/mistral-nemo                         | —         | 0.03       | 0.07        |
+| ollama      | gpt-oss:latest                                 | 0.607     | 0          | 0           |
+| ollama      | gpt-oss:20b                                    | 0.607     | 0          | 0           |
+| ollama      | gpt-oss:120b                                   | 0.624     | 0          | 0           |
 | ollama      | devstral:latest                                | —         | 0          | 0           |
 | ollama      | qwen3:latest                                   | —         | 0          | 0           |
 | ollama      | qwen3:14b                                      | —         | 0          | 0           |
@@ -134,6 +138,7 @@
 | openai      | gpt-4o                                         | 0.332     | 2.5        | 10          |
 | openai      | o3                                             | 0.5       | 2          | 8           |
 | openai      | o4-mini                                        | 0.45      | 1.1        | 4.4         |
+| openai      | gpt-5                                          | 0.749     | 5          | 20          |
 | google      | gemini-2.5-pro-preview-05-06                   | 0.638     | —          | —           |
 | google      | gemini-2.5-pro-preview-03-25                   | 0.638     | —          | —           |
 | google      | gemini-2.5-flash-preview-04-17                 | 0.604     | —          | —           |
@@ -172,6 +177,9 @@
 | openrouter  | qwen/qwen3-235b-a22b                           | —         | 0.14       | 2           |
 | openrouter  | mistralai/mistral-small-3.1-24b-instruct       | —         | 0.1        | 0.3         |
 | openrouter  | mistralai/mistral-nemo                         | —         | 0.03       | 0.07        |
+| ollama      | gpt-oss:latest                                 | 0.607     | 0          | 0           |
+| ollama      | gpt-oss:20b                                    | 0.607     | 0          | 0           |
+| ollama      | gpt-oss:120b                                   | 0.624     | 0          | 0           |
 | ollama      | devstral:latest                                | —         | 0          | 0           |
 | ollama      | qwen3:latest                                   | —         | 0          | 0           |
 | ollama      | qwen3:14b                                      | —         | 0          | 0           |

mcp-server/src/core/direct-functions/move-task-cross-tag.js

@@ -0,0 +1,203 @@
+/**
+ * Direct function wrapper for cross-tag task moves
+ */
+
+import { moveTasksBetweenTags } from '../../../../scripts/modules/task-manager/move-task.js';
+import { findTasksPath } from '../utils/path-utils.js';
+
+import {
+	enableSilentMode,
+	disableSilentMode
+} from '../../../../scripts/modules/utils.js';
+
+/**
+ * Move tasks between tags
+ * @param {Object} args - Function arguments
+ * @param {string} args.tasksJsonPath - Explicit path to the tasks.json file
+ * @param {string} args.sourceIds - Comma-separated IDs of tasks to move
+ * @param {string} args.sourceTag - Source tag name
+ * @param {string} args.targetTag - Target tag name
+ * @param {boolean} args.withDependencies - Move dependent tasks along with main task
+ * @param {boolean} args.ignoreDependencies - Break cross-tag dependencies during move
+ * @param {string} args.file - Alternative path to the tasks.json file
+ * @param {string} args.projectRoot - Project root directory
+ * @param {Object} log - Logger object
+ * @returns {Promise<{success: boolean, data?: Object, error?: Object}>}
+ */
+export async function moveTaskCrossTagDirect(args, log, context = {}) {
+	const { session } = context;
+	const { projectRoot } = args;
+
+	log.info(`moveTaskCrossTagDirect called with args: ${JSON.stringify(args)}`);
+
+	// Validate required parameters
+	if (!args.sourceIds) {
+		return {
+			success: false,
+			error: {
+				message: 'Source IDs are required',
+				code: 'MISSING_SOURCE_IDS'
+			}
+		};
+	}
+
+	if (!args.sourceTag) {
+		return {
+			success: false,
+			error: {
+				message: 'Source tag is required for cross-tag moves',
+				code: 'MISSING_SOURCE_TAG'
+			}
+		};
+	}
+
+	if (!args.targetTag) {
+		return {
+			success: false,
+			error: {
+				message: 'Target tag is required for cross-tag moves',
+				code: 'MISSING_TARGET_TAG'
+			}
+		};
+	}
+
+	// Validate that source and target tags are different
+	if (args.sourceTag === args.targetTag) {
+		return {
+			success: false,
+			error: {
+				message: `Source and target tags are the same ("${args.sourceTag}")`,
+				code: 'SAME_SOURCE_TARGET_TAG',
+				suggestions: [
+					'Use different tags for cross-tag moves',
+					'Use within-tag move: task-master move --from=<id> --to=<id> --tag=<tag>',
+					'Check available tags: task-master tags'
+				]
+			}
+		};
+	}
+
+	try {
+		// Find tasks.json path if not provided
+		let tasksPath = args.tasksJsonPath || args.file;
+		if (!tasksPath) {
+			if (!args.projectRoot) {
+				return {
+					success: false,
+					error: {
+						message:
+							'Project root is required if tasksJsonPath is not provided',
+						code: 'MISSING_PROJECT_ROOT'
+					}
+				};
+			}
+			tasksPath = findTasksPath(args, log);
+		}
+
+		// Enable silent mode to prevent console output during MCP operation
+		enableSilentMode();
+
+		try {
+			// Parse source IDs
+			const sourceIds = args.sourceIds.split(',').map((id) => id.trim());
+
+			// Prepare move options
+			const moveOptions = {
+				withDependencies: args.withDependencies || false,
+				ignoreDependencies: args.ignoreDependencies || false
+			};
+
+			// Call the core moveTasksBetweenTags function
+			const result = await moveTasksBetweenTags(
+				tasksPath,
+				sourceIds,
+				args.sourceTag,
+				args.targetTag,
+				moveOptions,
+				{ projectRoot }
+			);
+
+			return {
+				success: true,
+				data: {
+					...result,
+					message: `Successfully moved ${sourceIds.length} task(s) from "${args.sourceTag}" to "${args.targetTag}"`,
+					moveOptions,
+					sourceTag: args.sourceTag,
+					targetTag: args.targetTag
+				}
+			};
+		} finally {
+			// Restore console output - always executed regardless of success or error
+			disableSilentMode();
+		}
+	} catch (error) {
+		log.error(`Failed to move tasks between tags: ${error.message}`);
+		log.error(`Error code: ${error.code}, Error name: ${error.name}`);
+
+		// Enhanced error handling with structured error objects
+		let errorCode = 'MOVE_TASK_CROSS_TAG_ERROR';
+		let suggestions = [];
+
+		// Handle structured errors first
+		if (error.code === 'CROSS_TAG_DEPENDENCY_CONFLICTS') {
+			errorCode = 'CROSS_TAG_DEPENDENCY_CONFLICT';
+			suggestions = [
+				'Use --with-dependencies to move dependent tasks together',
+				'Use --ignore-dependencies to break cross-tag dependencies',
+				'Run task-master validate-dependencies to check for issues',
+				'Move dependencies first, then move the main task'
+			];
+		} else if (error.code === 'CANNOT_MOVE_SUBTASK') {
+			errorCode = 'SUBTASK_MOVE_RESTRICTION';
+			suggestions = [
+				'Promote subtask to full task first: task-master remove-subtask --id=<subtaskId> --convert',
+				'Move the parent task with all subtasks using --with-dependencies'
+			];
+		} else if (
+			error.code === 'TASK_NOT_FOUND' ||
+			error.code === 'INVALID_SOURCE_TAG' ||
+			error.code === 'INVALID_TARGET_TAG'
+		) {
+			errorCode = 'TAG_OR_TASK_NOT_FOUND';
+			suggestions = [
+				'Check available tags: task-master tags',
+				'Verify task IDs exist: task-master list',
+				'Check task details: task-master show <id>'
+			];
+		} else if (error.message.includes('cross-tag dependency conflicts')) {
+			// Fallback for legacy error messages
+			errorCode = 'CROSS_TAG_DEPENDENCY_CONFLICT';
+			suggestions = [
+				'Use --with-dependencies to move dependent tasks together',
+				'Use --ignore-dependencies to break cross-tag dependencies',
+				'Run task-master validate-dependencies to check for issues',
+				'Move dependencies first, then move the main task'
+			];
+		} else if (error.message.includes('Cannot move subtask')) {
+			// Fallback for legacy error messages
+			errorCode = 'SUBTASK_MOVE_RESTRICTION';
+			suggestions = [
+				'Promote subtask to full task first: task-master remove-subtask --id=<subtaskId> --convert',
+				'Move the parent task with all subtasks using --with-dependencies'
+			];
+		} else if (error.message.includes('not found')) {
+			// Fallback for legacy error messages
+			errorCode = 'TAG_OR_TASK_NOT_FOUND';
+			suggestions = [
+				'Check available tags: task-master tags',
+				'Verify task IDs exist: task-master list',
+				'Check task details: task-master show <id>'
+			];
+		}
+
+		return {
+			success: false,
+			error: {
+				message: error.message,
+				code: errorCode,
+				suggestions
+			}
+		};
+	}
+}

mcp-server/src/core/direct-functions/parse-prd.js

@@ -32,7 +32,7 @@ import { TASKMASTER_TASKS_FILE } from '../../../../src/constants/paths.js';
  * @returns {Promise<Object>} - Result object with success status and data/error information.
  */
 export async function parsePRDDirect(args, log, context = {}) {
-	const { session } = context;
+	const { session, reportProgress } = context;
 	// Extract projectRoot from args
 	const {
 		input: inputArg,
@@ -164,6 +164,7 @@ export async function parsePRDDirect(args, log, context = {}) {
 				force,
 				append,
 				research,
+				reportProgress,
 				commandName: 'parse-prd',
 				outputType: 'mcp'
 			},

mcp-server/src/core/direct-functions/scope-down.js

@@ -71,8 +71,8 @@ export async function scopeDownDirect(args, log, context = {}) {
 			};
 		}
 
-		// Parse task IDs
-		const taskIds = id.split(',').map((taskId) => taskId.trim());
+		// Parse task IDs - convert to numbers as expected by scopeDownTask
+		const taskIds = id.split(',').map((taskId) => parseInt(taskId.trim(), 10));
 
 		log.info(
 			`Scoping down tasks: ${taskIds.join(', ')}, strength: ${strength}, research: ${research}`
@@ -90,10 +90,10 @@ export async function scopeDownDirect(args, log, context = {}) {
 				projectRoot,
 				commandName: 'scope-down',
 				outputType: 'mcp',
-				tag
+				tag,
+				research
 			},
-			'json', // outputFormat
-			research
+			'json' // outputFormat
 		);
 
 		// Restore normal logging

mcp-server/src/core/direct-functions/scope-up.js

@@ -71,8 +71,8 @@ export async function scopeUpDirect(args, log, context = {}) {
 			};
 		}
 
-		// Parse task IDs
-		const taskIds = id.split(',').map((taskId) => taskId.trim());
+		// Parse task IDs - convert to numbers as expected by scopeUpTask
+		const taskIds = id.split(',').map((taskId) => parseInt(taskId.trim(), 10));
 
 		log.info(
 			`Scoping up tasks: ${taskIds.join(', ')}, strength: ${strength}, research: ${research}`
@@ -90,10 +90,10 @@ export async function scopeUpDirect(args, log, context = {}) {
 				projectRoot,
 				commandName: 'scope-up',
 				outputType: 'mcp',
-				tag
+				tag,
+				research
 			},
-			'json', // outputFormat
-			research
+			'json' // outputFormat
 		);
 
 		// Restore normal logging

mcp-server/src/core/task-master-core.js

@@ -31,6 +31,7 @@ import { removeTaskDirect } from './direct-functions/remove-task.js';
 import { initializeProjectDirect } from './direct-functions/initialize-project.js';
 import { modelsDirect } from './direct-functions/models.js';
 import { moveTaskDirect } from './direct-functions/move-task.js';
+import { moveTaskCrossTagDirect } from './direct-functions/move-task-cross-tag.js';
 import { researchDirect } from './direct-functions/research.js';
 import { addTagDirect } from './direct-functions/add-tag.js';
 import { deleteTagDirect } from './direct-functions/delete-tag.js';
@@ -72,6 +73,7 @@ export const directFunctions = new Map([
 	['initializeProjectDirect', initializeProjectDirect],
 	['modelsDirect', modelsDirect],
 	['moveTaskDirect', moveTaskDirect],
+	['moveTaskCrossTagDirect', moveTaskCrossTagDirect],
 	['researchDirect', researchDirect],
 	['addTagDirect', addTagDirect],
 	['deleteTagDirect', deleteTagDirect],
@@ -111,6 +113,7 @@ export {
 	initializeProjectDirect,
 	modelsDirect,
 	moveTaskDirect,
+	moveTaskCrossTagDirect,
 	researchDirect,
 	addTagDirect,
 	deleteTagDirect,

mcp-server/src/tools/move-task.js

@@ -9,7 +9,10 @@ import {
 	createErrorResponse,
 	withNormalizedProjectRoot
 } from './utils.js';
-import { moveTaskDirect } from '../core/task-master-core.js';
+import {
+	moveTaskDirect,
+	moveTaskCrossTagDirect
+} from '../core/task-master-core.js';
 import { findTasksPath } from '../core/utils/path-utils.js';
 import { resolveTag } from '../../../scripts/modules/utils.js';
 
@@ -29,8 +32,9 @@ export function registerMoveTaskTool(server) {
 				),
 			to: z
 				.string()
+				.optional()
 				.describe(
-					'ID of the destination (e.g., "7" or "7.3"). Must match the number of source IDs if comma-separated'
+					'ID of the destination (e.g., "7" or "7.3"). Required for within-tag moves. For cross-tag moves, if omitted, task will be moved to the target tag maintaining its ID'
 				),
 			file: z.string().optional().describe('Custom path to tasks.json file'),
 			projectRoot: z
@@ -38,101 +42,180 @@ export function registerMoveTaskTool(server) {
 				.describe(
 					'Root directory of the project (typically derived from session)'
 				),
-			tag: z.string().optional().describe('Tag context to operate on')
+			tag: z.string().optional().describe('Tag context to operate on'),
+			fromTag: z.string().optional().describe('Source tag for cross-tag moves'),
+			toTag: z.string().optional().describe('Target tag for cross-tag moves'),
+			withDependencies: z
+				.boolean()
+				.optional()
+				.describe('Move dependent tasks along with main task'),
+			ignoreDependencies: z
+				.boolean()
+				.optional()
+				.describe('Break cross-tag dependencies during move')
 		}),
 		execute: withNormalizedProjectRoot(async (args, { log, session }) => {
 			try {
-				const resolvedTag = resolveTag({
-					projectRoot: args.projectRoot,
-					tag: args.tag
-				});
-				// Find tasks.json path if not provided
-				let tasksJsonPath = args.file;
+				// Check if this is a cross-tag move
+				const isCrossTagMove =
+					args.fromTag && args.toTag && args.fromTag !== args.toTag;
 
-				if (!tasksJsonPath) {
-					tasksJsonPath = findTasksPath(args, log);
-				}
-
-				// Parse comma-separated IDs
-				const fromIds = args.from.split(',').map((id) => id.trim());
-				const toIds = args.to.split(',').map((id) => id.trim());
-
-				// Validate matching IDs count
-				if (fromIds.length !== toIds.length) {
-					return createErrorResponse(
-						'The number of source and destination IDs must match',
-						'MISMATCHED_ID_COUNT'
-					);
-				}
-
-				// If moving multiple tasks
-				if (fromIds.length > 1) {
-					const results = [];
-					// Move tasks one by one, only generate files on the last move
-					for (let i = 0; i < fromIds.length; i++) {
-						const fromId = fromIds[i];
-						const toId = toIds[i];
-
-						// Skip if source and destination are the same
-						if (fromId === toId) {
-							log.info(`Skipping ${fromId} -> ${toId} (same ID)`);
-							continue;
-						}
-
-						const shouldGenerateFiles = i === fromIds.length - 1;
-						const result = await moveTaskDirect(
-							{
-								sourceId: fromId,
-								destinationId: toId,
-								tasksJsonPath,
-								projectRoot: args.projectRoot,
-								tag: resolvedTag
-							},
-							log,
-							{ session }
+				if (isCrossTagMove) {
+					// Cross-tag move logic
+					if (!args.from) {
+						return createErrorResponse(
+							'Source IDs are required for cross-tag moves',
+							'MISSING_SOURCE_IDS'
 						);
-
-						if (!result.success) {
-							log.error(
-								`Failed to move ${fromId} to ${toId}: ${result.error.message}`
-							);
-						} else {
-							results.push(result.data);
-						}
 					}
 
+					// Warn if 'to' parameter is provided for cross-tag moves
+					if (args.to) {
+						log.warn(
+							'The "to" parameter is not used for cross-tag moves and will be ignored. Tasks retain their original IDs in the target tag.'
+						);
+					}
+
+					// Find tasks.json path if not provided
+					let tasksJsonPath = args.file;
+					if (!tasksJsonPath) {
+						tasksJsonPath = findTasksPath(args, log);
+					}
+
+					// Use cross-tag move function
 					return handleApiResult(
-						{
-							success: true,
-							data: {
-								moves: results,
-								message: `Successfully moved ${results.length} tasks`
-							}
-						},
-						log,
-						'Error moving multiple tasks',
-						undefined,
-						args.projectRoot
-					);
-				} else {
-					// Moving a single task
-					return handleApiResult(
-						await moveTaskDirect(
+						await moveTaskCrossTagDirect(
 							{
-								sourceId: args.from,
-								destinationId: args.to,
+								sourceIds: args.from,
+								sourceTag: args.fromTag,
+								targetTag: args.toTag,
+								withDependencies: args.withDependencies || false,
+								ignoreDependencies: args.ignoreDependencies || false,
 								tasksJsonPath,
-								projectRoot: args.projectRoot,
-								tag: resolvedTag
+								projectRoot: args.projectRoot
 							},
 							log,
 							{ session }
 						),
 						log,
-						'Error moving task',
+						'Error moving tasks between tags',
 						undefined,
 						args.projectRoot
 					);
+				} else {
+					// Within-tag move logic (existing functionality)
+					if (!args.to) {
+						return createErrorResponse(
+							'Destination ID is required for within-tag moves',
+							'MISSING_DESTINATION_ID'
+						);
+					}
+
+					const resolvedTag = resolveTag({
+						projectRoot: args.projectRoot,
+						tag: args.tag
+					});
+
+					// Find tasks.json path if not provided
+					let tasksJsonPath = args.file;
+					if (!tasksJsonPath) {
+						tasksJsonPath = findTasksPath(args, log);
+					}
+
+					// Parse comma-separated IDs
+					const fromIds = args.from.split(',').map((id) => id.trim());
+					const toIds = args.to.split(',').map((id) => id.trim());
+
+					// Validate matching IDs count
+					if (fromIds.length !== toIds.length) {
+						if (fromIds.length > 1) {
+							const results = [];
+							const skipped = [];
+							// Move tasks one by one, only generate files on the last move
+							for (let i = 0; i < fromIds.length; i++) {
+								const fromId = fromIds[i];
+								const toId = toIds[i];
+
+								// Skip if source and destination are the same
+								if (fromId === toId) {
+									log.info(`Skipping ${fromId} -> ${toId} (same ID)`);
+									skipped.push({ fromId, toId, reason: 'same ID' });
+									continue;
+								}
+
+								const shouldGenerateFiles = i === fromIds.length - 1;
+								const result = await moveTaskDirect(
+									{
+										sourceId: fromId,
+										destinationId: toId,
+										tasksJsonPath,
+										projectRoot: args.projectRoot,
+										tag: resolvedTag,
+										generateFiles: shouldGenerateFiles
+									},
+									log,
+									{ session }
+								);
+
+								if (!result.success) {
+									log.error(
+										`Failed to move ${fromId} to ${toId}: ${result.error.message}`
+									);
+								} else {
+									results.push(result.data);
+								}
+							}
+
+							return handleApiResult(
+								{
+									success: true,
+									data: {
+										moves: results,
+										skipped: skipped.length > 0 ? skipped : undefined,
+										message: `Successfully moved ${results.length} tasks${skipped.length > 0 ? `, skipped ${skipped.length}` : ''}`
+									}
+								},
+								log,
+								'Error moving multiple tasks',
+								undefined,
+								args.projectRoot
+							);
+						}
+						return handleApiResult(
+							{
+								success: true,
+								data: {
+									moves: results,
+									skippedMoves: skippedMoves,
+									message: `Successfully moved ${results.length} tasks${skippedMoves.length > 0 ? `, skipped ${skippedMoves.length} moves` : ''}`
+								}
+							},
+							log,
+							'Error moving multiple tasks',
+							undefined,
+							args.projectRoot
+						);
+					} else {
+						// Moving a single task
+						return handleApiResult(
+							await moveTaskDirect(
+								{
+									sourceId: args.from,
+									destinationId: args.to,
+									tasksJsonPath,
+									projectRoot: args.projectRoot,
+									tag: resolvedTag,
+									generateFiles: true
+								},
+								log,
+								{ session }
+							),
+							log,
+							'Error moving task',
+							undefined,
+							args.projectRoot
+						);
+					}
 				}
 			} catch (error) {
 				return createErrorResponse(

mcp-server/src/tools/parse-prd.js

@@ -7,7 +7,8 @@ import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot,
-	createErrorResponse
+	createErrorResponse,
+	checkProgressCapability
 } from './utils.js';
 import { parsePRDDirect } from '../core/task-master-core.js';
 import {
@@ -64,31 +65,37 @@ export function registerParsePRDTool(server) {
 				.optional()
 				.describe('Append generated tasks to existing file.')
 		}),
-		execute: withNormalizedProjectRoot(async (args, { log, session }) => {
-			try {
-				const resolvedTag = resolveTag({
-					projectRoot: args.projectRoot,
-					tag: args.tag
-				});
-				const result = await parsePRDDirect(
-					{
-						...args,
-						tag: resolvedTag
-					},
-					log,
-					{ session }
-				);
-				return handleApiResult(
-					result,
-					log,
-					'Error parsing PRD',
-					undefined,
-					args.projectRoot
-				);
-			} catch (error) {
-				log.error(`Error in parse_prd: ${error.message}`);
-				return createErrorResponse(`Failed to parse PRD: ${error.message}`);
+		execute: withNormalizedProjectRoot(
+			async (args, { log, session, reportProgress }) => {
+				try {
+					const resolvedTag = resolveTag({
+						projectRoot: args.projectRoot,
+						tag: args.tag
+					});
+					const progressCapability = checkProgressCapability(
+						reportProgress,
+						log
+					);
+					const result = await parsePRDDirect(
+						{
+							...args,
+							tag: resolvedTag
+						},
+						log,
+						{ session, reportProgress: progressCapability }
+					);
+					return handleApiResult(
+						result,
+						log,
+						'Error parsing PRD',
+						undefined,
+						args.projectRoot
+					);
+				} catch (error) {
+					log.error(`Error in parse_prd: ${error.message}`);
+					return createErrorResponse(`Failed to parse PRD: ${error.message}`);
+				}
 			}
-		})
+		)
 	});
 }

mcp-server/src/tools/utils.js

@@ -778,6 +778,77 @@ function withNormalizedProjectRoot(executeFn) {
 	};
 }
 
+/**
+ * Checks progress reporting capability and returns the validated function or undefined.
+ *
+ * STANDARD PATTERN for AI-powered, long-running operations (parse-prd, expand-task, expand-all, analyze):
+ *
+ * This helper should be used as the first step in any MCP tool that performs long-running
+ * AI operations. It validates the availability of progress reporting and provides consistent
+ * logging about the capability status.
+ *
+ * Operations that should use this pattern:
+ * - parse-prd: Parsing PRD documents with AI
+ * - expand-task: Expanding tasks into subtasks
+ * - expand-all: Expanding all tasks in batch
+ * - analyze-complexity: Analyzing task complexity
+ * - update-task: Updating tasks with AI assistance
+ * - add-task: Creating new tasks with AI
+ * - Any operation that makes AI service calls
+ *
+ * @example Basic usage in a tool's execute function:
+ * ```javascript
+ * import { checkProgressCapability } from './utils.js';
+ *
+ * async execute(args, context) {
+ *   const { log, reportProgress, session } = context;
+ *
+ *   // Always validate progress capability first
+ *   const progressCapability = checkProgressCapability(reportProgress, log);
+ *
+ *   // Pass to direct function - it handles undefined gracefully
+ *   const result = await expandTask(taskId, numSubtasks, {
+ *     session,
+ *     reportProgress: progressCapability,
+ *     mcpLog: log
+ *   });
+ * }
+ * ```
+ *
+ * @example With progress reporting available:
+ * ```javascript
+ * // When reportProgress is available, users see real-time updates:
+ * // "Starting PRD analysis (Input: 5432 tokens)..."
+ * // "Task 1/10 - Implement user authentication"
+ * // "Task 2/10 - Create database schema"
+ * // "Task Generation Completed | Tokens: 5432/1234"
+ * ```
+ *
+ * @example Without progress reporting (graceful degradation):
+ * ```javascript
+ * // When reportProgress is not available:
+ * // - Operation runs normally without progress updates
+ * // - Debug log: "reportProgress not available - operation will run without progress updates"
+ * // - User gets final result after completion
+ * ```
+ *
+ * @param {Function|undefined} reportProgress - The reportProgress function from MCP context.
+ *                                             Expected signature: async (progress: {progress: number, total: number, message: string}) => void
+ * @param {Object} log - Logger instance with debug, info, warn, error methods
+ * @returns {Function|undefined} The validated reportProgress function or undefined if not available
+ */
+function checkProgressCapability(reportProgress, log) {
+	// Validate that reportProgress is available for long-running operations
+	if (typeof reportProgress !== 'function') {
+		log.debug(
+			'reportProgress not available - operation will run without progress updates'
+		);
+		return undefined;
+	}
+
+	return reportProgress;
+}
+
 // Ensure all functions are exported
 export {
 	getProjectRoot,
@@ -792,5 +863,6 @@ export {
 	createLogWrapper,
 	normalizeProjectRoot,
 	getRawProjectRootFromSession,
-	withNormalizedProjectRoot
+	withNormalizedProjectRoot,
+	checkProgressCapability
 };

package.json

@@ -1,6 +1,6 @@
 {
 	"name": "task-master-ai",
-	"version": "0.23.0",
+	"version": "0.24.0",
 	"description": "A task management system for ambitious AI-driven development that doesn't overwhelm and confuse Cursor.",
 	"main": "index.js",
 	"type": "module",
@@ -54,12 +54,14 @@
 		"@aws-sdk/credential-providers": "^3.817.0",
 		"@inquirer/search": "^3.0.15",
 		"@openrouter/ai-sdk-provider": "^0.4.5",
+		"@streamparser/json": "^0.0.22",
 		"ai": "^4.3.10",
 		"ajv": "^8.17.1",
 		"ajv-formats": "^3.0.1",
 		"boxen": "^8.0.1",
 		"chalk": "^5.4.1",
 		"cli-highlight": "^2.1.11",
+		"cli-progress": "^3.12.0",
 		"cli-table3": "^0.6.5",
 		"commander": "^11.1.0",
 		"cors": "^2.8.5",
@@ -73,6 +75,7 @@
 		"helmet": "^8.1.0",
 		"inquirer": "^12.5.0",
 		"jsonc-parser": "^3.3.1",
+		"jsonrepair": "^3.13.0",
 		"jsonwebtoken": "^9.0.2",
 		"lru-cache": "^10.2.0",
 		"ollama-ai-provider": "^1.2.0",

scripts/modules/ai-services-unified.js

@@ -91,93 +91,117 @@ function _getProvider(providerName) {
 
 // Helper function to get cost for a specific model
 function _getCostForModel(providerName, modelId) {
+	const DEFAULT_COST = { inputCost: 0, outputCost: 0, currency: 'USD' };
+
 	if (!MODEL_MAP || !MODEL_MAP[providerName]) {
 		log(
 			'warn',
 			`Provider "${providerName}" not found in MODEL_MAP. Cannot determine cost for model ${modelId}.`
 		);
-		return { inputCost: 0, outputCost: 0, currency: 'USD' }; // Default to zero cost
+		return DEFAULT_COST;
 	}
 
 	const modelData = MODEL_MAP[providerName].find((m) => m.id === modelId);
 
-	if (!modelData || !modelData.cost_per_1m_tokens) {
+	if (!modelData?.cost_per_1m_tokens) {
 		log(
 			'debug',
 			`Cost data not found for model "${modelId}" under provider "${providerName}". Assuming zero cost.`
 		);
-		return { inputCost: 0, outputCost: 0, currency: 'USD' }; // Default to zero cost
+		return DEFAULT_COST;
 	}
 
-	// Ensure currency is part of the returned object, defaulting if not present
-	const currency = modelData.cost_per_1m_tokens.currency || 'USD';
-
+	const costs = modelData.cost_per_1m_tokens;
 	return {
-		inputCost: modelData.cost_per_1m_tokens.input || 0,
-		outputCost: modelData.cost_per_1m_tokens.output || 0,
-		currency: currency
+		inputCost: costs.input || 0,
+		outputCost: costs.output || 0,
+		currency: costs.currency || 'USD'
 	};
 }
 
+/**
+ * Calculate cost from token counts and cost per million
+ * @param {number} inputTokens - Number of input tokens
+ * @param {number} outputTokens - Number of output tokens
+ * @param {number} inputCost - Cost per million input tokens
+ * @param {number} outputCost - Cost per million output tokens
+ * @returns {number} Total calculated cost
+ */
+function _calculateCost(inputTokens, outputTokens, inputCost, outputCost) {
+	const calculatedCost =
+		((inputTokens || 0) / 1_000_000) * inputCost +
+		((outputTokens || 0) / 1_000_000) * outputCost;
+	return parseFloat(calculatedCost.toFixed(6));
+}
+
 // Helper function to get tag information for responses
 function _getTagInfo(projectRoot) {
+	const DEFAULT_TAG_INFO = { currentTag: 'master', availableTags: ['master'] };
+
 	try {
 		if (!projectRoot) {
-			return { currentTag: 'master', availableTags: ['master'] };
+			return DEFAULT_TAG_INFO;
 		}
 
-		const currentTag = getCurrentTag(projectRoot);
+		const currentTag = getCurrentTag(projectRoot) || 'master';
+		const availableTags = _readAvailableTags(projectRoot);
 
-		// Read available tags from tasks.json
-		let availableTags = ['master']; // Default fallback
-		try {
-			const path = require('path');
-			const fs = require('fs');
-			const tasksPath = path.join(
-				projectRoot,
-				'.taskmaster',
-				'tasks',
-				'tasks.json'
-			);
-
-			if (fs.existsSync(tasksPath)) {
-				const tasksData = JSON.parse(fs.readFileSync(tasksPath, 'utf8'));
-				if (tasksData && typeof tasksData === 'object') {
-					// Check if it's tagged format (has tag-like keys with tasks arrays)
-					const potentialTags = Object.keys(tasksData).filter(
-						(key) =>
-							tasksData[key] &&
-							typeof tasksData[key] === 'object' &&
-							Array.isArray(tasksData[key].tasks)
-					);
-
-					if (potentialTags.length > 0) {
-						availableTags = potentialTags;
-					}
-				}
-			}
-		} catch (readError) {
-			// Silently fall back to default if we can't read tasks file
-			if (getDebugFlag()) {
-				log(
-					'debug',
-					`Could not read tasks file for available tags: ${readError.message}`
-				);
-			}
-		}
-
-		return {
-			currentTag: currentTag || 'master',
-			availableTags: availableTags
-		};
+		return { currentTag, availableTags };
 	} catch (error) {
 		if (getDebugFlag()) {
 			log('debug', `Error getting tag information: ${error.message}`);
 		}
-		return { currentTag: 'master', availableTags: ['master'] };
+		return DEFAULT_TAG_INFO;
 	}
 }
 
+// Extract method for reading available tags
+function _readAvailableTags(projectRoot) {
+	const DEFAULT_TAGS = ['master'];
+
+	try {
+		const path = require('path');
+		const fs = require('fs');
+		const tasksPath = path.join(
+			projectRoot,
+			'.taskmaster',
+			'tasks',
+			'tasks.json'
+		);
+
+		if (!fs.existsSync(tasksPath)) {
+			return DEFAULT_TAGS;
+		}
+
+		const tasksData = JSON.parse(fs.readFileSync(tasksPath, 'utf8'));
+		if (!tasksData || typeof tasksData !== 'object') {
+			return DEFAULT_TAGS;
+		}
+
+		// Check if it's tagged format (has tag-like keys with tasks arrays)
+		const potentialTags = Object.keys(tasksData).filter((key) =>
+			_isValidTaggedTask(tasksData[key])
+		);
+
+		return potentialTags.length > 0 ? potentialTags : DEFAULT_TAGS;
+	} catch (readError) {
+		if (getDebugFlag()) {
+			log(
+				'debug',
+				`Could not read tasks file for available tags: ${readError.message}`
+			);
+		}
+		return DEFAULT_TAGS;
+	}
+}
+
+// Helper to validate tagged task structure
+function _isValidTaggedTask(taskData) {
+	return (
+		taskData && typeof taskData === 'object' && Array.isArray(taskData.tasks)
+	);
+}
+
 // --- Configuration for Retries ---
 const MAX_RETRIES = 2;
 const INITIAL_RETRY_DELAY_MS = 1000;
@@ -244,6 +268,65 @@ function _extractErrorMessage(error) {
 	}
 }
 
+/**
+ * Get role configuration (provider and model) based on role type
+ * @param {string} role - The role ('main', 'research', 'fallback')
+ * @param {string} projectRoot - Project root path
+ * @returns {Object|null} Configuration object with provider and modelId
+ */
+function _getRoleConfiguration(role, projectRoot) {
+	const roleConfigs = {
+		main: {
+			provider: getMainProvider(projectRoot),
+			modelId: getMainModelId(projectRoot)
+		},
+		research: {
+			provider: getResearchProvider(projectRoot),
+			modelId: getResearchModelId(projectRoot)
+		},
+		fallback: {
+			provider: getFallbackProvider(projectRoot),
+			modelId: getFallbackModelId(projectRoot)
+		}
+	};
+
+	return roleConfigs[role] || null;
+}
+
+/**
+ * Get Vertex AI specific configuration
+ * @param {string} projectRoot - Project root path
+ * @param {Object} session - Session object
+ * @returns {Object} Vertex AI configuration parameters
+ */
+function _getVertexConfiguration(projectRoot, session) {
+	const projectId =
+		getVertexProjectId(projectRoot) ||
+		resolveEnvVariable('VERTEX_PROJECT_ID', session, projectRoot);
+
+	const location =
+		getVertexLocation(projectRoot) ||
+		resolveEnvVariable('VERTEX_LOCATION', session, projectRoot) ||
+		'us-central1';
+
+	const credentialsPath = resolveEnvVariable(
+		'GOOGLE_APPLICATION_CREDENTIALS',
+		session,
+		projectRoot
+	);
+
+	log(
+		'debug',
+		`Using Vertex AI configuration: Project ID=${projectId}, Location=${location}`
+	);
+
+	return {
+		projectId,
+		location,
+		...(credentialsPath && { credentials: { credentialsFromEnv: true } })
+	};
+}
+
 /**
  * Internal helper to resolve the API key for a given provider.
  * @param {string} providerName - The name of the provider (lowercase).
@@ -424,18 +507,13 @@ async function _unifiedServiceRunner(serviceType, params) {
 		let telemetryData = null;
 
 		try {
-			log('info', `New AI service call with role: ${currentRole}`);
+			log('debug', `New AI service call with role: ${currentRole}`);
 
-			if (currentRole === 'main') {
-				providerName = getMainProvider(effectiveProjectRoot);
-				modelId = getMainModelId(effectiveProjectRoot);
-			} else if (currentRole === 'research') {
-				providerName = getResearchProvider(effectiveProjectRoot);
-				modelId = getResearchModelId(effectiveProjectRoot);
-			} else if (currentRole === 'fallback') {
-				providerName = getFallbackProvider(effectiveProjectRoot);
-				modelId = getFallbackModelId(effectiveProjectRoot);
-			} else {
+			const roleConfig = _getRoleConfiguration(
+				currentRole,
+				effectiveProjectRoot
+			);
+			if (!roleConfig) {
 				log(
 					'error',
 					`Unknown role encountered in _unifiedServiceRunner: ${currentRole}`
@@ -444,6 +522,8 @@ async function _unifiedServiceRunner(serviceType, params) {
 					lastError || new Error(`Unknown AI role specified: ${currentRole}`);
 				continue;
 			}
+			providerName = roleConfig.provider;
+			modelId = roleConfig.modelId;
 
 			if (!providerName || !modelId) {
 				log(
@@ -517,41 +597,9 @@ async function _unifiedServiceRunner(serviceType, params) {
 
 			// Handle Vertex AI specific configuration
 			if (providerName?.toLowerCase() === 'vertex') {
-				// Get Vertex project ID and location
-				const projectId =
-					getVertexProjectId(effectiveProjectRoot) ||
-					resolveEnvVariable(
-						'VERTEX_PROJECT_ID',
-						session,
-						effectiveProjectRoot
-					);
-
-				const location =
-					getVertexLocation(effectiveProjectRoot) ||
-					resolveEnvVariable(
-						'VERTEX_LOCATION',
-						session,
-						effectiveProjectRoot
-					) ||
-					'us-central1';
-
-				// Get credentials path if available
-				const credentialsPath = resolveEnvVariable(
-					'GOOGLE_APPLICATION_CREDENTIALS',
-					session,
-					effectiveProjectRoot
-				);
-
-				// Add Vertex-specific parameters
-				providerSpecificParams = {
-					projectId,
-					location,
-					...(credentialsPath && { credentials: { credentialsFromEnv: true } })
-				};
-
-				log(
-					'debug',
-					`Using Vertex AI configuration: Project ID=${projectId}, Location=${location}`
+				providerSpecificParams = _getVertexConfiguration(
+					effectiveProjectRoot,
+					session
 				);
 			}
 
@@ -594,7 +642,8 @@ async function _unifiedServiceRunner(serviceType, params) {
 				temperature: roleParams.temperature,
 				messages,
 				...(baseURL && { baseURL }),
-				...(serviceType === 'generateObject' && { schema, objectName }),
+				...((serviceType === 'generateObject' ||
+					serviceType === 'streamObject') && { schema, objectName }),
 				...providerSpecificParams,
 				...restApiParams
 			};
@@ -635,7 +684,10 @@ async function _unifiedServiceRunner(serviceType, params) {
 				finalMainResult = providerResponse.text;
 			} else if (serviceType === 'generateObject') {
 				finalMainResult = providerResponse.object;
-			} else if (serviceType === 'streamText') {
+			} else if (
+				serviceType === 'streamText' ||
+				serviceType === 'streamObject'
+			) {
 				finalMainResult = providerResponse;
 			} else {
 				log(
@@ -651,7 +703,9 @@ async function _unifiedServiceRunner(serviceType, params) {
 			return {
 				mainResult: finalMainResult,
 				telemetryData: telemetryData,
-				tagInfo: tagInfo
+				tagInfo: tagInfo,
+				providerName: providerName,
+				modelId: modelId
 			};
 		} catch (error) {
 			const cleanMessage = _extractErrorMessage(error);
@@ -732,6 +786,31 @@ async function streamTextService(params) {
 	return _unifiedServiceRunner('streamText', combinedParams);
 }
 
+/**
+ * Unified service function for streaming structured objects.
+ * Uses Vercel AI SDK's streamObject for proper JSON streaming.
+ *
+ * @param {object} params - Parameters for the service call.
+ * @param {string} params.role - The initial client role ('main', 'research', 'fallback').
+ * @param {object} [params.session=null] - Optional MCP session object.
+ * @param {string} [params.projectRoot=null] - Optional project root path for .env fallback.
+ * @param {import('zod').ZodSchema} params.schema - The Zod schema for the expected object.
+ * @param {string} params.prompt - The prompt for the AI.
+ * @param {string} [params.systemPrompt] - Optional system prompt.
+ * @param {string} params.commandName - Name of the command invoking the service.
+ * @param {string} [params.outputType='cli'] - 'cli' or 'mcp'.
+ * @returns {Promise<object>} Result object containing the stream and usage data.
+ */
+async function streamObjectService(params) {
+	const defaults = { outputType: 'cli' };
+	const combinedParams = { ...defaults, ...params };
+	// Stream object requires a schema
+	if (!combinedParams.schema) {
+		throw new Error('streamObjectService requires a schema parameter');
+	}
+	return _unifiedServiceRunner('streamObject', combinedParams);
+}
+
 /**
  * Unified service function for generating structured objects.
  * Handles client retrieval, retries, and fallback sequence.
@@ -792,9 +871,12 @@ async function logAiUsage({
 			modelId
 		);
 
-		const totalCost =
-			((inputTokens || 0) / 1_000_000) * inputCost +
-			((outputTokens || 0) / 1_000_000) * outputCost;
+		const totalCost = _calculateCost(
+			inputTokens,
+			outputTokens,
+			inputCost,
+			outputCost
+		);
 
 		const telemetryData = {
 			timestamp,
@@ -805,7 +887,7 @@ async function logAiUsage({
 			inputTokens: inputTokens || 0,
 			outputTokens: outputTokens || 0,
 			totalTokens,
-			totalCost: parseFloat(totalCost.toFixed(6)),
+			totalCost,
 			currency // Add currency to the telemetry data
 		};
 
@@ -828,6 +910,7 @@ async function logAiUsage({
 export {
 	generateTextService,
 	streamTextService,
+	streamObjectService,
 	generateObjectService,
 	logAiUsage
 };

scripts/modules/commands.js

@@ -48,6 +48,12 @@ import {
 	validateStrength
 } from './task-manager.js';
 
+import {
+	moveTasksBetweenTags,
+	MoveTaskError,
+	MOVE_ERROR_CODES
+} from './task-manager/move-task.js';
+
 import {
 	createTag,
 	deleteTag,
@@ -61,7 +67,9 @@ import {
 	addDependency,
 	removeDependency,
 	validateDependenciesCommand,
-	fixDependenciesCommand
+	fixDependenciesCommand,
+	DependencyError,
+	DEPENDENCY_ERROR_CODES
 } from './dependency-manager.js';
 
 import {
@@ -103,7 +111,11 @@ import {
 	displayAiUsageSummary,
 	displayMultipleTasksSummary,
 	displayTaggedTasksFYI,
-	displayCurrentTagIndicator
+	displayCurrentTagIndicator,
+	displayCrossTagDependencyError,
+	displaySubtaskMoveError,
+	displayInvalidTagCombinationError,
+	displayDependencyValidationHints
 } from './ui.js';
 import {
 	confirmProfilesRemove,
@@ -900,8 +912,6 @@ function registerCommands(programInstance) {
 				return true;
 			}
 
-			let spinner;
-
 			try {
 				if (!(await confirmOverwriteIfNeeded())) return;
 
@@ -918,7 +928,6 @@ function registerCommands(programInstance) {
 					);
 				}
 
-				spinner = ora('Parsing PRD and generating tasks...\n').start();
 				// Handle case where getTasksPath() returns null
 				const outputPath =
 					taskMaster.getTasksPath() ||
@@ -930,13 +939,8 @@ function registerCommands(programInstance) {
 					projectRoot: taskMaster.getProjectRoot(),
 					tag: tag
 				});
-				spinner.succeed('Tasks generated successfully!');
 			} catch (error) {
-				if (spinner) {
-					spinner.fail(`Error parsing PRD: ${error.message}`);
-				} else {
-					console.error(chalk.red(`Error parsing PRD: ${error.message}`));
-				}
+				console.error(chalk.red(`Error parsing PRD: ${error.message}`));
 				process.exit(1);
 			}
 		});
@@ -1479,7 +1483,8 @@ function registerCommands(programInstance) {
 					projectRoot: taskMaster.getProjectRoot(),
 					tag,
 					commandName: 'scope-up',
-					outputType: 'cli'
+					outputType: 'cli',
+					research: options.research || false
 				};
 
 				const result = await scopeUpTask(
@@ -1605,7 +1610,8 @@ function registerCommands(programInstance) {
 					projectRoot: taskMaster.getProjectRoot(),
 					tag,
 					commandName: 'scope-down',
-					outputType: 'cli'
+					outputType: 'cli',
+					research: options.research || false
 				};
 
 				const result = await scopeDownTask(
@@ -1751,6 +1757,7 @@ function registerCommands(programInstance) {
 		)
 		.option('-s, --status <status>', 'Filter by status')
 		.option('--with-subtasks', 'Show subtasks for each task')
+		.option('-c, --compact', 'Display tasks in compact one-line format')
 		.option('--tag <tag>', 'Specify tag context for task operations')
 		.action(async (options) => {
 			// Initialize TaskMaster
@@ -1768,18 +1775,21 @@ function registerCommands(programInstance) {
 
 			const statusFilter = options.status;
 			const withSubtasks = options.withSubtasks || false;
+			const compact = options.compact || false;
 			const tag = taskMaster.getCurrentTag();
 			// Show current tag context
 			displayCurrentTagIndicator(tag);
 
-			console.log(
-				chalk.blue(`Listing tasks from: ${taskMaster.getTasksPath()}`)
-			);
-			if (statusFilter) {
-				console.log(chalk.blue(`Filtering by status: ${statusFilter}`));
-			}
-			if (withSubtasks) {
-				console.log(chalk.blue('Including subtasks in listing'));
+			if (!compact) {
+				console.log(
+					chalk.blue(`Listing tasks from: ${taskMaster.getTasksPath()}`)
+				);
+				if (statusFilter) {
+					console.log(chalk.blue(`Filtering by status: ${statusFilter}`));
+				}
+				if (withSubtasks) {
+					console.log(chalk.blue('Including subtasks in listing'));
+				}
 			}
 
 			await listTasks(
@@ -1787,7 +1797,7 @@ function registerCommands(programInstance) {
 				statusFilter,
 				taskMaster.getComplexityReportPath(),
 				withSubtasks,
-				'text',
+				compact ? 'compact' : 'text',
 				{ projectRoot: taskMaster.getProjectRoot(), tag }
 			);
 		});
@@ -4032,7 +4042,9 @@ Examples:
 	// move-task command
 	programInstance
 		.command('move')
-		.description('Move a task or subtask to a new position')
+		.description(
+			'Move tasks between tags or reorder within tags. Supports cross-tag moves with dependency resolution options.'
+		)
 		.option(
 			'-f, --file <file>',
 			'Path to the tasks file',
@@ -4047,55 +4059,202 @@ Examples:
 			'ID of the destination (e.g., "7" or "7.3"). Must match the number of source IDs if comma-separated'
 		)
 		.option('--tag <tag>', 'Specify tag context for task operations')
+		.option('--from-tag <tag>', 'Source tag for cross-tag moves')
+		.option('--to-tag <tag>', 'Target tag for cross-tag moves')
+		.option('--with-dependencies', 'Move dependent tasks along with main task')
+		.option('--ignore-dependencies', 'Break cross-tag dependencies during move')
 		.action(async (options) => {
-			// Initialize TaskMaster
-			const taskMaster = initTaskMaster({
-				tasksPath: options.file || true,
-				tag: options.tag
-			});
-
-			const sourceId = options.from;
-			const destinationId = options.to;
-			const tag = taskMaster.getCurrentTag();
-
-			if (!sourceId || !destinationId) {
-				console.error(
-					chalk.red('Error: Both --from and --to parameters are required')
-				);
+			// Helper function to show move command help - defined in scope for proper encapsulation
+			function showMoveHelp() {
 				console.log(
-					chalk.yellow(
-						'Usage: task-master move --from=<sourceId> --to=<destinationId>'
-					)
+					chalk.white.bold('Move Command Help') +
+						'\n\n' +
+						chalk.cyan('Move tasks between tags or reorder within tags.') +
+						'\n\n' +
+						chalk.yellow.bold('Within-Tag Moves:') +
+						'\n' +
+						chalk.white('  task-master move --from=5 --to=7') +
+						'\n' +
+						chalk.white('  task-master move --from=5.2 --to=7.3') +
+						'\n' +
+						chalk.white('  task-master move --from=5,6,7 --to=10,11,12') +
+						'\n\n' +
+						chalk.yellow.bold('Cross-Tag Moves:') +
+						'\n' +
+						chalk.white(
+							'  task-master move --from=5 --from-tag=backlog --to-tag=in-progress'
+						) +
+						'\n' +
+						chalk.white(
+							'  task-master move --from=5,6 --from-tag=backlog --to-tag=done'
+						) +
+						'\n\n' +
+						chalk.yellow.bold('Dependency Resolution:') +
+						'\n' +
+						chalk.white('  # Move with dependencies') +
+						'\n' +
+						chalk.white(
+							'  task-master move --from=5 --from-tag=backlog --to-tag=in-progress --with-dependencies'
+						) +
+						'\n\n' +
+						chalk.white('  # Break dependencies') +
+						'\n' +
+						chalk.white(
+							'  task-master move --from=5 --from-tag=backlog --to-tag=in-progress --ignore-dependencies'
+						) +
+						'\n\n' +
+						chalk.white('  # Force move (may break dependencies)') +
+						'\n' +
+						chalk.white(
+							'  task-master move --from=5 --from-tag=backlog --to-tag=in-progress --force'
+						) +
+						'\n\n' +
+						chalk.yellow.bold('Best Practices:') +
+						'\n' +
+						chalk.white(
+							'  • Use --with-dependencies to move dependent tasks together'
+						) +
+						'\n' +
+						chalk.white(
+							'  • Use --ignore-dependencies to break cross-tag dependencies'
+						) +
+						'\n' +
+						chalk.white(
+							'  • Use --force only when you understand the consequences'
+						) +
+						'\n' +
+						chalk.white(
+							'  • Check dependencies first: task-master validate-dependencies'
+						) +
+						'\n' +
+						chalk.white(
+							'  • Fix dependency issues: task-master fix-dependencies'
+						) +
+						'\n\n' +
+						chalk.yellow.bold('Error Resolution:') +
+						'\n' +
+						chalk.white(
+							'  • Cross-tag dependency conflicts: Use --with-dependencies or --ignore-dependencies'
+						) +
+						'\n' +
+						chalk.white(
+							'  • Subtask movement: Promote subtask first with remove-subtask --convert'
+						) +
+						'\n' +
+						chalk.white(
+							'  • Invalid tags: Check available tags with task-master tags'
+						) +
+						'\n\n' +
+						chalk.gray('For more help, run: task-master move --help')
 				);
-				process.exit(1);
 			}
 
-			// Check if we're moving multiple tasks (comma-separated IDs)
-			const sourceIds = sourceId.split(',').map((id) => id.trim());
-			const destinationIds = destinationId.split(',').map((id) => id.trim());
+			// Helper function to handle cross-tag move logic
+			async function handleCrossTagMove(moveContext, options) {
+				const { sourceId, sourceTag, toTag, taskMaster } = moveContext;
 
-			// Validate that the number of source and destination IDs match
-			if (sourceIds.length !== destinationIds.length) {
-				console.error(
-					chalk.red(
-						'Error: The number of source and destination IDs must match'
-					)
-				);
-				console.log(
-					chalk.yellow('Example: task-master move --from=5,6,7 --to=10,11,12')
-				);
-				process.exit(1);
-			}
+				if (!sourceId) {
+					console.error(
+						chalk.red('Error: --from parameter is required for cross-tag moves')
+					);
+					showMoveHelp();
+					process.exit(1);
+				}
+
+				const sourceIds = sourceId.split(',').map((id) => id.trim());
+				const moveOptions = {
+					withDependencies: options.withDependencies || false,
+					ignoreDependencies: options.ignoreDependencies || false
+				};
 
-			// If moving multiple tasks
-			if (sourceIds.length > 1) {
 				console.log(
 					chalk.blue(
-						`Moving multiple tasks: ${sourceIds.join(', ')} to ${destinationIds.join(', ')}...`
+						`Moving tasks ${sourceIds.join(', ')} from "${sourceTag}" to "${toTag}"...`
 					)
 				);
 
-				try {
+				const result = await moveTasksBetweenTags(
+					taskMaster.getTasksPath(),
+					sourceIds,
+					sourceTag,
+					toTag,
+					moveOptions,
+					{ projectRoot: taskMaster.getProjectRoot() }
+				);
+
+				console.log(chalk.green(`✓ ${result.message}`));
+
+				// Check if source tag still contains tasks before regenerating files
+				const tasksData = readJSON(
+					taskMaster.getTasksPath(),
+					taskMaster.getProjectRoot(),
+					sourceTag
+				);
+				const sourceTagHasTasks =
+					tasksData &&
+					Array.isArray(tasksData.tasks) &&
+					tasksData.tasks.length > 0;
+
+				// Generate task files for the affected tags
+				await generateTaskFiles(
+					taskMaster.getTasksPath(),
+					path.dirname(taskMaster.getTasksPath()),
+					{ tag: toTag, projectRoot: taskMaster.getProjectRoot() }
+				);
+
+				// Only regenerate source tag files if it still contains tasks
+				if (sourceTagHasTasks) {
+					await generateTaskFiles(
+						taskMaster.getTasksPath(),
+						path.dirname(taskMaster.getTasksPath()),
+						{ tag: sourceTag, projectRoot: taskMaster.getProjectRoot() }
+					);
+				}
+			}
+
+			// Helper function to handle within-tag move logic
+			async function handleWithinTagMove(moveContext) {
+				const { sourceId, destinationId, tag, taskMaster } = moveContext;
+
+				if (!sourceId || !destinationId) {
+					console.error(
+						chalk.red(
+							'Error: Both --from and --to parameters are required for within-tag moves'
+						)
+					);
+					console.log(
+						chalk.yellow(
+							'Usage: task-master move --from=<sourceId> --to=<destinationId>'
+						)
+					);
+					process.exit(1);
+				}
+
+				// Check if we're moving multiple tasks (comma-separated IDs)
+				const sourceIds = sourceId.split(',').map((id) => id.trim());
+				const destinationIds = destinationId.split(',').map((id) => id.trim());
+
+				// Validate that the number of source and destination IDs match
+				if (sourceIds.length !== destinationIds.length) {
+					console.error(
+						chalk.red(
+							'Error: The number of source and destination IDs must match'
+						)
+					);
+					console.log(
+						chalk.yellow('Example: task-master move --from=5,6,7 --to=10,11,12')
+					);
+					process.exit(1);
+				}
+
+				// If moving multiple tasks
+				if (sourceIds.length > 1) {
+					console.log(
+						chalk.blue(
+							`Moving multiple tasks: ${sourceIds.join(', ')} to ${destinationIds.join(', ')}...`
+						)
+					);
+
 					// Read tasks data once to validate destination IDs
 					const tasksData = readJSON(
 						taskMaster.getTasksPath(),
@@ -4104,11 +4263,17 @@ Examples:
 					);
 					if (!tasksData || !tasksData.tasks) {
 						console.error(
-							chalk.red(`Error: Invalid or missing tasks file at ${tasksPath}`)
+							chalk.red(
+								`Error: Invalid or missing tasks file at ${taskMaster.getTasksPath()}`
+							)
 						);
 						process.exit(1);
 					}
 
+					// Collect errors during move attempts
+					const moveErrors = [];
+					const successfulMoves = [];
+
 					// Move tasks one by one
 					for (let i = 0; i < sourceIds.length; i++) {
 						const fromId = sourceIds[i];
@@ -4138,24 +4303,59 @@ Examples:
 									`✓ Successfully moved task/subtask ${fromId} to ${toId}`
 								)
 							);
+							successfulMoves.push({ fromId, toId });
 						} catch (error) {
+							const errorInfo = {
+								fromId,
+								toId,
+								error: error.message
+							};
+							moveErrors.push(errorInfo);
 							console.error(
 								chalk.red(`Error moving ${fromId} to ${toId}: ${error.message}`)
 							);
 							// Continue with the next task rather than exiting
 						}
 					}
-				} catch (error) {
-					console.error(chalk.red(`Error: ${error.message}`));
-					process.exit(1);
-				}
-			} else {
-				// Moving a single task (existing logic)
-				console.log(
-					chalk.blue(`Moving task/subtask ${sourceId} to ${destinationId}...`)
-				);
 
-				try {
+					// Display summary after all moves are attempted
+					if (moveErrors.length > 0) {
+						console.log(chalk.yellow('\n--- Move Operation Summary ---'));
+						console.log(
+							chalk.green(
+								`✓ Successfully moved: ${successfulMoves.length} tasks`
+							)
+						);
+						console.log(
+							chalk.red(`✗ Failed to move: ${moveErrors.length} tasks`)
+						);
+
+						if (successfulMoves.length > 0) {
+							console.log(chalk.cyan('\nSuccessful moves:'));
+							successfulMoves.forEach(({ fromId, toId }) => {
+								console.log(chalk.cyan(`  ${fromId} → ${toId}`));
+							});
+						}
+
+						console.log(chalk.red('\nFailed moves:'));
+						moveErrors.forEach(({ fromId, toId, error }) => {
+							console.log(chalk.red(`  ${fromId} → ${toId}: ${error}`));
+						});
+
+						console.log(
+							chalk.yellow(
+								'\nNote: Some tasks were moved successfully. Check the errors above for failed moves.'
+							)
+						);
+					} else {
+						console.log(chalk.green('\n✓ All tasks moved successfully!'));
+					}
+				} else {
+					// Moving a single task (existing logic)
+					console.log(
+						chalk.blue(`Moving task/subtask ${sourceId} to ${destinationId}...`)
+					);
+
 					const result = await moveTask(
 						taskMaster.getTasksPath(),
 						sourceId,
@@ -4168,11 +4368,90 @@ Examples:
 							`✓ Successfully moved task/subtask ${sourceId} to ${destinationId}`
 						)
 					);
-				} catch (error) {
-					console.error(chalk.red(`Error: ${error.message}`));
-					process.exit(1);
 				}
 			}
+
+			// Helper function to handle move errors
+			function handleMoveError(error, moveContext) {
+				console.error(chalk.red(`Error: ${error.message}`));
+
+				// Enhanced error handling with structured error objects
+				if (error.code === 'CROSS_TAG_DEPENDENCY_CONFLICTS') {
+					// Use structured error data
+					const conflicts = error.data.conflicts || [];
+					const taskIds = error.data.taskIds || [];
+					displayCrossTagDependencyError(
+						conflicts,
+						moveContext.sourceTag,
+						moveContext.toTag,
+						taskIds.join(', ')
+					);
+				} else if (error.code === 'CANNOT_MOVE_SUBTASK') {
+					// Use structured error data
+					const taskId =
+						error.data.taskId || moveContext.sourceId?.split(',')[0];
+					displaySubtaskMoveError(
+						taskId,
+						moveContext.sourceTag,
+						moveContext.toTag
+					);
+				} else if (
+					error.code === 'SOURCE_TARGET_TAGS_SAME' ||
+					error.code === 'SAME_SOURCE_TARGET_TAG'
+				) {
+					displayInvalidTagCombinationError(
+						moveContext.sourceTag,
+						moveContext.toTag,
+						'Source and target tags are identical'
+					);
+				} else {
+					// General error - show dependency validation hints
+					displayDependencyValidationHints('after-error');
+				}
+
+				process.exit(1);
+			}
+
+			// Initialize TaskMaster
+			const taskMaster = initTaskMaster({
+				tasksPath: options.file || true,
+				tag: options.tag
+			});
+
+			const sourceId = options.from;
+			const destinationId = options.to;
+			const fromTag = options.fromTag;
+			const toTag = options.toTag;
+
+			const tag = taskMaster.getCurrentTag();
+
+			// Get the source tag - fallback to current tag if not provided
+			const sourceTag = fromTag || taskMaster.getCurrentTag();
+
+			// Check if this is a cross-tag move (different tags)
+			const isCrossTagMove = sourceTag && toTag && sourceTag !== toTag;
+
+			// Initialize move context with all relevant data
+			const moveContext = {
+				sourceId,
+				destinationId,
+				sourceTag,
+				toTag,
+				tag,
+				taskMaster
+			};
+
+			try {
+				if (isCrossTagMove) {
+					// Cross-tag move logic
+					await handleCrossTagMove(moveContext, options);
+				} else {
+					// Within-tag move logic
+					await handleWithinTagMove(moveContext);
+				}
+			} catch (error) {
+				handleMoveError(error, moveContext);
+			}
 		});
 
 	// Add/remove profile rules command
@@ -4592,7 +4871,7 @@ Examples:
 					const gitUtils = await import('./utils/git-utils.js');
 
 					// Check if we're in a git repository
-					if (!(await gitUtils.isGitRepository(projectRoot))) {
+					if (!(await gitUtils.isGitRepository(context.projectRoot))) {
 						console.error(
 							chalk.red(
 								'Error: Not in a git repository. Cannot use --from-branch option.'
@@ -4602,7 +4881,9 @@ Examples:
 					}
 
 					// Get current git branch
-					const currentBranch = await gitUtils.getCurrentBranch(projectRoot);
+					const currentBranch = await gitUtils.getCurrentBranch(
+						context.projectRoot
+					);
 					if (!currentBranch) {
 						console.error(
 							chalk.red('Error: Could not determine current git branch.')

scripts/modules/config-manager.js

@@ -557,6 +557,7 @@ function getParametersForRole(role, explicitRoot = null) {
 	const providerName = roleConfig.provider;
 
 	let effectiveMaxTokens = roleMaxTokens; // Start with the role's default
+	let effectiveTemperature = roleTemperature; // Start with the role's default
 
 	try {
 		// Find the model definition in MODEL_MAP
@@ -583,6 +584,20 @@ function getParametersForRole(role, explicitRoot = null) {
 					`No valid model-specific max_tokens override found for ${modelId}. Using role default: ${roleMaxTokens}`
 				);
 			}
+
+			// Check if a model-specific temperature is defined
+			if (
+				modelDefinition &&
+				typeof modelDefinition.temperature === 'number' &&
+				modelDefinition.temperature >= 0 &&
+				modelDefinition.temperature <= 1
+			) {
+				effectiveTemperature = modelDefinition.temperature;
+				log(
+					'debug',
+					`Applying model-specific temperature (${modelDefinition.temperature}) for ${modelId}`
+				);
+			}
 		} else {
 			// Special handling for custom OpenRouter models
 			if (providerName === CUSTOM_PROVIDERS.OPENROUTER) {
@@ -603,15 +618,16 @@ function getParametersForRole(role, explicitRoot = null) {
 	} catch (lookupError) {
 		log(
 			'warn',
-			`Error looking up model-specific max_tokens for ${modelId}: ${lookupError.message}. Using role default: ${roleMaxTokens}`
+			`Error looking up model-specific parameters for ${modelId}: ${lookupError.message}. Using role defaults.`
 		);
-		// Fallback to role default on error
+		// Fallback to role defaults on error
 		effectiveMaxTokens = roleMaxTokens;
+		effectiveTemperature = roleTemperature;
 	}
 
 	return {
 		maxTokens: effectiveMaxTokens,
-		temperature: roleTemperature
+		temperature: effectiveTemperature
 	};
 }
 

scripts/modules/dependency-manager.js

@@ -14,12 +14,35 @@ import {
 	taskExists,
 	formatTaskId,
 	findCycles,
+	traverseDependencies,
 	isSilentMode
 } from './utils.js';
 
 import { displayBanner } from './ui.js';
 
-import { generateTaskFiles } from './task-manager.js';
+import generateTaskFiles from './task-manager/generate-task-files.js';
+
+/**
+ * Structured error class for dependency operations
+ */
+class DependencyError extends Error {
+	constructor(code, message, data = {}) {
+		super(message);
+		this.name = 'DependencyError';
+		this.code = code;
+		this.data = data;
+	}
+}
+
+/**
+ * Error codes for dependency operations
+ */
+const DEPENDENCY_ERROR_CODES = {
+	CANNOT_MOVE_SUBTASK: 'CANNOT_MOVE_SUBTASK',
+	INVALID_TASK_ID: 'INVALID_TASK_ID',
+	INVALID_SOURCE_TAG: 'INVALID_SOURCE_TAG',
+	INVALID_TARGET_TAG: 'INVALID_TARGET_TAG'
+};
 
 /**
  * Add a dependency to a task
@@ -1235,6 +1258,580 @@ function validateAndFixDependencies(
 	return changesDetected;
 }
 
+/**
+ * Recursively find all dependencies for a set of tasks with depth limiting
+ * Recursively find all dependencies for a set of tasks with depth limiting
+ *
+ * @note This function depends on the traverseDependencies utility from utils.js
+ * for the actual dependency traversal logic.
+ *
+ * @param {Array} sourceTasks - Array of source tasks to find dependencies for
+ * @param {Array} allTasks - Array of all available tasks
+ * @param {Object} options - Options object
+ * @param {number} options.maxDepth - Maximum recursion depth (default: 50)
+ * @param {boolean} options.includeSelf - Whether to include self-references (default: false)
+ * @returns {Array} Array of all dependency task IDs
+ */
+function findAllDependenciesRecursively(sourceTasks, allTasks, options = {}) {
+	if (!Array.isArray(sourceTasks)) {
+		throw new Error('Source tasks parameter must be an array');
+	}
+	if (!Array.isArray(allTasks)) {
+		throw new Error('All tasks parameter must be an array');
+	}
+	return traverseDependencies(sourceTasks, allTasks, {
+		...options,
+		direction: 'forward',
+		logger: { warn: log.warn || console.warn }
+	});
+}
+
+/**
+ * Find dependency task by ID, handling various ID formats
+ * @param {string|number} depId - Dependency ID to find
+ * @param {string} taskId - ID of the task that has this dependency
+ * @param {Array} allTasks - Array of all tasks to search
+ * @returns {Object|null} Found dependency task or null
+ */
+/**
+ * Find a subtask within a parent task's subtasks array
+ * @param {string} parentId - The parent task ID
+ * @param {string|number} subtaskId - The subtask ID to find
+ * @param {Array} allTasks - Array of all tasks to search in
+ * @param {boolean} useStringComparison - Whether to use string comparison for subtaskId
+ * @returns {Object|null} The found subtask with full ID or null if not found
+ */
+function findSubtaskInParent(
+	parentId,
+	subtaskId,
+	allTasks,
+	useStringComparison = false
+) {
+	// Convert parentId to numeric for proper comparison with top-level task IDs
+	const numericParentId = parseInt(parentId, 10);
+	const parentTask = allTasks.find((t) => t.id === numericParentId);
+
+	if (parentTask && parentTask.subtasks && Array.isArray(parentTask.subtasks)) {
+		const foundSubtask = parentTask.subtasks.find((subtask) =>
+			useStringComparison
+				? String(subtask.id) === String(subtaskId)
+				: subtask.id === subtaskId
+		);
+		if (foundSubtask) {
+			// Return a task-like object that represents the subtask with full ID
+			return {
+				...foundSubtask,
+				id: `${parentId}.${foundSubtask.id}`
+			};
+		}
+	}
+
+	return null;
+}
+
+function findDependencyTask(depId, taskId, allTasks) {
+	if (!depId) {
+		return null;
+	}
+
+	// Convert depId to string for consistent comparison
+	const depIdStr = String(depId);
+
+	// Find the dependency task - handle both top-level and subtask IDs
+	let depTask = null;
+
+	// First try exact match (for top-level tasks)
+	depTask = allTasks.find((t) => String(t.id) === depIdStr);
+
+	// If not found and it's a subtask reference (contains dot), find the parent task first
+	if (!depTask && depIdStr.includes('.')) {
+		const [parentId, subtaskId] = depIdStr.split('.');
+		depTask = findSubtaskInParent(parentId, subtaskId, allTasks, true);
+	}
+
+	// If still not found, try numeric comparison for relative subtask references
+	if (!depTask && !isNaN(depId)) {
+		const numericId = parseInt(depId, 10);
+		// For subtasks, this might be a relative reference within the same parent
+		if (taskId && typeof taskId === 'string' && taskId.includes('.')) {
+			const [parentId] = taskId.split('.');
+			depTask = findSubtaskInParent(parentId, numericId, allTasks, false);
+		}
+	}
+
+	return depTask;
+}
+
+/**
+ * Check if a task has cross-tag dependencies
+ * @param {Object} task - Task to check
+ * @param {string} targetTag - Target tag name
+ * @param {Array} allTasks - Array of all tasks from all tags
+ * @returns {Array} Array of cross-tag dependency conflicts
+ */
+function findTaskCrossTagConflicts(task, targetTag, allTasks) {
+	const conflicts = [];
+
+	// Validate task.dependencies is an array before processing
+	if (!Array.isArray(task.dependencies) || task.dependencies.length === 0) {
+		return conflicts;
+	}
+
+	// Filter out null/undefined dependencies and check each valid dependency
+	const validDependencies = task.dependencies.filter((depId) => depId != null);
+
+	validDependencies.forEach((depId) => {
+		const depTask = findDependencyTask(depId, task.id, allTasks);
+
+		if (depTask && depTask.tag !== targetTag) {
+			conflicts.push({
+				taskId: task.id,
+				dependencyId: depId,
+				dependencyTag: depTask.tag,
+				message: `Task ${task.id} depends on ${depId} (in ${depTask.tag})`
+			});
+		}
+	});
+
+	return conflicts;
+}
+
+function validateCrossTagMove(task, sourceTag, targetTag, allTasks) {
+	// Parameter validation
+	if (!task || typeof task !== 'object') {
+		throw new Error('Task parameter must be a valid object');
+	}
+
+	if (!sourceTag || typeof sourceTag !== 'string') {
+		throw new Error('Source tag must be a valid string');
+	}
+
+	if (!targetTag || typeof targetTag !== 'string') {
+		throw new Error('Target tag must be a valid string');
+	}
+
+	if (!Array.isArray(allTasks)) {
+		throw new Error('All tasks parameter must be an array');
+	}
+
+	const conflicts = findTaskCrossTagConflicts(task, targetTag, allTasks);
+
+	return {
+		canMove: conflicts.length === 0,
+		conflicts
+	};
+}
+
+/**
+ * Find all cross-tag dependencies for a set of tasks
+ * @param {Array} sourceTasks - Array of tasks to check
+ * @param {string} sourceTag - Source tag name
+ * @param {string} targetTag - Target tag name
+ * @param {Array} allTasks - Array of all tasks from all tags
+ * @returns {Array} Array of cross-tag dependency conflicts
+ */
+function findCrossTagDependencies(sourceTasks, sourceTag, targetTag, allTasks) {
+	// Parameter validation
+	if (!Array.isArray(sourceTasks)) {
+		throw new Error('Source tasks parameter must be an array');
+	}
+
+	if (!sourceTag || typeof sourceTag !== 'string') {
+		throw new Error('Source tag must be a valid string');
+	}
+
+	if (!targetTag || typeof targetTag !== 'string') {
+		throw new Error('Target tag must be a valid string');
+	}
+
+	if (!Array.isArray(allTasks)) {
+		throw new Error('All tasks parameter must be an array');
+	}
+
+	const conflicts = [];
+
+	sourceTasks.forEach((task) => {
+		// Validate task object and dependencies array
+		if (
+			!task ||
+			typeof task !== 'object' ||
+			!Array.isArray(task.dependencies) ||
+			task.dependencies.length === 0
+		) {
+			return;
+		}
+
+		// Use the shared helper function to find conflicts for this task
+		const taskConflicts = findTaskCrossTagConflicts(task, targetTag, allTasks);
+		conflicts.push(...taskConflicts);
+	});
+
+	return conflicts;
+}
+
+/**
+ * Helper function to find all tasks that depend on a given task (reverse dependencies)
+ * @param {string|number} taskId - The task ID to find dependencies for
+ * @param {Array} allTasks - Array of all tasks to search
+ * @param {Set} dependentTaskIds - Set to add found dependencies to
+ */
+function findTasksThatDependOn(taskId, allTasks, dependentTaskIds) {
+	// Find the task object for the given ID
+	const sourceTask = allTasks.find((t) => t.id === taskId);
+	if (!sourceTask) {
+		return;
+	}
+
+	// Use the shared utility for reverse dependency traversal
+	const reverseDeps = traverseDependencies([sourceTask], allTasks, {
+		direction: 'reverse',
+		includeSelf: false,
+		logger: { warn: log.warn || console.warn }
+	});
+
+	// Add all found reverse dependencies to the dependentTaskIds set
+	reverseDeps.forEach((depId) => dependentTaskIds.add(depId));
+}
+
+/**
+ * Helper function to check if a task depends on a source task
+ * @param {Object} task - Task to check for dependencies
+ * @param {Object} sourceTask - Source task to check dependency against
+ * @returns {boolean} True if task depends on source task
+ */
+function taskDependsOnSource(task, sourceTask) {
+	if (!task || !Array.isArray(task.dependencies)) {
+		return false;
+	}
+
+	const sourceTaskIdStr = String(sourceTask.id);
+
+	return task.dependencies.some((depId) => {
+		if (!depId) return false;
+
+		const depIdStr = String(depId);
+
+		// Exact match
+		if (depIdStr === sourceTaskIdStr) {
+			return true;
+		}
+
+		// Handle subtask references
+		if (
+			sourceTaskIdStr &&
+			typeof sourceTaskIdStr === 'string' &&
+			sourceTaskIdStr.includes('.')
+		) {
+			// If source is a subtask, check if dependency references the parent
+			const [parentId] = sourceTaskIdStr.split('.');
+			if (depIdStr === parentId) {
+				return true;
+			}
+		}
+
+		// Handle relative subtask references
+		if (
+			depIdStr &&
+			typeof depIdStr === 'string' &&
+			depIdStr.includes('.') &&
+			sourceTaskIdStr &&
+			typeof sourceTaskIdStr === 'string' &&
+			sourceTaskIdStr.includes('.')
+		) {
+			const [depParentId] = depIdStr.split('.');
+			const [sourceParentId] = sourceTaskIdStr.split('.');
+			if (depParentId === sourceParentId) {
+				// Both are subtasks of the same parent, check if they reference each other
+				const depSubtaskNum = parseInt(depIdStr.split('.')[1], 10);
+				const sourceSubtaskNum = parseInt(sourceTaskIdStr.split('.')[1], 10);
+				if (depSubtaskNum === sourceSubtaskNum) {
+					return true;
+				}
+			}
+		}
+
+		return false;
+	});
+}
+
+/**
+ * Helper function to check if any subtasks of a task depend on source tasks
+ * @param {Object} task - Task to check subtasks of
+ * @param {Array} sourceTasks - Array of source tasks to check dependencies against
+ * @returns {boolean} True if any subtasks depend on source tasks
+ */
+function subtasksDependOnSource(task, sourceTasks) {
+	if (!task.subtasks || !Array.isArray(task.subtasks)) {
+		return false;
+	}
+
+	return task.subtasks.some((subtask) => {
+		// Check if this subtask depends on any source task
+		const subtaskDependsOnSource = sourceTasks.some((sourceTask) =>
+			taskDependsOnSource(subtask, sourceTask)
+		);
+
+		if (subtaskDependsOnSource) {
+			return true;
+		}
+
+		// Recursively check if any nested subtasks depend on source tasks
+		if (subtask.subtasks && Array.isArray(subtask.subtasks)) {
+			return subtasksDependOnSource(subtask, sourceTasks);
+		}
+
+		return false;
+	});
+}
+
+/**
+ * Get all dependent task IDs for a set of cross-tag dependencies
+ * @param {Array} sourceTasks - Array of source tasks
+ * @param {Array} crossTagDependencies - Array of cross-tag dependency conflicts
+ * @param {Array} allTasks - Array of all tasks from all tags
+ * @returns {Array} Array of dependent task IDs to move
+ */
+function getDependentTaskIds(sourceTasks, crossTagDependencies, allTasks) {
+	// Enhanced parameter validation
+	if (!Array.isArray(sourceTasks)) {
+		throw new Error('Source tasks parameter must be an array');
+	}
+
+	if (!Array.isArray(crossTagDependencies)) {
+		throw new Error('Cross tag dependencies parameter must be an array');
+	}
+
+	if (!Array.isArray(allTasks)) {
+		throw new Error('All tasks parameter must be an array');
+	}
+
+	// Use the shared recursive dependency finder
+	const dependentTaskIds = new Set(
+		findAllDependenciesRecursively(sourceTasks, allTasks, {
+			includeSelf: false
+		})
+	);
+
+	// Add immediate dependency IDs from conflicts and find their dependencies recursively
+	const conflictTasksToProcess = [];
+	crossTagDependencies.forEach((conflict) => {
+		if (conflict && conflict.dependencyId) {
+			const depId =
+				typeof conflict.dependencyId === 'string'
+					? parseInt(conflict.dependencyId, 10)
+					: conflict.dependencyId;
+			if (!isNaN(depId)) {
+				dependentTaskIds.add(depId);
+				// Find the task object for recursive dependency finding
+				const depTask = allTasks.find((t) => t.id === depId);
+				if (depTask) {
+					conflictTasksToProcess.push(depTask);
+				}
+			}
+		}
+	});
+
+	// Find dependencies of conflict tasks
+	if (conflictTasksToProcess.length > 0) {
+		const conflictDependencies = findAllDependenciesRecursively(
+			conflictTasksToProcess,
+			allTasks,
+			{ includeSelf: false }
+		);
+		conflictDependencies.forEach((depId) => dependentTaskIds.add(depId));
+	}
+
+	// For --with-dependencies, we also need to find all dependencies of the source tasks
+	sourceTasks.forEach((sourceTask) => {
+		if (sourceTask && sourceTask.id) {
+			// Find all tasks that this source task depends on (forward dependencies) - already handled above
+
+			// Find all tasks that depend on this source task (reverse dependencies)
+			findTasksThatDependOn(sourceTask.id, allTasks, dependentTaskIds);
+		}
+	});
+
+	// Also include any tasks that depend on the source tasks
+	sourceTasks.forEach((sourceTask) => {
+		if (!sourceTask || typeof sourceTask !== 'object' || !sourceTask.id) {
+			return; // Skip invalid source tasks
+		}
+
+		allTasks.forEach((task) => {
+			// Validate task and dependencies array
+			if (
+				!task ||
+				typeof task !== 'object' ||
+				!Array.isArray(task.dependencies)
+			) {
+				return;
+			}
+
+			// Check if this task depends on the source task
+			const hasDependency = taskDependsOnSource(task, sourceTask);
+
+			// Check if any subtasks of this task depend on the source task
+			const subtasksHaveDependency = subtasksDependOnSource(task, [sourceTask]);
+
+			if (hasDependency || subtasksHaveDependency) {
+				dependentTaskIds.add(task.id);
+			}
+		});
+	});
+
+	return Array.from(dependentTaskIds);
+}
+
+/**
+ * Validate subtask movement - block direct cross-tag subtask moves
+ * @param {string} taskId - Task ID to validate
+ * @param {string} sourceTag - Source tag name
+ * @param {string} targetTag - Target tag name
+ * @throws {Error} If subtask movement is attempted
+ */
+function validateSubtaskMove(taskId, sourceTag, targetTag) {
+	// Parameter validation
+	if (!taskId || typeof taskId !== 'string') {
+		throw new DependencyError(
+			DEPENDENCY_ERROR_CODES.INVALID_TASK_ID,
+			'Task ID must be a valid string'
+		);
+	}
+
+	if (!sourceTag || typeof sourceTag !== 'string') {
+		throw new DependencyError(
+			DEPENDENCY_ERROR_CODES.INVALID_SOURCE_TAG,
+			'Source tag must be a valid string'
+		);
+	}
+
+	if (!targetTag || typeof targetTag !== 'string') {
+		throw new DependencyError(
+			DEPENDENCY_ERROR_CODES.INVALID_TARGET_TAG,
+			'Target tag must be a valid string'
+		);
+	}
+
+	if (taskId.includes('.')) {
+		throw new DependencyError(
+			DEPENDENCY_ERROR_CODES.CANNOT_MOVE_SUBTASK,
+			`Cannot move subtask ${taskId} directly between tags.
+
+First promote it to a full task using:
+  task-master remove-subtask --id=${taskId} --convert`,
+			{
+				taskId,
+				sourceTag,
+				targetTag
+			}
+		);
+	}
+}
+
+/**
+ * Check if a task can be moved with its dependencies
+ * @param {string} taskId - Task ID to check
+ * @param {string} sourceTag - Source tag name
+ * @param {string} targetTag - Target tag name
+ * @param {Array} allTasks - Array of all tasks from all tags
+ * @returns {Object} Object with canMove boolean and dependentTaskIds array
+ */
+function canMoveWithDependencies(taskId, sourceTag, targetTag, allTasks) {
+	// Parameter validation
+	if (!taskId || typeof taskId !== 'string') {
+		throw new Error('Task ID must be a valid string');
+	}
+
+	if (!sourceTag || typeof sourceTag !== 'string') {
+		throw new Error('Source tag must be a valid string');
+	}
+
+	if (!targetTag || typeof targetTag !== 'string') {
+		throw new Error('Target tag must be a valid string');
+	}
+
+	if (!Array.isArray(allTasks)) {
+		throw new Error('All tasks parameter must be an array');
+	}
+
+	// Enhanced task lookup to handle subtasks properly
+	let sourceTask = null;
+
+	// Check if it's a subtask ID (e.g., "1.2")
+	if (taskId.includes('.')) {
+		const [parentId, subtaskId] = taskId
+			.split('.')
+			.map((id) => parseInt(id, 10));
+		const parentTask = allTasks.find(
+			(t) => t.id === parentId && t.tag === sourceTag
+		);
+
+		if (
+			parentTask &&
+			parentTask.subtasks &&
+			Array.isArray(parentTask.subtasks)
+		) {
+			const subtask = parentTask.subtasks.find((st) => st.id === subtaskId);
+			if (subtask) {
+				// Create a copy of the subtask with parent context
+				sourceTask = {
+					...subtask,
+					parentTask: {
+						id: parentTask.id,
+						title: parentTask.title,
+						status: parentTask.status
+					},
+					isSubtask: true
+				};
+			}
+		}
+	} else {
+		// Regular task lookup - handle both string and numeric IDs
+		sourceTask = allTasks.find((t) => {
+			const taskIdNum = parseInt(taskId, 10);
+			return (t.id === taskIdNum || t.id === taskId) && t.tag === sourceTag;
+		});
+	}
+
+	if (!sourceTask) {
+		return {
+			canMove: false,
+			dependentTaskIds: [],
+			conflicts: [],
+			error: 'Task not found'
+		};
+	}
+
+	const validation = validateCrossTagMove(
+		sourceTask,
+		sourceTag,
+		targetTag,
+		allTasks
+	);
+
+	// Fix contradictory logic: return canMove: false when conflicts exist
+	if (validation.canMove) {
+		return {
+			canMove: true,
+			dependentTaskIds: [],
+			conflicts: []
+		};
+	}
+
+	// When conflicts exist, return canMove: false with conflicts and dependent task IDs
+	const dependentTaskIds = getDependentTaskIds(
+		[sourceTask],
+		validation.conflicts,
+		allTasks
+	);
+
+	return {
+		canMove: false,
+		dependentTaskIds,
+		conflicts: validation.conflicts
+	};
+}
+
 export {
 	addDependency,
 	removeDependency,
@@ -1245,5 +1842,15 @@ export {
 	removeDuplicateDependencies,
 	cleanupSubtaskDependencies,
 	ensureAtLeastOneIndependentSubtask,
-	validateAndFixDependencies
+	validateAndFixDependencies,
+	findDependencyTask,
+	findTaskCrossTagConflicts,
+	validateCrossTagMove,
+	findCrossTagDependencies,
+	getDependentTaskIds,
+	validateSubtaskMove,
+	canMoveWithDependencies,
+	findAllDependenciesRecursively,
+	DependencyError,
+	DEPENDENCY_ERROR_CODES
 };

scripts/modules/prompt-manager.js

@@ -36,7 +36,7 @@ export class PromptManager {
 			const schema = JSON.parse(schemaContent);
 
 			this.validatePrompt = this.ajv.compile(schema);
-			log('info', '✓ JSON schema validation enabled');
+			log('debug', '✓ JSON schema validation enabled');
 		} catch (error) {
 			log('warn', `⚠ Schema validation disabled: ${error.message}`);
 			this.validatePrompt = () => true; // Fallback to no validation

scripts/modules/supported-models.json

@@ -239,6 +239,18 @@
 			},
 			"allowed_roles": ["research"],
 			"supported": true
+		},
+		{
+			"id": "gpt-5",
+			"swe_score": 0.749,
+			"cost_per_1m_tokens": {
+				"input": 5.0,
+				"output": 20.0
+			},
+			"allowed_roles": ["main", "fallback"],
+			"max_tokens": 100000,
+			"temperature": 1,
+			"supported": true
 		}
 	],
 	"google": [
@@ -774,6 +786,39 @@
 		}
 	],
 	"ollama": [
+		{
+			"id": "gpt-oss:latest",
+			"swe_score": 0.607,
+			"cost_per_1m_tokens": {
+				"input": 0,
+				"output": 0
+			},
+			"allowed_roles": ["main", "fallback"],
+			"max_tokens": 128000,
+			"supported": true
+		},
+		{
+			"id": "gpt-oss:20b",
+			"swe_score": 0.607,
+			"cost_per_1m_tokens": {
+				"input": 0,
+				"output": 0
+			},
+			"allowed_roles": ["main", "fallback"],
+			"max_tokens": 128000,
+			"supported": true
+		},
+		{
+			"id": "gpt-oss:120b",
+			"swe_score": 0.624,
+			"cost_per_1m_tokens": {
+				"input": 0,
+				"output": 0
+			},
+			"allowed_roles": ["main", "fallback"],
+			"max_tokens": 128000,
+			"supported": true
+		},
 		{
 			"id": "devstral:latest",
 			"swe_score": 0,

scripts/modules/task-manager.js

@@ -4,7 +4,7 @@
  */
 
 import { findTaskById } from './utils.js';
-import parsePRD from './task-manager/parse-prd.js';
+import parsePRD from './task-manager/parse-prd/index.js';
 import updateTasks from './task-manager/update-tasks.js';
 import updateTaskById from './task-manager/update-task-by-id.js';
 import generateTaskFiles from './task-manager/generate-task-files.js';

scripts/modules/task-manager/analyze-task-complexity.js

@@ -13,12 +13,18 @@ import {
 
 import { generateTextService } from '../ai-services-unified.js';
 
-import { getDebugFlag, getProjectName } from '../config-manager.js';
+import {
+	getDebugFlag,
+	getProjectName,
+	getMainProvider,
+	getResearchProvider
+} from '../config-manager.js';
 import { getPromptManager } from '../prompt-manager.js';
 import {
 	COMPLEXITY_REPORT_FILE,
 	LEGACY_TASKS_FILE
 } from '../../../src/constants/paths.js';
+import { CUSTOM_PROVIDERS } from '../../../src/constants/providers.js';
 import { resolveComplexityReportOutputPath } from '../../../src/utils/path-utils.js';
 import { ContextGatherer } from '../utils/contextGatherer.js';
 import { FuzzyTaskSearch } from '../utils/fuzzyTaskSearch.js';
@@ -408,10 +414,18 @@ async function analyzeTaskComplexity(options, context = {}) {
 		// Load prompts using PromptManager
 		const promptManager = getPromptManager();
 
+		// Check if Claude Code is being used as the provider
+		const currentProvider = useResearch
+			? getResearchProvider(projectRoot)
+			: getMainProvider(projectRoot);
+		const isClaudeCode = currentProvider === CUSTOM_PROVIDERS.CLAUDE_CODE;
+
 		const promptParams = {
 			tasks: tasksData.tasks,
 			gatheredContext: gatheredContext || '',
-			useResearch: useResearch
+			useResearch: useResearch,
+			isClaudeCode: isClaudeCode,
+			projectRoot: projectRoot || ''
 		};
 
 		const { systemPrompt, userPrompt: prompt } = await promptManager.loadPrompt(

scripts/modules/task-manager/expand-task.js

@@ -18,10 +18,16 @@ import {
 
 import { generateTextService } from '../ai-services-unified.js';
 
-import { getDefaultSubtasks, getDebugFlag } from '../config-manager.js';
+import {
+	getDefaultSubtasks,
+	getDebugFlag,
+	getMainProvider,
+	getResearchProvider
+} from '../config-manager.js';
 import { getPromptManager } from '../prompt-manager.js';
 import generateTaskFiles from './generate-task-files.js';
 import { COMPLEXITY_REPORT_FILE } from '../../../src/constants/paths.js';
+import { CUSTOM_PROVIDERS } from '../../../src/constants/providers.js';
 import { ContextGatherer } from '../utils/contextGatherer.js';
 import { FuzzyTaskSearch } from '../utils/fuzzyTaskSearch.js';
 import { flattenTasksWithSubtasks, findProjectRoot } from '../utils.js';
@@ -451,6 +457,12 @@ async function expandTask(
 		// Load prompts using PromptManager
 		const promptManager = getPromptManager();
 
+		// Check if Claude Code is being used as the provider
+		const currentProvider = useResearch
+			? getResearchProvider(projectRoot)
+			: getMainProvider(projectRoot);
+		const isClaudeCode = currentProvider === CUSTOM_PROVIDERS.CLAUDE_CODE;
+
 		// Combine all context sources into a single additionalContext parameter
 		let combinedAdditionalContext = '';
 		if (additionalContext || complexityReasoningContext) {
@@ -495,7 +507,9 @@ async function expandTask(
 			complexityReasoningContext: complexityReasoningContext,
 			gatheredContext: gatheredContextText || '',
 			useResearch: useResearch,
-			expansionPrompt: expansionPromptText || undefined
+			expansionPrompt: expansionPromptText || undefined,
+			isClaudeCode: isClaudeCode,
+			projectRoot: projectRoot || ''
 		};
 
 		let variantKey = 'default';
@@ -513,6 +527,18 @@ async function expandTask(
 
 		const { systemPrompt, userPrompt: promptContent } =
 			await promptManager.loadPrompt('expand-task', promptParams, variantKey);
+
+		// Debug logging to identify the issue
+		logger.debug(`Selected variant: ${variantKey}`);
+		logger.debug(
+			`Prompt params passed: ${JSON.stringify(promptParams, null, 2)}`
+		);
+		logger.debug(
+			`System prompt (first 500 chars): ${systemPrompt.substring(0, 500)}...`
+		);
+		logger.debug(
+			`User prompt (first 500 chars): ${promptContent.substring(0, 500)}...`
+		);
 		// --- End Complexity Report / Prompt Logic ---
 
 		// --- AI Subtask Generation using generateTextService ---

scripts/modules/task-manager/list-tasks.js

@@ -294,6 +294,11 @@ function listTasks(
 			});
 		}
 
+		// For compact output, return minimal one-line format
+		if (outputFormat === 'compact') {
+			return renderCompactOutput(filteredTasks, withSubtasks);
+		}
+
 		// ... existing code for text output ...
 
 		// Calculate status breakdowns as percentages of total
@@ -962,4 +967,98 @@ function generateMarkdownOutput(data, filteredTasks, stats) {
 	return markdown;
 }
 
+/**
+ * Format dependencies for compact output with truncation and coloring
+ * @param {Array} dependencies - Array of dependency IDs
+ * @returns {string} - Formatted dependency string with arrow prefix
+ */
+function formatCompactDependencies(dependencies) {
+	if (!dependencies || dependencies.length === 0) {
+		return '';
+	}
+
+	if (dependencies.length > 5) {
+		const visible = dependencies.slice(0, 5).join(',');
+		const remaining = dependencies.length - 5;
+		return ` → ${chalk.cyan(visible)}${chalk.gray('... (+' + remaining + ' more)')}`;
+	} else {
+		return ` → ${chalk.cyan(dependencies.join(','))}`;
+	}
+}
+
+/**
+ * Format a single task in compact one-line format
+ * @param {Object} task - Task object
+ * @param {number} maxTitleLength - Maximum title length before truncation
+ * @returns {string} - Formatted task line
+ */
+function formatCompactTask(task, maxTitleLength = 50) {
+	const status = task.status || 'pending';
+	const priority = task.priority || 'medium';
+	const title = truncate(task.title || 'Untitled', maxTitleLength);
+
+	// Use colored status from existing function
+	const coloredStatus = getStatusWithColor(status, true);
+
+	// Color priority based on level
+	const priorityColors = {
+		high: chalk.red,
+		medium: chalk.yellow,
+		low: chalk.gray
+	};
+	const priorityColor = priorityColors[priority] || chalk.white;
+
+	// Format dependencies using shared helper
+	const depsText = formatCompactDependencies(task.dependencies);
+
+	return `${chalk.cyan(task.id)} ${coloredStatus} ${chalk.white(title)} ${priorityColor('(' + priority + ')')}${depsText}`;
+}
+
+/**
+ * Format a subtask in compact format with indentation
+ * @param {Object} subtask - Subtask object
+ * @param {string|number} parentId - Parent task ID
+ * @param {number} maxTitleLength - Maximum title length before truncation
+ * @returns {string} - Formatted subtask line
+ */
+function formatCompactSubtask(subtask, parentId, maxTitleLength = 47) {
+	const status = subtask.status || 'pending';
+	const title = truncate(subtask.title || 'Untitled', maxTitleLength);
+
+	// Use colored status from existing function
+	const coloredStatus = getStatusWithColor(status, true);
+
+	// Format dependencies using shared helper
+	const depsText = formatCompactDependencies(subtask.dependencies);
+
+	return `  ${chalk.cyan(parentId + '.' + subtask.id)} ${coloredStatus} ${chalk.dim(title)}${depsText}`;
+}
+
+/**
+ * Render complete compact output
+ * @param {Array} filteredTasks - Tasks to display
+ * @param {boolean} withSubtasks - Whether to include subtasks
+ * @returns {void} - Outputs directly to console
+ */
+function renderCompactOutput(filteredTasks, withSubtasks) {
+	if (filteredTasks.length === 0) {
+		console.log('No tasks found');
+		return;
+	}
+
+	const output = [];
+
+	filteredTasks.forEach((task) => {
+		output.push(formatCompactTask(task));
+
+		if (withSubtasks && task.subtasks && task.subtasks.length > 0) {
+			task.subtasks.forEach((subtask) => {
+				output.push(formatCompactSubtask(subtask, task.id));
+			});
+		}
+	});
+
+	console.log(output.join('\n'));
+}
+
 export default listTasks;

scripts/modules/task-manager/move-task.js

@@ -1,7 +1,65 @@
 import path from 'path';
-import { log, readJSON, writeJSON, setTasksForTag } from '../utils.js';
-import { isTaskDependentOn } from '../task-manager.js';
+import {
+	log,
+	readJSON,
+	writeJSON,
+	setTasksForTag,
+	traverseDependencies
+} from '../utils.js';
 import generateTaskFiles from './generate-task-files.js';
+import {
+	findCrossTagDependencies,
+	getDependentTaskIds,
+	validateSubtaskMove
+} from '../dependency-manager.js';
+
+/**
+ * Find all dependencies recursively for a set of source tasks with depth limiting
+ * @param {Array} sourceTasks - The source tasks to find dependencies for
+ * @param {Array} allTasks - All available tasks from all tags
+ * @param {Object} options - Options object
+ * @param {number} options.maxDepth - Maximum recursion depth (default: 50)
+ * @param {boolean} options.includeSelf - Whether to include self-references (default: false)
+ * @returns {Array} Array of all dependency task IDs
+ */
+function findAllDependenciesRecursively(sourceTasks, allTasks, options = {}) {
+	return traverseDependencies(sourceTasks, allTasks, {
+		...options,
+		direction: 'forward',
+		logger: { warn: console.warn }
+	});
+}
+
+/**
+ * Structured error class for move operations
+ */
+class MoveTaskError extends Error {
+	constructor(code, message, data = {}) {
+		super(message);
+		this.name = 'MoveTaskError';
+		this.code = code;
+		this.data = data;
+	}
+}
+
+/**
+ * Error codes for move operations
+ */
+const MOVE_ERROR_CODES = {
+	CROSS_TAG_DEPENDENCY_CONFLICTS: 'CROSS_TAG_DEPENDENCY_CONFLICTS',
+	CANNOT_MOVE_SUBTASK: 'CANNOT_MOVE_SUBTASK',
+	SOURCE_TARGET_TAGS_SAME: 'SOURCE_TARGET_TAGS_SAME',
+	TASK_NOT_FOUND: 'TASK_NOT_FOUND',
+	SUBTASK_NOT_FOUND: 'SUBTASK_NOT_FOUND',
+	PARENT_TASK_NOT_FOUND: 'PARENT_TASK_NOT_FOUND',
+	PARENT_TASK_NO_SUBTASKS: 'PARENT_TASK_NO_SUBTASKS',
+	DESTINATION_TASK_NOT_FOUND: 'DESTINATION_TASK_NOT_FOUND',
+	TASK_ALREADY_EXISTS: 'TASK_ALREADY_EXISTS',
+	INVALID_TASKS_FILE: 'INVALID_TASKS_FILE',
+	ID_COUNT_MISMATCH: 'ID_COUNT_MISMATCH',
+	INVALID_SOURCE_TAG: 'INVALID_SOURCE_TAG',
+	INVALID_TARGET_TAG: 'INVALID_TARGET_TAG'
+};
 
 /**
  * Move one or more tasks/subtasks to new positions
@@ -27,7 +85,8 @@ async function moveTask(
 	const destinationIds = destinationId.split(',').map((id) => id.trim());
 
 	if (sourceIds.length !== destinationIds.length) {
-		throw new Error(
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.ID_COUNT_MISMATCH,
 			`Number of source IDs (${sourceIds.length}) must match number of destination IDs (${destinationIds.length})`
 		);
 	}
@@ -72,7 +131,8 @@ async function moveTask(
 
 	// Ensure the tag exists in the raw data
 	if (!rawData || !rawData[tag] || !Array.isArray(rawData[tag].tasks)) {
-		throw new Error(
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.INVALID_TASKS_FILE,
 			`Invalid tasks file or tag "${tag}" not found at ${tasksPath}`
 		);
 	}
@@ -137,10 +197,14 @@ function moveSubtaskToSubtask(tasks, sourceId, destinationId) {
 	const destParentTask = tasks.find((t) => t.id === destParentId);
 
 	if (!sourceParentTask) {
-		throw new Error(`Source parent task with ID ${sourceParentId} not found`);
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.PARENT_TASK_NOT_FOUND,
+			`Source parent task with ID ${sourceParentId} not found`
+		);
 	}
 	if (!destParentTask) {
-		throw new Error(
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.PARENT_TASK_NOT_FOUND,
 			`Destination parent task with ID ${destParentId} not found`
 		);
 	}
@@ -158,7 +222,10 @@ function moveSubtaskToSubtask(tasks, sourceId, destinationId) {
 		(st) => st.id === sourceSubtaskId
 	);
 	if (sourceSubtaskIndex === -1) {
-		throw new Error(`Source subtask ${sourceId} not found`);
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.SUBTASK_NOT_FOUND,
+			`Source subtask ${sourceId} not found`
+		);
 	}
 
 	const sourceSubtask = sourceParentTask.subtasks[sourceSubtaskIndex];
@@ -216,10 +283,16 @@ function moveSubtaskToTask(tasks, sourceId, destinationId) {
 	const sourceParentTask = tasks.find((t) => t.id === sourceParentId);
 
 	if (!sourceParentTask) {
-		throw new Error(`Source parent task with ID ${sourceParentId} not found`);
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.PARENT_TASK_NOT_FOUND,
+			`Source parent task with ID ${sourceParentId} not found`
+		);
 	}
 	if (!sourceParentTask.subtasks) {
-		throw new Error(`Source parent task ${sourceParentId} has no subtasks`);
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.PARENT_TASK_NO_SUBTASKS,
+			`Source parent task ${sourceParentId} has no subtasks`
+		);
 	}
 
 	// Find source subtask
@@ -227,7 +300,10 @@ function moveSubtaskToTask(tasks, sourceId, destinationId) {
 		(st) => st.id === sourceSubtaskId
 	);
 	if (sourceSubtaskIndex === -1) {
-		throw new Error(`Source subtask ${sourceId} not found`);
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.SUBTASK_NOT_FOUND,
+			`Source subtask ${sourceId} not found`
+		);
 	}
 
 	const sourceSubtask = sourceParentTask.subtasks[sourceSubtaskIndex];
@@ -235,7 +311,8 @@ function moveSubtaskToTask(tasks, sourceId, destinationId) {
 	// Check if destination task exists
 	const existingDestTask = tasks.find((t) => t.id === destTaskId);
 	if (existingDestTask) {
-		throw new Error(
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.TASK_ALREADY_EXISTS,
 			`Cannot move to existing task ID ${destTaskId}. Choose a different ID or use subtask destination.`
 		);
 	}
@@ -282,10 +359,14 @@ function moveTaskToSubtask(tasks, sourceId, destinationId) {
 	const destParentTask = tasks.find((t) => t.id === destParentId);
 
 	if (sourceTaskIndex === -1) {
-		throw new Error(`Source task with ID ${sourceTaskId} not found`);
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.TASK_NOT_FOUND,
+			`Source task with ID ${sourceTaskId} not found`
+		);
 	}
 	if (!destParentTask) {
-		throw new Error(
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.PARENT_TASK_NOT_FOUND,
 			`Destination parent task with ID ${destParentId} not found`
 		);
 	}
@@ -340,7 +421,10 @@ function moveTaskToTask(tasks, sourceId, destinationId) {
 	// Find source task
 	const sourceTaskIndex = tasks.findIndex((t) => t.id === sourceTaskId);
 	if (sourceTaskIndex === -1) {
-		throw new Error(`Source task with ID ${sourceTaskId} not found`);
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.TASK_NOT_FOUND,
+			`Source task with ID ${sourceTaskId} not found`
+		);
 	}
 
 	const sourceTask = tasks[sourceTaskIndex];
@@ -353,7 +437,8 @@ function moveTaskToTask(tasks, sourceId, destinationId) {
 		const destTask = tasks[destTaskIndex];
 
 		// For now, throw an error to avoid accidental overwrites
-		throw new Error(
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.TASK_ALREADY_EXISTS,
 			`Task with ID ${destTaskId} already exists. Use a different destination ID.`
 		);
 	} else {
@@ -478,4 +563,434 @@ function moveTaskToNewId(tasks, sourceTaskIndex, sourceTask, destTaskId) {
 	};
 }
 
+/**
+ * Get all tasks from all tags with tag information
+ * @param {Object} rawData - The raw tagged data object
+ * @returns {Array} A flat array of all task objects with tag property
+ */
+function getAllTasksWithTags(rawData) {
+	let allTasks = [];
+	for (const tagName in rawData) {
+		if (
+			Object.prototype.hasOwnProperty.call(rawData, tagName) &&
+			rawData[tagName] &&
+			Array.isArray(rawData[tagName].tasks)
+		) {
+			const tasksWithTag = rawData[tagName].tasks.map((task) => ({
+				...task,
+				tag: tagName
+			}));
+			allTasks = allTasks.concat(tasksWithTag);
+		}
+	}
+	return allTasks;
+}
+
+/**
+ * Validate move operation parameters and data
+ * @param {string} tasksPath - Path to tasks.json file
+ * @param {Array} taskIds - Array of task IDs to move
+ * @param {string} sourceTag - Source tag name
+ * @param {string} targetTag - Target tag name
+ * @param {Object} context - Context object
+ * @returns {Object} Validation result with rawData and sourceTasks
+ */
+async function validateMove(tasksPath, taskIds, sourceTag, targetTag, context) {
+	const { projectRoot } = context;
+
+	// Read the raw data without tag resolution to preserve tagged structure
+	let rawData = readJSON(tasksPath, projectRoot, sourceTag);
+
+	// Handle the case where readJSON returns resolved data with _rawTaggedData
+	if (rawData && rawData._rawTaggedData) {
+		rawData = rawData._rawTaggedData;
+	}
+
+	// Validate source tag exists
+	if (
+		!rawData ||
+		!rawData[sourceTag] ||
+		!Array.isArray(rawData[sourceTag].tasks)
+	) {
+		throw new MoveTaskError(
+			MOVE_ERROR_CODES.INVALID_SOURCE_TAG,
+			`Source tag "${sourceTag}" not found or invalid`
+		);
+	}
+
+	// Create target tag if it doesn't exist
+	if (!rawData[targetTag]) {
+		rawData[targetTag] = { tasks: [] };
+		log('info', `Created new tag "${targetTag}"`);
+	}
+
+	// Normalize all IDs to strings once for consistent comparison
+	const normalizedSearchIds = taskIds.map((id) => String(id));
+
+	const sourceTasks = rawData[sourceTag].tasks.filter((t) => {
+		const normalizedTaskId = String(t.id);
+		return normalizedSearchIds.includes(normalizedTaskId);
+	});
+
+	// Validate subtask movement
+	taskIds.forEach((taskId) => {
+		validateSubtaskMove(taskId, sourceTag, targetTag);
+	});
+
+	return { rawData, sourceTasks };
+}
+
+/**
+ * Load and prepare task data for move operation
+ * @param {Object} validation - Validation result from validateMove
+ * @returns {Object} Prepared data with rawData, sourceTasks, and allTasks
+ */
+async function prepareTaskData(validation) {
+	const { rawData, sourceTasks } = validation;
+
+	// Get all tasks for validation
+	const allTasks = getAllTasksWithTags(rawData);
+
+	return { rawData, sourceTasks, allTasks };
+}
+
+/**
+ * Resolve dependencies and determine tasks to move
+ * @param {Array} sourceTasks - Source tasks to move
+ * @param {Array} allTasks - All available tasks from all tags
+ * @param {Object} options - Move options
+ * @param {Array} taskIds - Original task IDs
+ * @param {string} sourceTag - Source tag name
+ * @param {string} targetTag - Target tag name
+ * @returns {Object} Tasks to move and dependency resolution info
+ */
+async function resolveDependencies(
+	sourceTasks,
+	allTasks,
+	options,
+	taskIds,
+	sourceTag,
+	targetTag
+) {
+	const { withDependencies = false, ignoreDependencies = false } = options;
+
+	// Handle --with-dependencies flag first (regardless of cross-tag dependencies)
+	if (withDependencies) {
+		// Move dependent tasks along with main tasks
+		// Find ALL dependencies recursively within the same tag
+		const allDependentTaskIds = findAllDependenciesRecursively(
+			sourceTasks,
+			allTasks,
+			{ maxDepth: 100, includeSelf: false }
+		);
+		const allTaskIdsToMove = [...new Set([...taskIds, ...allDependentTaskIds])];
+
+		log(
+			'info',
+			`Moving ${allTaskIdsToMove.length} tasks (including dependencies): ${allTaskIdsToMove.join(', ')}`
+		);
+
+		return {
+			tasksToMove: allTaskIdsToMove,
+			dependencyResolution: {
+				type: 'with-dependencies',
+				dependentTasks: allDependentTaskIds
+			}
+		};
+	}
+
+	// Find cross-tag dependencies (these shouldn't exist since dependencies are only within tags)
+	const crossTagDependencies = findCrossTagDependencies(
+		sourceTasks,
+		sourceTag,
+		targetTag,
+		allTasks
+	);
+
+	if (crossTagDependencies.length > 0) {
+		if (ignoreDependencies) {
+			// Break cross-tag dependencies (edge case - shouldn't normally happen)
+			sourceTasks.forEach((task) => {
+				task.dependencies = task.dependencies.filter((depId) => {
+					// Handle both task IDs and subtask IDs (e.g., "1.2")
+					let depTask = null;
+					if (typeof depId === 'string' && depId.includes('.')) {
+						// It's a subtask ID - extract parent task ID and find the parent task
+						const [parentId, subtaskId] = depId
+							.split('.')
+							.map((id) => parseInt(id, 10));
+						depTask = allTasks.find((t) => t.id === parentId);
+					} else {
+						// It's a regular task ID - normalize to number for comparison
+						const normalizedDepId =
+							typeof depId === 'string' ? parseInt(depId, 10) : depId;
+						depTask = allTasks.find((t) => t.id === normalizedDepId);
+					}
+					return !depTask || depTask.tag === targetTag;
+				});
+			});
+
+			log(
+				'warn',
+				`Removed ${crossTagDependencies.length} cross-tag dependencies`
+			);
+
+			return {
+				tasksToMove: taskIds,
+				dependencyResolution: {
+					type: 'ignored-dependencies',
+					conflicts: crossTagDependencies
+				}
+			};
+		} else {
+			// Block move and show error
+			throw new MoveTaskError(
+				MOVE_ERROR_CODES.CROSS_TAG_DEPENDENCY_CONFLICTS,
+				`Cannot move tasks: ${crossTagDependencies.length} cross-tag dependency conflicts found`,
+				{
+					conflicts: crossTagDependencies,
+					sourceTag,
+					targetTag,
+					taskIds
+				}
+			);
+		}
+	}
+
+	return {
+		tasksToMove: taskIds,
+		dependencyResolution: { type: 'no-conflicts' }
+	};
+}
+
+/**
+ * Execute the actual move operation
+ * @param {Array} tasksToMove - Array of task IDs to move
+ * @param {string} sourceTag - Source tag name
+ * @param {string} targetTag - Target tag name
+ * @param {Object} rawData - Raw data object
+ * @param {Object} context - Context object
+ * @param {string} tasksPath - Path to tasks.json file
+ * @returns {Object} Move operation result
+ */
+async function executeMoveOperation(
+	tasksToMove,
+	sourceTag,
+	targetTag,
+	rawData,
+	context,
+	tasksPath
+) {
+	const { projectRoot } = context;
+	const movedTasks = [];
+
+	// Move each task from source to target tag
+	for (const taskId of tasksToMove) {
+		// Normalize taskId to number for comparison
+		const normalizedTaskId =
+			typeof taskId === 'string' ? parseInt(taskId, 10) : taskId;
+
+		const sourceTaskIndex = rawData[sourceTag].tasks.findIndex(
+			(t) => t.id === normalizedTaskId
+		);
+
+		if (sourceTaskIndex === -1) {
+			throw new MoveTaskError(
+				MOVE_ERROR_CODES.TASK_NOT_FOUND,
+				`Task ${taskId} not found in source tag "${sourceTag}"`
+			);
+		}
+
+		const taskToMove = rawData[sourceTag].tasks[sourceTaskIndex];
+
+		// Check for ID conflicts in target tag
+		const existingTaskIndex = rawData[targetTag].tasks.findIndex(
+			(t) => t.id === normalizedTaskId
+		);
+		if (existingTaskIndex !== -1) {
+			throw new MoveTaskError(
+				MOVE_ERROR_CODES.TASK_ALREADY_EXISTS,
+				`Task ${taskId} already exists in target tag "${targetTag}"`
+			);
+		}
+
+		// Remove from source tag
+		rawData[sourceTag].tasks.splice(sourceTaskIndex, 1);
+
+		// Preserve task metadata and add to target tag
+		const taskWithPreservedMetadata = preserveTaskMetadata(
+			taskToMove,
+			sourceTag,
+			targetTag
+		);
+		rawData[targetTag].tasks.push(taskWithPreservedMetadata);
+
+		movedTasks.push({
+			id: taskId,
+			fromTag: sourceTag,
+			toTag: targetTag
+		});
+
+		log('info', `Moved task ${taskId} from "${sourceTag}" to "${targetTag}"`);
+	}
+
+	return { rawData, movedTasks };
+}
+
+/**
+ * Finalize the move operation by saving data and returning result
+ * @param {Object} moveResult - Result from executeMoveOperation
+ * @param {string} tasksPath - Path to tasks.json file
+ * @param {Object} context - Context object
+ * @param {string} sourceTag - Source tag name
+ * @param {string} targetTag - Target tag name
+ * @returns {Object} Final result object
+ */
+async function finalizeMove(
+	moveResult,
+	tasksPath,
+	context,
+	sourceTag,
+	targetTag
+) {
+	const { projectRoot } = context;
+	const { rawData, movedTasks } = moveResult;
+
+	// Write the updated data
+	writeJSON(tasksPath, rawData, projectRoot, null);
+
+	return {
+		message: `Successfully moved ${movedTasks.length} tasks from "${sourceTag}" to "${targetTag}"`,
+		movedTasks
+	};
+}
+
+/**
+ * Move tasks between different tags with dependency handling
+ * @param {string} tasksPath - Path to tasks.json file
+ * @param {Array} taskIds - Array of task IDs to move
+ * @param {string} sourceTag - Source tag name
+ * @param {string} targetTag - Target tag name
+ * @param {Object} options - Move options
+ * @param {boolean} options.withDependencies - Move dependent tasks along with main task
+ * @param {boolean} options.ignoreDependencies - Break cross-tag dependencies during move
+ * @param {Object} context - Context object containing projectRoot and tag information
+ * @returns {Object} Result object with moved task details
+ */
+async function moveTasksBetweenTags(
+	tasksPath,
+	taskIds,
+	sourceTag,
+	targetTag,
+	options = {},
+	context = {}
+) {
+	// 1. Validation phase
+	const validation = await validateMove(
+		tasksPath,
+		taskIds,
+		sourceTag,
+		targetTag,
+		context
+	);
+
+	// 2. Load and prepare data
+	const { rawData, sourceTasks, allTasks } = await prepareTaskData(validation);
+
+	// 3. Handle dependencies
+	const { tasksToMove } = await resolveDependencies(
+		sourceTasks,
+		allTasks,
+		options,
+		taskIds,
+		sourceTag,
+		targetTag
+	);
+
+	// 4. Execute move
+	const moveResult = await executeMoveOperation(
+		tasksToMove,
+		sourceTag,
+		targetTag,
+		rawData,
+		context,
+		tasksPath
+	);
+
+	// 5. Save and return
+	return await finalizeMove(
+		moveResult,
+		tasksPath,
+		context,
+		sourceTag,
+		targetTag
+	);
+}
+
+/**
+ * Detect ID conflicts in target tag
+ * @param {Array} taskIds - Array of task IDs to check
+ * @param {string} targetTag - Target tag name
+ * @param {Object} rawData - Raw data object
+ * @returns {Array} Array of conflicting task IDs
+ */
+function detectIdConflicts(taskIds, targetTag, rawData) {
+	const conflicts = [];
+
+	if (!rawData[targetTag] || !Array.isArray(rawData[targetTag].tasks)) {
+		return conflicts;
+	}
+
+	taskIds.forEach((taskId) => {
+		// Normalize taskId to number for comparison
+		const normalizedTaskId =
+			typeof taskId === 'string' ? parseInt(taskId, 10) : taskId;
+		const existingTask = rawData[targetTag].tasks.find(
+			(t) => t.id === normalizedTaskId
+		);
+		if (existingTask) {
+			conflicts.push(taskId);
+		}
+	});
+
+	return conflicts;
+}
+
+/**
+ * Preserve task metadata during cross-tag moves
+ * @param {Object} task - Task object
+ * @param {string} sourceTag - Source tag name
+ * @param {string} targetTag - Target tag name
+ * @returns {Object} Task object with preserved metadata
+ */
+function preserveTaskMetadata(task, sourceTag, targetTag) {
+	// Update the tag property to reflect the new location
+	task.tag = targetTag;
+
+	// Add move history to task metadata
+	if (!task.metadata) {
+		task.metadata = {};
+	}
+
+	if (!task.metadata.moveHistory) {
+		task.metadata.moveHistory = [];
+	}
+
+	task.metadata.moveHistory.push({
+		fromTag: sourceTag,
+		toTag: targetTag,
+		timestamp: new Date().toISOString()
+	});
+
+	return task;
+}
+
 export default moveTask;
+export {
+	moveTasksBetweenTags,
+	getAllTasksWithTags,
+	detectIdConflicts,
+	preserveTaskMetadata,
+	MoveTaskError,
+	MOVE_ERROR_CODES
+};

scripts/modules/task-manager/parse-prd.js

@@ -1,377 +0,0 @@
-import fs from 'fs';
-import path from 'path';
-import chalk from 'chalk';
-import boxen from 'boxen';
-import { z } from 'zod';
-
-import {
-	log,
-	writeJSON,
-	enableSilentMode,
-	disableSilentMode,
-	isSilentMode,
-	readJSON,
-	findTaskById,
-	ensureTagMetadata,
-	getCurrentTag
-} from '../utils.js';
-
-import { generateObjectService } from '../ai-services-unified.js';
-import { getDebugFlag } from '../config-manager.js';
-import { getPromptManager } from '../prompt-manager.js';
-import { displayAiUsageSummary } from '../ui.js';
-
-// Define the Zod schema for a SINGLE task object
-const prdSingleTaskSchema = z.object({
-	id: z.number().int().positive(),
-	title: z.string().min(1),
-	description: z.string().min(1),
-	details: z.string().nullable(),
-	testStrategy: z.string().nullable(),
-	priority: z.enum(['high', 'medium', 'low']).nullable(),
-	dependencies: z.array(z.number().int().positive()).nullable(),
-	status: z.string().nullable()
-});
-
-// Define the Zod schema for the ENTIRE expected AI response object
-const prdResponseSchema = z.object({
-	tasks: z.array(prdSingleTaskSchema),
-	metadata: z.object({
-		projectName: z.string(),
-		totalTasks: z.number(),
-		sourceFile: z.string(),
-		generatedAt: z.string()
-	})
-});
-
-/**
- * Parse a PRD file and generate tasks
- * @param {string} prdPath - Path to the PRD file
- * @param {string} tasksPath - Path to the tasks.json file
- * @param {number} numTasks - Number of tasks to generate
- * @param {Object} options - Additional options
- * @param {boolean} [options.force=false] - Whether to overwrite existing tasks.json.
- * @param {boolean} [options.append=false] - Append to existing tasks file.
- * @param {boolean} [options.research=false] - Use research model for enhanced PRD analysis.
- * @param {Object} [options.reportProgress] - Function to report progress (optional, likely unused).
- * @param {Object} [options.mcpLog] - MCP logger object (optional).
- * @param {Object} [options.session] - Session object from MCP server (optional).
- * @param {string} [options.projectRoot] - Project root path (for MCP/env fallback).
- * @param {string} [options.tag] - Target tag for task generation.
- * @param {string} [outputFormat='text'] - Output format ('text' or 'json').
- */
-async function parsePRD(prdPath, tasksPath, numTasks, options = {}) {
-	const {
-		reportProgress,
-		mcpLog,
-		session,
-		projectRoot,
-		force = false,
-		append = false,
-		research = false,
-		tag
-	} = options;
-	const isMCP = !!mcpLog;
-	const outputFormat = isMCP ? 'json' : 'text';
-
-	// Use the provided tag, or the current active tag, or default to 'master'
-	const targetTag = tag;
-
-	const logFn = mcpLog
-		? mcpLog
-		: {
-				// Wrapper for CLI
-				info: (...args) => log('info', ...args),
-				warn: (...args) => log('warn', ...args),
-				error: (...args) => log('error', ...args),
-				debug: (...args) => log('debug', ...args),
-				success: (...args) => log('success', ...args)
-			};
-
-	// Create custom reporter using logFn
-	const report = (message, level = 'info') => {
-		// Check logFn directly
-		if (logFn && typeof logFn[level] === 'function') {
-			logFn[level](message);
-		} else if (!isSilentMode() && outputFormat === 'text') {
-			// Fallback to original log only if necessary and in CLI text mode
-			log(level, message);
-		}
-	};
-
-	report(
-		`Parsing PRD file: ${prdPath}, Force: ${force}, Append: ${append}, Research: ${research}`
-	);
-
-	let existingTasks = [];
-	let nextId = 1;
-	let aiServiceResponse = null;
-
-	try {
-		// Check if there are existing tasks in the target tag
-		let hasExistingTasksInTag = false;
-		if (fs.existsSync(tasksPath)) {
-			try {
-				// Read the entire file to check if the tag exists
-				const existingFileContent = fs.readFileSync(tasksPath, 'utf8');
-				const allData = JSON.parse(existingFileContent);
-
-				// Check if the target tag exists and has tasks
-				if (
-					allData[targetTag] &&
-					Array.isArray(allData[targetTag].tasks) &&
-					allData[targetTag].tasks.length > 0
-				) {
-					hasExistingTasksInTag = true;
-					existingTasks = allData[targetTag].tasks;
-					nextId = Math.max(...existingTasks.map((t) => t.id || 0)) + 1;
-				}
-			} catch (error) {
-				// If we can't read the file or parse it, assume no existing tasks in this tag
-				hasExistingTasksInTag = false;
-			}
-		}
-
-		// Handle file existence and overwrite/append logic based on target tag
-		if (hasExistingTasksInTag) {
-			if (append) {
-				report(
-					`Append mode enabled. Found ${existingTasks.length} existing tasks in tag '${targetTag}'. Next ID will be ${nextId}.`,
-					'info'
-				);
-			} else if (!force) {
-				// Not appending and not forcing overwrite, and there are existing tasks in the target tag
-				const overwriteError = new Error(
-					`Tag '${targetTag}' already contains ${existingTasks.length} tasks. Use --force to overwrite or --append to add to existing tasks.`
-				);
-				report(overwriteError.message, 'error');
-				if (outputFormat === 'text') {
-					console.error(chalk.red(overwriteError.message));
-				}
-				throw overwriteError;
-			} else {
-				// Force overwrite is true
-				report(
-					`Force flag enabled. Overwriting existing tasks in tag '${targetTag}'.`,
-					'info'
-				);
-			}
-		} else {
-			// No existing tasks in target tag, proceed without confirmation
-			report(
-				`Tag '${targetTag}' is empty or doesn't exist. Creating/updating tag with new tasks.`,
-				'info'
-			);
-		}
-
-		report(`Reading PRD content from ${prdPath}`, 'info');
-		const prdContent = fs.readFileSync(prdPath, 'utf8');
-		if (!prdContent) {
-			throw new Error(`Input file ${prdPath} is empty or could not be read.`);
-		}
-
-		// Load prompts using PromptManager
-		const promptManager = getPromptManager();
-
-		// Get defaultTaskPriority from config
-		const { getDefaultPriority } = await import('../config-manager.js');
-		const defaultTaskPriority = getDefaultPriority(projectRoot) || 'medium';
-
-		const { systemPrompt, userPrompt } = await promptManager.loadPrompt(
-			'parse-prd',
-			{
-				research,
-				numTasks,
-				nextId,
-				prdContent,
-				prdPath,
-				defaultTaskPriority
-			}
-		);
-
-		// Call the unified AI service
-		report(
-			`Calling AI service to generate tasks from PRD${research ? ' with research-backed analysis' : ''}...`,
-			'info'
-		);
-
-		// Call generateObjectService with the CORRECT schema and additional telemetry params
-		aiServiceResponse = await generateObjectService({
-			role: research ? 'research' : 'main', // Use research role if flag is set
-			session: session,
-			projectRoot: projectRoot,
-			schema: prdResponseSchema,
-			objectName: 'tasks_data',
-			systemPrompt: systemPrompt,
-			prompt: userPrompt,
-			commandName: 'parse-prd',
-			outputType: isMCP ? 'mcp' : 'cli'
-		});
-
-		// Create the directory if it doesn't exist
-		const tasksDir = path.dirname(tasksPath);
-		if (!fs.existsSync(tasksDir)) {
-			fs.mkdirSync(tasksDir, { recursive: true });
-		}
-		logFn.success(
-			`Successfully parsed PRD via AI service${research ? ' with research-backed analysis' : ''}.`
-		);
-
-		// Validate and Process Tasks
-		// const generatedData = aiServiceResponse?.mainResult?.object;
-
-		// Robustly get the actual AI-generated object
-		let generatedData = null;
-		if (aiServiceResponse?.mainResult) {
-			if (
-				typeof aiServiceResponse.mainResult === 'object' &&
-				aiServiceResponse.mainResult !== null &&
-				'tasks' in aiServiceResponse.mainResult
-			) {
-				// If mainResult itself is the object with a 'tasks' property
-				generatedData = aiServiceResponse.mainResult;
-			} else if (
-				typeof aiServiceResponse.mainResult.object === 'object' &&
-				aiServiceResponse.mainResult.object !== null &&
-				'tasks' in aiServiceResponse.mainResult.object
-			) {
-				// If mainResult.object is the object with a 'tasks' property
-				generatedData = aiServiceResponse.mainResult.object;
-			}
-		}
-
-		if (!generatedData || !Array.isArray(generatedData.tasks)) {
-			logFn.error(
-				`Internal Error: generateObjectService returned unexpected data structure: ${JSON.stringify(generatedData)}`
-			);
-			throw new Error(
-				'AI service returned unexpected data structure after validation.'
-			);
-		}
-
-		let currentId = nextId;
-		const taskMap = new Map();
-		const processedNewTasks = generatedData.tasks.map((task) => {
-			const newId = currentId++;
-			taskMap.set(task.id, newId);
-			return {
-				...task,
-				id: newId,
-				status: 'pending',
-				priority: task.priority || 'medium',
-				dependencies: Array.isArray(task.dependencies) ? task.dependencies : [],
-				subtasks: []
-			};
-		});
-
-		// Remap dependencies for the NEWLY processed tasks
-		processedNewTasks.forEach((task) => {
-			task.dependencies = task.dependencies
-				.map((depId) => taskMap.get(depId)) // Map old AI ID to new sequential ID
-				.filter(
-					(newDepId) =>
-						newDepId != null && // Must exist
-						newDepId < task.id && // Must be a lower ID (could be existing or newly generated)
-						(findTaskById(existingTasks, newDepId) || // Check if it exists in old tasks OR
-							processedNewTasks.some((t) => t.id === newDepId)) // check if it exists in new tasks
-				);
-		});
-
-		const finalTasks = append
-			? [...existingTasks, ...processedNewTasks]
-			: processedNewTasks;
-
-		// Read the existing file to preserve other tags
-		let outputData = {};
-		if (fs.existsSync(tasksPath)) {
-			try {
-				const existingFileContent = fs.readFileSync(tasksPath, 'utf8');
-				outputData = JSON.parse(existingFileContent);
-			} catch (error) {
-				// If we can't read the existing file, start with empty object
-				outputData = {};
-			}
-		}
-
-		// Update only the target tag, preserving other tags
-		outputData[targetTag] = {
-			tasks: finalTasks,
-			metadata: {
-				created:
-					outputData[targetTag]?.metadata?.created || new Date().toISOString(),
-				updated: new Date().toISOString(),
-				description: `Tasks for ${targetTag} context`
-			}
-		};
-
-		// Ensure the target tag has proper metadata
-		ensureTagMetadata(outputData[targetTag], {
-			description: `Tasks for ${targetTag} context`
-		});
-
-		// Write the complete data structure back to the file
-		fs.writeFileSync(tasksPath, JSON.stringify(outputData, null, 2));
-		report(
-			`Successfully ${append ? 'appended' : 'generated'} ${processedNewTasks.length} tasks in ${tasksPath}${research ? ' with research-backed analysis' : ''}`,
-			'success'
-		);
-
-		// Generate markdown task files after writing tasks.json
-		// await generateTaskFiles(tasksPath, path.dirname(tasksPath), { mcpLog });
-
-		// Handle CLI output (e.g., success message)
-		if (outputFormat === 'text') {
-			console.log(
-				boxen(
-					chalk.green(
-						`Successfully generated ${processedNewTasks.length} new tasks${research ? ' with research-backed analysis' : ''}. Total tasks in ${tasksPath}: ${finalTasks.length}`
-					),
-					{ padding: 1, borderColor: 'green', borderStyle: 'round' }
-				)
-			);
-
-			console.log(
-				boxen(
-					chalk.white.bold('Next Steps:') +
-						'\n\n' +
-						`${chalk.cyan('1.')} Run ${chalk.yellow('task-master list')} to view all tasks\n` +
-						`${chalk.cyan('2.')} Run ${chalk.yellow('task-master expand --id=<id>')} to break down a task into subtasks`,
-					{
-						padding: 1,
-						borderColor: 'cyan',
-						borderStyle: 'round',
-						margin: { top: 1 }
-					}
-				)
-			);
-
-			if (aiServiceResponse && aiServiceResponse.telemetryData) {
-				displayAiUsageSummary(aiServiceResponse.telemetryData, 'cli');
-			}
-		}
-
-		// Return telemetry data
-		return {
-			success: true,
-			tasksPath,
-			telemetryData: aiServiceResponse?.telemetryData,
-			tagInfo: aiServiceResponse?.tagInfo
-		};
-	} catch (error) {
-		report(`Error parsing PRD: ${error.message}`, 'error');
-
-		// Only show error UI for text output (CLI)
-		if (outputFormat === 'text') {
-			console.error(chalk.red(`Error: ${error.message}`));
-
-			if (getDebugFlag(projectRoot)) {
-				// Use projectRoot for debug flag check
-				console.error(error);
-			}
-		}
-
-		throw error; // Always re-throw for proper error handling
-	}
-}
-
-export default parsePRD;

scripts/modules/task-manager/parse-prd/index.js

@@ -0,0 +1,3 @@
+// Main entry point for parse-prd module
+export { default } from './parse-prd.js';
+export { default as parsePRD } from './parse-prd.js';