chore: implement requested changes

- add typescript
- add npm workspaces

.changeset/clarify-force-move-docs.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+docs(move): clarify cross-tag move docs; deprecate "force"; add explicit --with-dependencies/--ignore-dependencies examples

.changeset/config.json

@@ -8,10 +8,11 @@
   ],
   "commit": false,
   "fixed": [],
+  "linked": [],
   "access": "public",
   "baseBranch": "main",
+  "updateInternalDependencies": "patch",
   "ignore": [
-    "docs",
-    "@tm/claude-code-plugin"
+    "docs"
   ]
 }

.changeset/crazy-zebras-drum.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": minor
+---
+
+Restore Taskmaster claude-code commands and move clear commands under /remove to avoid collision with the claude-code /clear command.

.changeset/curvy-moons-dig.md

@@ -0,0 +1,9 @@
+---
+"task-master-ai": minor
+---
+
+Enhanced Gemini CLI provider with codebase-aware task generation
+
+Added automatic codebase analysis for Gemini CLI provider in parse-prd, and analyze-complexity, add-task, udpate-task, update, update-subtask commands
+When using Gemini CLI 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

.changeset/pre.json

@@ -0,0 +1,16 @@
+{
+  "mode": "pre",
+  "tag": "rc",
+  "initialVersions": {
+    "task-master-ai": "0.25.1",
+    "docs": "0.0.1",
+    "extension": "0.24.1"
+  },
+  "changesets": [
+    "clarify-force-move-docs",
+    "curvy-moons-dig",
+    "sour-coins-lay",
+    "strong-eagles-vanish",
+    "wet-candies-accept"
+  ]
+}

.changeset/sour-coins-lay.md

@@ -0,0 +1,11 @@
+---
+"task-master-ai": minor
+---
+
+Add configurable codebase analysis feature flag with multiple configuration sources
+
+Users can now control whether codebase analysis features (Claude Code and Gemini CLI integration) are enabled through environment variables, MCP configuration, or project config files.
+
+Priority order: .env > MCP session env > .taskmaster/config.json.
+
+Set `TASKMASTER_ENABLE_CODEBASE_ANALYSIS=false` in `.env` to disable codebase analysis prompts and tool integration.

.changeset/strong-eagles-vanish.md

@@ -0,0 +1,12 @@
+---
+"task-master-ai": minor
+---
+
+feat(move): improve cross-tag move UX and safety
+
+- CLI: print "Next Steps" tips after cross-tag moves that used --ignore-dependencies (validate/fix guidance)
+- CLI: show dedicated help block on ID collisions (destination tag already has the ID)
+- Core: add structured suggestions to TASK_ALREADY_EXISTS errors
+- MCP: map ID collision errors to TASK_ALREADY_EXISTS and include suggestions
+- Tests: cover MCP options, error suggestions, CLI tips printing, and integration error payload suggestions
+---

.changeset/wet-candies-accept.md

@@ -0,0 +1,14 @@
+---
+"task-master-ai": minor
+---
+
+Enhanced Claude Code and Google CLI integration with automatic codebase analysis for task operations
+
+When using Claude Code as the AI provider, task management commands now automatically analyze your codebase before generating or updating tasks. This provides more accurate, context-aware implementation details that align with your project's existing architecture and patterns.
+
+Commands contextualised:
+
+- add-task
+- update-subtask
+- update-task
+- update

.claude-plugin/marketplace.json

@@ -1,32 +0,0 @@
-{
-	"name": "taskmaster",
-	"owner": {
-		"name": "Hamster",
-		"email": "ralph@tryhamster.com"
-	},
-	"metadata": {
-		"description": "Official marketplace for Taskmaster AI - AI-powered task management for ambitious development",
-		"version": "1.0.0"
-	},
-	"plugins": [
-		{
-			"name": "taskmaster",
-			"source": "./packages/claude-code-plugin",
-			"description": "AI-powered task management system for ambitious development workflows with intelligent orchestration, complexity analysis, and automated coordination",
-			"author": {
-				"name": "Hamster"
-			},
-			"homepage": "https://github.com/eyaltoledano/claude-task-master",
-			"repository": "https://github.com/eyaltoledano/claude-task-master",
-			"keywords": [
-				"task-management",
-				"ai",
-				"workflow",
-				"orchestration",
-				"automation",
-				"mcp"
-			],
-			"category": "productivity"
-		}
-	]
-}

.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/add-dependency/add-dependency.md

@@ -48,7 +48,7 @@ After adding dependency:
 ## Example Flows
 
 ```
-/taskmaster:add-dependency 5 needs 3
+/project:tm/add-dependency 5 needs 3
 → Task #5 now depends on Task #3
 → Task #5 is now blocked until #3 completes
 → Suggested: Also consider if #5 needs #4

.claude/commands/tm/add-subtask/add-subtask.md

@@ -56,12 +56,12 @@ task-master add-subtask --parent=<id> --task-id=<existing-id>
 ## Example Flows
 
 ```
-/taskmaster:add-subtask to 5: implement user authentication
+/project:tm/add-subtask to 5: implement user authentication
 → Created subtask #5.1: "implement user authentication"
 → Parent task #5 now has 1 subtask
 → Suggested next subtasks: tests, documentation
 
-/taskmaster:add-subtask 5: setup, implement, test
+/project:tm/add-subtask 5: setup, implement, test
 → Created 3 subtasks:
   #5.1: setup
   #5.2: implement  

.claude/commands/tm/add-subtask/convert-task-to-subtask.md

@@ -53,7 +53,7 @@ task-master add-subtask --parent=<parent-id> --task-id=<task-to-convert>
 ## Example
 
 ```
-/taskmaster:add-subtask/from-task 5 8
+/project:tm/add-subtask/from-task 5 8
 → Converting: Task #8 becomes subtask #5.1
 → Updated: 3 dependency references
 → Parent task #5 now has 1 subtask

.claude/commands/tm/analyze-complexity/analyze-complexity.md

@@ -115,7 +115,7 @@ Results are:
 
 After analysis:
 ```
-/taskmaster:expand 5    # Expand specific task
-/taskmaster:expand-all  # Expand all recommended
-/taskmaster:complexity-report  # View detailed report
+/project:tm/expand 5    # Expand specific task
+/project:tm/expand/all  # Expand all recommended
+/project:tm/complexity-report  # View detailed report
 ```

.claude/commands/tm/complexity-report/complexity-report.md

@@ -105,13 +105,13 @@ Use report for:
 ## Example Usage
 
 ```
-/taskmaster:complexity-report
+/project:tm/complexity-report
 → Opens latest analysis
 
-/taskmaster:complexity-report --file=archived/2024-01-01.md
+/project:tm/complexity-report --file=archived/2024-01-01.md
 → View historical analysis
 
 After viewing:
-/taskmaster:expand 5
+/project:tm/expand 5
 → Expand high-complexity task
 ```

.claude/commands/tm/fix-dependencies/fix-dependencies.md

@@ -70,7 +70,7 @@ Manual Review Needed:
 ⚠️ Task #45 has 8 dependencies
   Suggestion: Break into subtasks
 
-Run '/taskmaster:validate-dependencies' to verify fixes
+Run '/project:tm/validate-dependencies' to verify fixes
 ```
 
 ## Safety

.claude/commands/tm/help.md

@@ -0,0 +1,81 @@
+Show help for Task Master commands.
+
+Arguments: $ARGUMENTS
+
+Display help for Task Master commands. If arguments provided, show specific command help.
+
+## Task Master Command Help
+
+### Quick Navigation
+
+Type `/project:tm/` and use tab completion to explore all commands.
+
+### Command Categories
+
+#### 🚀 Setup & Installation
+- `/project:tm/setup/install` - Comprehensive installation guide
+- `/project:tm/setup/quick-install` - One-line global install
+
+#### 📋 Project Setup
+- `/project:tm/init` - Initialize new project
+- `/project:tm/init/quick` - Quick setup with auto-confirm
+- `/project:tm/models` - View AI configuration
+- `/project:tm/models/setup` - Configure AI providers
+
+#### 🎯 Task Generation
+- `/project:tm/parse-prd` - Generate tasks from PRD
+- `/project:tm/parse-prd/with-research` - Enhanced parsing
+- `/project:tm/generate` - Create task files
+
+#### 📝 Task Management
+- `/project:tm/list` - List tasks (natural language filters)
+- `/project:tm/show <id>` - Display task details
+- `/project:tm/add-task` - Create new task
+- `/project:tm/update` - Update tasks naturally
+- `/project:tm/next` - Get next task recommendation
+
+#### 🔄 Status Management
+- `/project:tm/set-status/to-pending <id>`
+- `/project:tm/set-status/to-in-progress <id>`
+- `/project:tm/set-status/to-done <id>`
+- `/project:tm/set-status/to-review <id>`
+- `/project:tm/set-status/to-deferred <id>`
+- `/project:tm/set-status/to-cancelled <id>`
+
+#### 🔍 Analysis & Breakdown
+- `/project:tm/analyze-complexity` - Analyze task complexity
+- `/project:tm/expand <id>` - Break down complex task
+- `/project:tm/expand/all` - Expand all eligible tasks
+
+#### 🔗 Dependencies
+- `/project:tm/add-dependency` - Add task dependency
+- `/project:tm/remove-dependency` - Remove dependency
+- `/project:tm/validate-dependencies` - Check for issues
+
+#### 🤖 Workflows
+- `/project:tm/workflows/smart-flow` - Intelligent workflows
+- `/project:tm/workflows/pipeline` - Command chaining
+- `/project:tm/workflows/auto-implement` - Auto-implementation
+
+#### 📊 Utilities
+- `/project:tm/utils/analyze` - Project analysis
+- `/project:tm/status` - Project dashboard
+- `/project:tm/learn` - Interactive learning
+
+### Natural Language Examples
+
+```
+/project:tm/list pending high priority
+/project:tm/update mark all API tasks as done
+/project:tm/add-task create login system with OAuth
+/project:tm/show current
+```
+
+### Getting Started
+
+1. Install: `/project:tm/setup/quick-install`
+2. Initialize: `/project:tm/init/quick`
+3. Learn: `/project:tm/learn start`
+4. Work: `/project:tm/workflows/smart-flow`
+
+For detailed command info: `/project:tm/help <command-name>`

.claude/commands/tm/init/init-project-quick.md

@@ -30,17 +30,17 @@ task-master init -y
 After quick init:
 1. Configure AI models if needed:
    ```
-   /taskmaster:models/setup
+   /project:tm/models/setup
    ```
 
 2. Parse PRD if available:
    ```
-   /taskmaster:parse-prd <file>
+   /project:tm/parse-prd <file>
    ```
 
 3. Or create first task:
    ```
-   /taskmaster:add-task create initial setup
+   /project:tm/add-task create initial setup
    ```
 
 Perfect for rapid project setup!

.claude/commands/tm/init/init-project.md

@@ -45,6 +45,6 @@ After successful init:
 
 If PRD file provided:
 ```
-/taskmaster:init my-prd.md
+/project:tm/init my-prd.md
 → Automatically runs parse-prd after init
 ```

.claude/commands/tm/remove-dependency/remove-dependency.md

@@ -55,7 +55,7 @@ After removing:
 ## Example
 
 ```
-/taskmaster:remove-dependency 5 from 3
+/project:tm/remove-dependency 5 from 3
 → Removed: Task #5 no longer depends on #3
 → Task #5 is now UNBLOCKED and ready to start
 → Warning: Consider if #5 still needs #2 completed first

.claude/commands/tm/remove-subtask/remove-subtask.md

@@ -63,13 +63,13 @@ task-master remove-subtask --id=<parentId.subtaskId> --convert
 ## Example Flows
 
 ```
-/taskmaster:remove-subtask 5.1
+/project:tm/remove-subtask 5.1
 → Warning: Subtask #5.1 is in-progress
 → This will delete all subtask data
 → Parent task #5 will be updated
 Confirm deletion? (y/n)
 
-/taskmaster:remove-subtask 5.1 convert
+/project:tm/remove-subtask 5.1 convert
 → Converting subtask #5.1 to standalone task #89
 → Preserved: All task data and history
 → Updated: 2 dependency references

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

@@ -77,7 +77,7 @@ Suggest alternatives:
 ## Example
 
 ```
-/taskmaster:clear-subtasks 5
+/project:tm/clear-subtasks 5
 → Found 4 subtasks to remove
 → Warning: Subtask #5.2 is in-progress
 → Cleared all subtasks from task #5

.claude/commands/tm/remove-task/remove-task.md

@@ -85,17 +85,17 @@ Suggest before deletion:
 ## Example Flows
 
 ```
-/taskmaster:remove-task 5
+/project:tm/remove-task 5
 → Task #5 is in-progress with 8 hours logged
 → 3 other tasks depend on this
 → Suggestion: Mark as cancelled instead?
 Remove anyway? (y/n)
 
-/taskmaster:remove-task 5 -y
+/project:tm/remove-task 5 -y
 → Removed: Task #5 and 4 subtasks
 → Updated: 3 task dependencies
 → Warning: Tasks #7, #8, #9 now have missing dependency
-→ Run /taskmaster:fix-dependencies to resolve
+→ Run /project:tm/fix-dependencies to resolve
 ```
 
 ## Safety Features

.claude/commands/tm/tm-main.md

@@ -8,11 +8,11 @@ Commands are organized hierarchically to match Task Master's CLI structure while
 
 ## Project Setup & Configuration
 
-### `/taskmaster:init`
+### `/project:tm/init`
 - `init-project` - Initialize new project (handles PRD files intelligently)
 - `init-project-quick` - Quick setup with auto-confirmation (-y flag)
 
-### `/taskmaster:models`
+### `/project:tm/models`
 - `view-models` - View current AI model configuration
 - `setup-models` - Interactive model configuration
 - `set-main` - Set primary generation model
@@ -21,21 +21,21 @@ Commands are organized hierarchically to match Task Master's CLI structure while
 
 ## Task Generation
 
-### `/taskmaster:parse-prd`
+### `/project:tm/parse-prd`
 - `parse-prd` - Generate tasks from PRD document
 - `parse-prd-with-research` - Enhanced parsing with research mode
 
-### `/taskmaster:generate`
+### `/project:tm/generate`
 - `generate-tasks` - Create individual task files from tasks.json
 
 ## Task Management
 
-### `/taskmaster:list`
+### `/project:tm/list`
 - `list-tasks` - Smart listing with natural language filters
 - `list-tasks-with-subtasks` - Include subtasks in hierarchical view
 - `list-tasks-by-status` - Filter by specific status
 
-### `/taskmaster:set-status`
+### `/project:tm/set-status`
 - `to-pending` - Reset task to pending
 - `to-in-progress` - Start working on task
 - `to-done` - Mark task complete
@@ -43,84 +43,84 @@ Commands are organized hierarchically to match Task Master's CLI structure while
 - `to-deferred` - Defer task
 - `to-cancelled` - Cancel task
 
-### `/taskmaster:sync-readme`
+### `/project:tm/sync-readme`
 - `sync-readme` - Export tasks to README.md with formatting
 
-### `/taskmaster:update`
+### `/project:tm/update`
 - `update-task` - Update tasks with natural language
 - `update-tasks-from-id` - Update multiple tasks from a starting point
 - `update-single-task` - Update specific task
 
-### `/taskmaster:add-task`
+### `/project:tm/add-task`
 - `add-task` - Add new task with AI assistance
 
-### `/taskmaster:remove-task`
+### `/project:tm/remove-task`
 - `remove-task` - Remove task with confirmation
 
 ## Subtask Management
 
-### `/taskmaster:add-subtask`
+### `/project:tm/add-subtask`
 - `add-subtask` - Add new subtask to parent
 - `convert-task-to-subtask` - Convert existing task to subtask
 
-### `/taskmaster:remove-subtask`
+### `/project:tm/remove-subtask`
 - `remove-subtask` - Remove subtask (with optional conversion)
 
-### `/taskmaster:clear-subtasks`
+### `/project:tm/clear-subtasks`
 - `clear-subtasks` - Clear subtasks from specific task
 - `clear-all-subtasks` - Clear all subtasks globally
 
 ## Task Analysis & Breakdown
 
-### `/taskmaster:analyze-complexity`
+### `/project:tm/analyze-complexity`
 - `analyze-complexity` - Analyze and generate expansion recommendations
 
-### `/taskmaster:complexity-report`
+### `/project:tm/complexity-report`
 - `complexity-report` - Display complexity analysis report
 
-### `/taskmaster:expand`
+### `/project:tm/expand`
 - `expand-task` - Break down specific task
 - `expand-all-tasks` - Expand all eligible tasks
 - `with-research` - Enhanced expansion
 
 ## Task Navigation
 
-### `/taskmaster:next`
+### `/project:tm/next`
 - `next-task` - Intelligent next task recommendation
 
-### `/taskmaster:show`
+### `/project:tm/show`
 - `show-task` - Display detailed task information
 
-### `/taskmaster:status`
+### `/project:tm/status`
 - `project-status` - Comprehensive project dashboard
 
 ## Dependency Management
 
-### `/taskmaster:add-dependency`
+### `/project:tm/add-dependency`
 - `add-dependency` - Add task dependency
 
-### `/taskmaster:remove-dependency`
+### `/project:tm/remove-dependency`
 - `remove-dependency` - Remove task dependency
 
-### `/taskmaster:validate-dependencies`
+### `/project:tm/validate-dependencies`
 - `validate-dependencies` - Check for dependency issues
 
-### `/taskmaster:fix-dependencies`
+### `/project:tm/fix-dependencies`
 - `fix-dependencies` - Automatically fix dependency problems
 
 ## Workflows & Automation
 
-### `/taskmaster:workflows`
+### `/project:tm/workflows`
 - `smart-workflow` - Context-aware intelligent workflow execution
 - `command-pipeline` - Chain multiple commands together
 - `auto-implement-tasks` - Advanced auto-implementation with code generation
 
 ## Utilities
 
-### `/taskmaster:utils`
+### `/project:tm/utils`
 - `analyze-project` - Deep project analysis and insights
 
-### `/taskmaster:setup`
+### `/project:tm/setup`
 - `install-taskmaster` - Comprehensive installation guide
 - `quick-install-taskmaster` - One-line global installation
 
@@ -129,17 +129,17 @@ Commands are organized hierarchically to match Task Master's CLI structure while
 ### Natural Language
 Most commands accept natural language arguments:
 ```
-/taskmaster:add-task create user authentication system
-/taskmaster:update mark all API tasks as high priority
-/taskmaster:list show blocked tasks
+/project:tm/add-task create user authentication system
+/project:tm/update mark all API tasks as high priority
+/project:tm/list show blocked tasks
 ```
 
 ### ID-Based Commands
 Commands requiring IDs intelligently parse from $ARGUMENTS:
 ```
-/taskmaster:show 45
-/taskmaster:expand 23
-/taskmaster:set-status/to-done 67
+/project:tm/show 45
+/project:tm/expand 23
+/project:tm/set-status/to-done 67
 ```
 
 ### Smart Defaults

.claude/commands/tm/update/update-single-task.md

@@ -66,7 +66,7 @@ The AI:
 ## Example Updates
 
 ```
-/taskmaster:update/single 5: add rate limiting
+/project:tm/update/single 5: add rate limiting
 → Updating Task #5: "Implement API endpoints"
 
 Current: Basic CRUD endpoints

.claude/commands/tm/update/update-tasks-from-id.md

@@ -77,7 +77,7 @@ AI analyzes the update context and:
 ## Example Updates
 
 ```
-/taskmaster:update/from-id 5: change database to PostgreSQL
+/project:tm/update/from-id 5: change database to PostgreSQL
 → Analyzing impact starting from task #5
 → Found 6 related tasks to update
 → Updates will maintain consistency

.claude/commands/tm/validate-dependencies/validate-dependencies.md

@@ -66,6 +66,6 @@ For each issue found:
 ## Next Steps
 
 After validation:
-- Run `/taskmaster:fix-dependencies` to auto-fix
+- Run `/project:tm/fix-dependencies` to auto-fix
 - Manually adjust problematic dependencies
 - Rerun to verify fixes

.cursor/mcp.json

@@ -2,7 +2,7 @@
 	"mcpServers": {
 		"task-master-ai": {
 			"command": "node",
-			"args": ["./dist/mcp-server.js"],
+			"args": ["./mcp-server/server.js"],
 			"env": {
 				"ANTHROPIC_API_KEY": "ANTHROPIC_API_KEY_HERE",
 				"PERPLEXITY_API_KEY": "PERPLEXITY_API_KEY_HERE",

.github/scripts/parse-metrics.mjs

@@ -1,157 +0,0 @@
-#!/usr/bin/env node
-
-import { readFileSync, existsSync, writeFileSync } from 'fs';
-
-function parseMetricsTable(content, metricName) {
-	const lines = content.split('\n');
-
-	for (let i = 0; i < lines.length; i++) {
-		const line = lines[i].trim();
-		// Match a markdown table row like: | Metric Name | value | ...
-		const safeName = metricName.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
-		const re = new RegExp(`^\\|\\s*${safeName}\\s*\\|\\s*([^|]+)\\|?`);
-		const match = line.match(re);
-		if (match) {
-			return match[1].trim() || 'N/A';
-		}
-	}
-	return 'N/A';
-}
-
-function parseCountMetric(content, metricName) {
-	const result = parseMetricsTable(content, metricName);
-	// Extract number from string, handling commas and spaces
-	const numberMatch = result.toString().match(/[\d,]+/);
-	if (numberMatch) {
-		const number = parseInt(numberMatch[0].replace(/,/g, ''));
-		return isNaN(number) ? 0 : number;
-	}
-	return 0;
-}
-
-function main() {
-	const metrics = {
-		issues_created: 0,
-		issues_closed: 0,
-		prs_created: 0,
-		prs_merged: 0,
-		issue_avg_first_response: 'N/A',
-		issue_avg_time_to_close: 'N/A',
-		pr_avg_first_response: 'N/A',
-		pr_avg_merge_time: 'N/A'
-	};
-
-	// Parse issue metrics
-	if (existsSync('issue_metrics.md')) {
-		console.log('📄 Found issue_metrics.md, parsing...');
-		const issueContent = readFileSync('issue_metrics.md', 'utf8');
-
-		metrics.issues_created = parseCountMetric(
-			issueContent,
-			'Total number of items created'
-		);
-		metrics.issues_closed = parseCountMetric(
-			issueContent,
-			'Number of items closed'
-		);
-		metrics.issue_avg_first_response = parseMetricsTable(
-			issueContent,
-			'Time to first response'
-		);
-		metrics.issue_avg_time_to_close = parseMetricsTable(
-			issueContent,
-			'Time to close'
-		);
-	} else {
-		console.warn('[parse-metrics] issue_metrics.md not found; using defaults.');
-	}
-
-	// Parse PR created metrics
-	if (existsSync('pr_created_metrics.md')) {
-		console.log('📄 Found pr_created_metrics.md, parsing...');
-		const prCreatedContent = readFileSync('pr_created_metrics.md', 'utf8');
-
-		metrics.prs_created = parseCountMetric(
-			prCreatedContent,
-			'Total number of items created'
-		);
-		metrics.pr_avg_first_response = parseMetricsTable(
-			prCreatedContent,
-			'Time to first response'
-		);
-	} else {
-		console.warn(
-			'[parse-metrics] pr_created_metrics.md not found; using defaults.'
-		);
-	}
-
-	// Parse PR merged metrics (for more accurate merge data)
-	if (existsSync('pr_merged_metrics.md')) {
-		console.log('📄 Found pr_merged_metrics.md, parsing...');
-		const prMergedContent = readFileSync('pr_merged_metrics.md', 'utf8');
-
-		metrics.prs_merged = parseCountMetric(
-			prMergedContent,
-			'Total number of items created'
-		);
-		// For merged PRs, "Time to close" is actually time to merge
-		metrics.pr_avg_merge_time = parseMetricsTable(
-			prMergedContent,
-			'Time to close'
-		);
-	} else {
-		console.warn(
-			'[parse-metrics] pr_merged_metrics.md not found; falling back to pr_metrics.md.'
-		);
-		// Fallback: try old pr_metrics.md if it exists
-		if (existsSync('pr_metrics.md')) {
-			console.log('📄 Falling back to pr_metrics.md...');
-			const prContent = readFileSync('pr_metrics.md', 'utf8');
-
-			const mergedCount = parseCountMetric(prContent, 'Number of items merged');
-			metrics.prs_merged =
-				mergedCount || parseCountMetric(prContent, 'Number of items closed');
-
-			const maybeMergeTime = parseMetricsTable(
-				prContent,
-				'Average time to merge'
-			);
-			metrics.pr_avg_merge_time =
-				maybeMergeTime !== 'N/A'
-					? maybeMergeTime
-					: parseMetricsTable(prContent, 'Time to close');
-		} else {
-			console.warn('[parse-metrics] pr_metrics.md not found; using defaults.');
-		}
-	}
-
-	// Output for GitHub Actions
-	const output = Object.entries(metrics)
-		.map(([key, value]) => `${key}=${value}`)
-		.join('\n');
-
-	// Always output to stdout for debugging
-	console.log('\n=== FINAL METRICS ===');
-	Object.entries(metrics).forEach(([key, value]) => {
-		console.log(`${key}: ${value}`);
-	});
-
-	// Write to GITHUB_OUTPUT if in GitHub Actions
-	if (process.env.GITHUB_OUTPUT) {
-		try {
-			writeFileSync(process.env.GITHUB_OUTPUT, output + '\n', { flag: 'a' });
-			console.log(
-				`\nSuccessfully wrote metrics to ${process.env.GITHUB_OUTPUT}`
-			);
-		} catch (error) {
-			console.error(`Failed to write to GITHUB_OUTPUT: ${error.message}`);
-			process.exit(1);
-		}
-	} else {
-		console.log(
-			'\nNo GITHUB_OUTPUT environment variable found, skipping file write'
-		);
-	}
-}
-
-main();

.github/workflows/ci.yml

@@ -6,124 +6,73 @@ on:
       - main
       - next
   pull_request:
-  workflow_dispatch:
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
+    branches:
+      - main
+      - next
 
 permissions:
   contents: read
 
-env:
-  DO_NOT_TRACK: 1
-  NODE_ENV: development
-
 jobs:
-  # Fast checks that can run in parallel
-  format-check:
-    name: Format Check
+  setup:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
         with:
-          fetch-depth: 2
+          fetch-depth: 0
 
       - uses: actions/setup-node@v4
         with:
           node-version: 20
-          cache: "npm"
+          cache: 'npm'
 
-      - name: Install dependencies
-        run: npm install --frozen-lockfile --prefer-offline
-        timeout-minutes: 5
+      - name: Install Dependencies
+        id: install
+        run: npm ci
+        timeout-minutes: 2
+
+      - name: Cache node_modules
+        uses: actions/cache@v4
+        with:
+          path: node_modules
+          key: ${{ runner.os }}-node-modules-${{ hashFiles('**/package-lock.json') }}
+
+  format-check:
+    needs: setup
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+
+      - name: Restore node_modules
+        uses: actions/cache@v4
+        with:
+          path: node_modules
+          key: ${{ runner.os }}-node-modules-${{ hashFiles('**/package-lock.json') }}
 
       - name: Format Check
         run: npm run format-check
         env:
           FORCE_COLOR: 1
 
-  typecheck:
-    name: Typecheck
-    timeout-minutes: 10
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 2
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm install --frozen-lockfile --prefer-offline
-        timeout-minutes: 5
-
-      - name: Typecheck
-        run: npm run turbo:typecheck
-        env:
-          FORCE_COLOR: 1
-
-  # Build job to ensure everything compiles
-  build:
-    name: Build
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 2
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm install --frozen-lockfile --prefer-offline
-        timeout-minutes: 5
-
-      - name: Build
-        run: npm run turbo:build
-        env:
-          NODE_ENV: production
-          FORCE_COLOR: 1
-          TM_PUBLIC_BASE_DOMAIN: ${{ secrets.TM_PUBLIC_BASE_DOMAIN }}
-          TM_PUBLIC_SUPABASE_URL: ${{ secrets.TM_PUBLIC_SUPABASE_URL }}
-          TM_PUBLIC_SUPABASE_ANON_KEY: ${{ secrets.TM_PUBLIC_SUPABASE_ANON_KEY }}
-
-      - name: Upload build artifacts
-        uses: actions/upload-artifact@v4
-        with:
-          name: build-artifacts
-          path: dist/
-          retention-days: 1
-
   test:
-    name: Test
-    timeout-minutes: 15
+    needs: setup
     runs-on: ubuntu-latest
-    needs: [format-check, typecheck, build]
     steps:
       - uses: actions/checkout@v4
-        with:
-          fetch-depth: 2
 
       - uses: actions/setup-node@v4
         with:
           node-version: 20
-          cache: "npm"
 
-      - name: Install dependencies
-        run: npm install --frozen-lockfile --prefer-offline
-        timeout-minutes: 5
-
-      - name: Download build artifacts
-        uses: actions/download-artifact@v4
+      - name: Restore node_modules
+        uses: actions/cache@v4
         with:
-          name: build-artifacts
-          path: dist/
+          path: node_modules
+          key: ${{ runner.os }}-node-modules-${{ hashFiles('**/package-lock.json') }}
 
       - name: Run Tests
         run: |
@@ -132,6 +81,7 @@ jobs:
           NODE_ENV: test
           CI: true
           FORCE_COLOR: 1
+        timeout-minutes: 10
 
       - name: Upload Test Results
         if: always()

.github/workflows/claude-docs-trigger.yml

@@ -1,57 +0,0 @@
-name: Trigger Claude Documentation Update
-
-on:
-  push:
-    branches:
-      - next
-    paths-ignore:
-      - "apps/docs/**"
-      - "*.md"
-      - ".github/workflows/**"
-
-jobs:
-  trigger-docs-update:
-    # Only run if changes were merged (not direct pushes from bots)
-    if: github.actor != 'github-actions[bot]' && github.actor != 'dependabot[bot]'
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      actions: write
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 2 # Need previous commit for comparison
-
-      - name: Get changed files
-        id: changed-files
-        run: |
-          echo "Changed files in this push:"
-          git diff --name-only HEAD^ HEAD | tee changed_files.txt
-
-          # Store changed files for Claude to analyze (escaped for JSON)
-          CHANGED_FILES=$(git diff --name-only HEAD^ HEAD | jq -Rs .)
-          echo "changed_files=$CHANGED_FILES" >> $GITHUB_OUTPUT
-
-          # Get the commit message (escaped for JSON)
-          COMMIT_MSG=$(git log -1 --pretty=%B | jq -Rs .)
-          echo "commit_message=$COMMIT_MSG" >> $GITHUB_OUTPUT
-
-          # Get diff for documentation context (escaped for JSON)
-          COMMIT_DIFF=$(git diff HEAD^ HEAD --stat | jq -Rs .)
-          echo "commit_diff=$COMMIT_DIFF" >> $GITHUB_OUTPUT
-
-          # Get commit SHA
-          echo "commit_sha=${{ github.sha }}" >> $GITHUB_OUTPUT
-
-      - name: Trigger Claude workflow
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          # Trigger the Claude docs updater workflow with the change information
-          gh workflow run claude-docs-updater.yml \
-            --ref next \
-            -f commit_sha="${{ steps.changed-files.outputs.commit_sha }}" \
-            -f commit_message=${{ steps.changed-files.outputs.commit_message }} \
-            -f changed_files=${{ steps.changed-files.outputs.changed_files }} \
-            -f commit_diff=${{ steps.changed-files.outputs.commit_diff }}

.github/workflows/claude-docs-updater.yml

@@ -1,27 +1,18 @@
 name: Claude Documentation Updater
 
 on:
-  workflow_dispatch:
-    inputs:
-      commit_sha:
-        description: 'The commit SHA that triggered this update'
-        required: true
-        type: string
-      commit_message:
-        description: 'The commit message'
-        required: true
-        type: string
-      changed_files:
-        description: 'List of changed files'
-        required: true
-        type: string
-      commit_diff:
-        description: 'Diff summary of changes'
-        required: true
-        type: string
+  push:
+    branches:
+      - next
+    paths-ignore:
+      - "apps/docs/**"
+      - "*.md"
+      - ".github/workflows/**"
 
 jobs:
   update-docs:
+    # Only run if changes were merged (not direct pushes from bots)
+    if: github.actor != 'github-actions[bot]' && github.actor != 'dependabot[bot]'
     runs-on: ubuntu-latest
     permissions:
       contents: write
@@ -31,8 +22,28 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v4
         with:
-          ref: next
-          fetch-depth: 0 # Need full history to checkout specific commit
+          fetch-depth: 2 # Need previous commit for comparison
+
+      - name: Get changed files
+        id: changed-files
+        run: |
+          echo "Changed files in this push:"
+          git diff --name-only HEAD^ HEAD | tee changed_files.txt
+
+          # Store changed files for Claude to analyze
+          echo "changed_files<<EOF" >> $GITHUB_OUTPUT
+          git diff --name-only HEAD^ HEAD >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
+
+          # Get the commit message and changes summary
+          echo "commit_message<<EOF" >> $GITHUB_OUTPUT
+          git log -1 --pretty=%B >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
+
+          # Get diff for documentation context
+          echo "commit_diff<<EOF" >> $GITHUB_OUTPUT
+          git diff HEAD^ HEAD --stat >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
 
       - name: Create docs update branch
         id: create-branch
@@ -60,12 +71,12 @@ jobs:
             You are a documentation specialist. Analyze the recent changes pushed to the 'next' branch and update the documentation accordingly.
 
             Recent changes:
-            - Commit: ${{ inputs.commit_message }}
+            - Commit: ${{ steps.changed-files.outputs.commit_message }}
             - Changed files:
-            ${{ inputs.changed_files }}
+            ${{ steps.changed-files.outputs.changed_files }}
 
             - Changes summary:
-            ${{ inputs.commit_diff }}
+            ${{ steps.changed-files.outputs.commit_diff }}
 
             Your task:
             1. Analyze the changes to understand what functionality was added, modified, or removed
@@ -102,7 +113,7 @@ jobs:
 
             This PR was automatically generated to update documentation based on recent changes.
             
-            Original commit: ${{ inputs.commit_message }}
+            Original commit: ${{ steps.changed-files.outputs.commit_message }}
             
             Co-authored-by: Claude <claude-assistant@anthropic.com>"
           fi
@@ -122,12 +133,12 @@ jobs:
             This PR automatically updates documentation based on recent changes merged to the \`next\` branch.
 
             ### Original Changes
-            **Commit:** ${{ inputs.commit_sha }}
-            **Message:** ${{ inputs.commit_message }}
+            **Commit:** ${{ github.sha }}
+            **Message:** ${{ steps.changed-files.outputs.commit_message }}
             
             ### Changed Files in Original Commit
             \`\`\`
-            ${{ inputs.changed_files }}
+            ${{ steps.changed-files.outputs.changed_files }}
             \`\`\`
 
             ### Documentation Updates

.github/workflows/extension-ci.yml

@@ -41,7 +41,8 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-node-
 
-      - name: Install Monorepo Dependencies
+      - name: Install Extension Dependencies
+        working-directory: apps/extension
         run: npm ci
         timeout-minutes: 5
 
@@ -67,6 +68,7 @@ jobs:
             ${{ runner.os }}-node-
 
       - name: Install if cache miss
+        working-directory: apps/extension
         run: npm ci
         timeout-minutes: 3
 
@@ -98,6 +100,7 @@ jobs:
             ${{ runner.os }}-node-
 
       - name: Install if cache miss
+        working-directory: apps/extension
         run: npm ci
         timeout-minutes: 3
 

.github/workflows/extension-release.yml

@@ -31,7 +31,8 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-node-
 
-      - name: Install Monorepo Dependencies
+      - name: Install Extension Dependencies
+        working-directory: apps/extension
         run: npm ci
         timeout-minutes: 5
 

.github/workflows/pre-release.yml

@@ -65,20 +65,6 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
 
-      - name: Run format
-        run: npm run format
-        env:
-          FORCE_COLOR: 1
-
-      - name: Build packages
-        run: npm run turbo:build
-        env:
-          NODE_ENV: production
-          FORCE_COLOR: 1
-          TM_PUBLIC_BASE_DOMAIN: ${{ secrets.TM_PUBLIC_BASE_DOMAIN }}
-          TM_PUBLIC_SUPABASE_URL: ${{ secrets.TM_PUBLIC_SUPABASE_URL }}
-          TM_PUBLIC_SUPABASE_ANON_KEY: ${{ secrets.TM_PUBLIC_SUPABASE_ANON_KEY }}
-
       - name: Create Release Candidate Pull Request or Publish Release Candidate to npm
         uses: changesets/action@v1
         with:

.github/workflows/release.yml

@@ -22,7 +22,7 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 20
-          cache: "npm"
+          cache: 'npm'
 
       - name: Cache node_modules
         uses: actions/cache@v4
@@ -41,15 +41,6 @@ jobs:
       - name: Check pre-release mode
         run: node ./.github/scripts/check-pre-release-mode.mjs "main"
 
-      - name: Build packages
-        run: npm run turbo:build
-        env:
-          NODE_ENV: production
-          FORCE_COLOR: 1
-          TM_PUBLIC_BASE_DOMAIN: ${{ secrets.TM_PUBLIC_BASE_DOMAIN }}
-          TM_PUBLIC_SUPABASE_URL: ${{ secrets.TM_PUBLIC_SUPABASE_URL }}
-          TM_PUBLIC_SUPABASE_ANON_KEY: ${{ secrets.TM_PUBLIC_SUPABASE_ANON_KEY }}
-
       - name: Create Release Pull Request or Publish to npm
         uses: changesets/action@v1
         with:

.github/workflows/weekly-metrics-discord.yml

@@ -8,7 +8,7 @@ on:
 
 permissions:
   contents: read
-  issues: read
+  issues: write
   pull-requests: read
 
 jobs:
@@ -17,25 +17,15 @@ jobs:
     env:
       DISCORD_WEBHOOK: ${{ secrets.DISCORD_METRICS_WEBHOOK }}
     steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-
-      - name: Get dates for last 14 days
+      - name: Get dates for last week
         run: |
-          set -Eeuo pipefail
-          # Last 14 days
-          first_day=$(date -d "14 days ago" +%Y-%m-%d)
+          # Last 7 days
+          first_day=$(date -d "7 days ago" +%Y-%m-%d)
           last_day=$(date +%Y-%m-%d)
 
           echo "first_day=$first_day" >> $GITHUB_ENV
           echo "last_day=$last_day" >> $GITHUB_ENV
           echo "week_of=$(date -d '7 days ago' +'Week of %B %d, %Y')" >> $GITHUB_ENV
-          echo "date_range=Past 14 days ($first_day to $last_day)" >> $GITHUB_ENV
 
       - name: Generate issue metrics
         uses: github/issue-metrics@v3
@@ -44,39 +34,40 @@ jobs:
           SEARCH_QUERY: "repo:${{ github.repository }} is:issue created:${{ env.first_day }}..${{ env.last_day }}"
           HIDE_TIME_TO_ANSWER: true
           HIDE_LABEL_METRICS: false
-          OUTPUT_FILE: issue_metrics.md
 
-      - name: Generate PR created metrics
+      - name: Generate PR metrics
         uses: github/issue-metrics@v3
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SEARCH_QUERY: "repo:${{ github.repository }} is:pr created:${{ env.first_day }}..${{ env.last_day }}"
-          OUTPUT_FILE: pr_created_metrics.md
-
-      - name: Generate PR merged metrics
-        uses: github/issue-metrics@v3
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          SEARCH_QUERY: "repo:${{ github.repository }} is:pr is:merged merged:${{ env.first_day }}..${{ env.last_day }}"
-          OUTPUT_FILE: pr_merged_metrics.md
-
-      - name: Debug generated metrics
-        run: |
-          set -Eeuo pipefail
-          echo "Listing markdown files in workspace:"
-          ls -la *.md || true
-          for f in issue_metrics.md pr_created_metrics.md pr_merged_metrics.md; do
-            if [ -f "$f" ]; then
-              echo "== $f (first 10 lines) =="
-              head -n 10 "$f"
-            else
-              echo "Missing $f"
-            fi
-          done
+          OUTPUT_FILE: pr_metrics.md
 
       - name: Parse metrics
         id: metrics
-        run: node .github/scripts/parse-metrics.mjs
+        run: |
+          # Parse the metrics from the generated markdown files
+          if [ -f "issue_metrics.md" ]; then
+            # Extract key metrics using grep/awk
+            AVG_TIME_TO_FIRST_RESPONSE=$(grep -A 1 "Average time to first response" issue_metrics.md | tail -1 | xargs || echo "N/A")
+            AVG_TIME_TO_CLOSE=$(grep -A 1 "Average time to close" issue_metrics.md | tail -1 | xargs || echo "N/A")
+            NUM_ISSUES_CREATED=$(grep -oP '\d+(?= issues created)' issue_metrics.md || echo "0")
+            NUM_ISSUES_CLOSED=$(grep -oP '\d+(?= issues closed)' issue_metrics.md || echo "0")
+          fi
+
+          if [ -f "pr_metrics.md" ]; then
+            PR_AVG_TIME_TO_MERGE=$(grep -A 1 "Average time to close" pr_metrics.md | tail -1 | xargs || echo "N/A")
+            NUM_PRS_CREATED=$(grep -oP '\d+(?= pull requests created)' pr_metrics.md || echo "0")
+            NUM_PRS_MERGED=$(grep -oP '\d+(?= pull requests closed)' pr_metrics.md || echo "0")
+          fi
+
+          # Set outputs for Discord action
+          echo "issues_created=${NUM_ISSUES_CREATED:-0}" >> $GITHUB_OUTPUT
+          echo "issues_closed=${NUM_ISSUES_CLOSED:-0}" >> $GITHUB_OUTPUT
+          echo "prs_created=${NUM_PRS_CREATED:-0}" >> $GITHUB_OUTPUT
+          echo "prs_merged=${NUM_PRS_MERGED:-0}" >> $GITHUB_OUTPUT
+          echo "avg_first_response=${AVG_TIME_TO_FIRST_RESPONSE:-N/A}" >> $GITHUB_OUTPUT
+          echo "avg_time_to_close=${AVG_TIME_TO_CLOSE:-N/A}" >> $GITHUB_OUTPUT
+          echo "pr_avg_merge_time=${PR_AVG_TIME_TO_MERGE:-N/A}" >> $GITHUB_OUTPUT
 
       - name: Send to Discord
         uses: sarisia/actions-status-discord@v1
@@ -87,22 +78,19 @@ jobs:
           title: "📊 Weekly Metrics Report"
           description: |
             **${{ env.week_of }}**
-            *${{ env.date_range }}*
-
+            
             **🎯 Issues**
             • Created: ${{ steps.metrics.outputs.issues_created }}
             • Closed: ${{ steps.metrics.outputs.issues_closed }}
-            • Avg Response Time: ${{ steps.metrics.outputs.issue_avg_first_response }}
-            • Avg Time to Close: ${{ steps.metrics.outputs.issue_avg_time_to_close }}
-
+            
             **🔀 Pull Requests**
             • Created: ${{ steps.metrics.outputs.prs_created }}
             • Merged: ${{ steps.metrics.outputs.prs_merged }}
-            • Avg Response Time: ${{ steps.metrics.outputs.pr_avg_first_response }}
-            • Avg Time to Merge: ${{ steps.metrics.outputs.pr_avg_merge_time }}
-
-            **📈 Visual Analytics**
-            https://repobeats.axiom.co/api/embed/b439f28f0ab5bd7a2da19505355693cd2c55bfd4.svg
+            
+            **⏱️ Response Times**
+            • First Response: ${{ steps.metrics.outputs.avg_first_response }}
+            • Time to Close: ${{ steps.metrics.outputs.avg_time_to_close }}
+            • PR Merge Time: ${{ steps.metrics.outputs.pr_avg_merge_time }}
           color: 0x58AFFF
           username: Task Master Metrics Bot
           avatar_url: https://raw.githubusercontent.com/eyaltoledano/claude-task-master/main/images/logo.png

.gitignore

@@ -93,7 +93,4 @@ dev-debug.log
 apps/extension/.vscode-test/
 
 # apps/extension
-apps/extension/vsix-build/
-
-# turbo
-.turbo
+apps/extension/vsix-build/

.kiro/settings/mcp.json

@@ -2,7 +2,7 @@
 	"mcpServers": {
 		"task-master-ai": {
 			"command": "npx",
-			"args": ["-y", "task-master-ai"],
+			"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",

.manypkg.json

@@ -1,6 +0,0 @@
-{
-	"$schema": "https://unpkg.com/@manypkg/get-packages@1.1.3/schema.json",
-	"defaultBranch": "main",
-	"ignoredRules": ["ROOT_HAS_DEPENDENCIES", "INTERNAL_MISMATCH"],
-	"ignoredPackages": ["@tm/core", "@tm/cli", "@tm/build-config"]
-}

.nvmrc

@@ -1 +1 @@
-22
+22 

.taskmaster/CLAUDE.md

@@ -85,7 +85,7 @@ Task Master provides an MCP server that Claude Code can connect to. Configure in
   "mcpServers": {
     "task-master-ai": {
       "command": "npx",
-      "args": ["-y", "task-master-ai"],
+      "args": ["-y", "--package=task-master-ai", "task-master-ai"],
       "env": {
         "ANTHROPIC_API_KEY": "your_key_here",
         "PERPLEXITY_API_KEY": "your_key_here",

.taskmaster/config.json

@@ -2,8 +2,8 @@
 	"models": {
 		"main": {
 			"provider": "anthropic",
-			"modelId": "claude-sonnet-4-20250514",
-			"maxTokens": 64000,
+			"modelId": "claude-3-7-sonnet-20250219",
+			"maxTokens": 120000,
 			"temperature": 0.2
 		},
 		"research": {
@@ -14,8 +14,8 @@
 		},
 		"fallback": {
 			"provider": "anthropic",
-			"modelId": "claude-3-7-sonnet-20250219",
-			"maxTokens": 120000,
+			"modelId": "claude-3-5-sonnet-20241022",
+			"maxTokens": 8192,
 			"temperature": 0.2
 		}
 	},
@@ -29,15 +29,9 @@
 		"ollamaBaseURL": "http://localhost:11434/api",
 		"bedrockBaseURL": "https://bedrock.us-east-1.amazonaws.com",
 		"responseLanguage": "English",
-		"enableCodebaseAnalysis": true,
 		"userId": "1234567890",
 		"azureBaseURL": "https://your-endpoint.azure.com/",
 		"defaultTag": "master"
 	},
-	"claudeCode": {},
-	"grokCli": {
-		"timeout": 120000,
-		"workingDirectory": null,
-		"defaultModel": "grok-4-latest"
-	}
+	"claudeCode": {}
 }

.taskmaster/docs/prd-tm-start.txt

@@ -1,91 +0,0 @@
-<context>
-# Overview
-Add a new CLI command: `task-master start <task_id>` (alias: `tm start <task_id>`). This command hard-codes `claude-code` as the executor, fetches task details, builds a standardized prompt, runs claude-code, shows the result, checks for git changes, and auto-marks the task as done if successful.
-
-We follow the Commander class pattern, reuse task retrieval from `show` command flow. Extremely minimal for 1-hour hackathon timeline.
-
-# Core Features
-- `start` command (Commander class style) 
-- Hard-coded executor: `claude-code`
-- Standardized prompt designed for minimal changes following existing patterns
-- Shows claude-code output (no streaming)
-- Git status check for success detection
-- Auto-mark task done if successful
-
-# User Experience
-```
-task-master start 12
-```
-1) Fetches Task #12 details
-2) Builds standardized prompt with task context
-3) Runs claude-code with the prompt
-4) Shows output
-5) Checks git status for changes
-6) Auto-marks task done if changes detected
-</context>
-
-<PRD>
-# Technical Architecture
-
-- Command pattern:
-  - Create `apps/cli/src/commands/start.command.ts` modeled on [list.command.ts](mdc:apps/cli/src/commands/list.command.ts) and task lookup from [show.command.ts](mdc:apps/cli/src/commands/show.command.ts)
-
-- Task retrieval:
-  - Use `@tm/core` via `createTaskMasterCore` to get task by ID
-  - Extract: id, title, description, details
-
-- Executor (ultra-simple approach):
-  - Execute `claude "full prompt here"` command directly
-  - The prompt tells Claude to first run `tm show <task_id>` to get task details
-  - Then tells Claude to implement the code changes
-  - This opens Claude CLI interface naturally in the current terminal
-  - No subprocess management needed - just execute the command
-
-- Execution flow:
-  1) Validate `<task_id>` exists; exit with error if not
-  2) Build standardized prompt that includes instructions to run `tm show <task_id>`
-  3) Execute `claude "prompt"` command directly in terminal
-  4) Claude CLI opens, runs `tm show`, then implements changes
-  5) After Claude session ends, run `git status --porcelain` to detect changes
-  6) If changes detected, auto-run `task-master set-status --id=<task_id> --status=done`
-
-- Success criteria:
-  - Success = exit code 0 AND git shows modified/created files
-  - Print changed file paths; warn if no changes detected
-
-# Development Roadmap
-
-MVP (ship in ~1 hour):
-1) Implement `start.command.ts` (Commander class), parse `<task_id>`
-2) Validate task exists via tm-core 
-3) Build prompt that tells Claude to run `tm show <task_id>` then implement
-4) Execute `claude "prompt"` command, then check git status and auto-mark done
-
-# Risks and Mitigations
-- Executor availability: Error clearly if `claude-code` provider fails
-- False success: Git-change heuristic acceptable for hackathon MVP
-
-# Appendix
-
-**Standardized Prompt Template:**
-```
-You are an AI coding assistant with access to this repository's codebase.
-
-First, run this command to get the task details:
-tm show <task_id>
-
-Then implement the task with these requirements:
-- Make the SMALLEST number of code changes possible
-- Follow ALL existing patterns in the codebase (you have access to analyze the code)
-- Do NOT over-engineer the solution
-- Use existing files/functions/patterns wherever possible
-- When complete, print: COMPLETED: <brief summary of changes>
-
-Begin by running tm show <task_id> to understand what needs to be implemented.
-```
-
-**Key References:**
-- [list.command.ts](mdc:apps/cli/src/commands/list.command.ts) - Command structure
-- [show.command.ts](mdc:apps/cli/src/commands/show.command.ts) - Task validation
-- Node.js `child_process.exec()` - For executing `claude "prompt"` command
-</PRD>

.taskmaster/state.json

@@ -1,6 +1,6 @@
 {
 	"currentTag": "master",
-	"lastSwitched": "2025-09-12T22:25:27.535Z",
+	"lastSwitched": "2025-08-27T21:03:20.550Z",
 	"branchTagMapping": {
 		"v017-adds": "v017-adds",
 		"next": "next"

.taskmaster/tasks/task_001_tm-start.txt

@@ -1,34 +0,0 @@
-# Task ID: 1
-# Title: Create start command class structure
-# Status: pending
-# Dependencies: None
-# Priority: high
-# Description: Create the basic structure for the start command following the Commander class pattern
-# Details:
-Create a new file `apps/cli/src/commands/start.command.ts` based on the existing list.command.ts pattern. Implement the command class with proper command registration, description, and argument handling for the task_id parameter. The class should extend the base Command class and implement the required methods.
-
-Example structure:
-```typescript
-import { Command } from 'commander';
-import { BaseCommand } from './base.command';
-
-export class StartCommand extends BaseCommand {
-  public register(program: Command): void {
-    program
-      .command('start')
-      .alias('tm start')
-      .description('Start implementing a task using claude-code')
-      .argument('<task_id>', 'ID of the task to start')
-      .action(async (taskId: string) => {
-        await this.execute(taskId);
-      });
-  }
-
-  public async execute(taskId: string): Promise<void> {
-    // Implementation will be added in subsequent tasks
-  }
-}
-```
-
-# Test Strategy:
-Verify the command registers correctly by running the CLI with --help and checking that the start command appears with proper description and arguments. Test the basic structure by ensuring the command can be invoked without errors.

.taskmaster/tasks/task_002_tm-start.txt

@@ -1,26 +0,0 @@
-# Task ID: 2
-# Title: Register start command in CLI
-# Status: pending
-# Dependencies: 7
-# Priority: high
-# Description: Register the start command in the CLI application
-# Details:
-Update the CLI application to register the new start command. This involves importing the StartCommand class and adding it to the commands array in the CLI initialization.
-
-In `apps/cli/src/index.ts` or the appropriate file where commands are registered:
-
-```typescript
-import { StartCommand } from './commands/start.command';
-
-// Add StartCommand to the commands array
-const commands = [
-  // ... existing commands
-  new StartCommand(),
-];
-
-// Register all commands
-commands.forEach(command => command.register(program));
-```
-
-# Test Strategy:
-Verify the command is correctly registered by running the CLI with --help and checking that the start command appears in the list of available commands.

.taskmaster/tasks/task_003_tm-start.txt

@@ -1,32 +0,0 @@
-# Task ID: 3
-# Title: Create standardized prompt builder
-# Status: pending
-# Dependencies: 1
-# Priority: medium
-# Description: Implement a function to build the standardized prompt for claude-code based on the task details
-# Details:
-Create a function in the StartCommand class that builds the standardized prompt according to the template provided in the PRD. The prompt should include instructions for Claude to first run `tm show <task_id>` to get task details, and then implement the required changes.
-
-```typescript
-private buildPrompt(taskId: string): string {
-  return `You are an AI coding assistant with access to this repository's codebase.
-
-First, run this command to get the task details:
-tm show ${taskId}
-
-Then implement the task with these requirements:
-- Make the SMALLEST number of code changes possible
-- Follow ALL existing patterns in the codebase (you have access to analyze the code)
-- Do NOT over-engineer the solution
-- Use existing files/functions/patterns wherever possible
-- When complete, print: COMPLETED: <brief summary of changes>
-
-Begin by running tm show ${taskId} to understand what needs to be implemented.`;
-}
-```
-<info added on 2025-09-12T02:40:01.812Z>
-The prompt builder function will handle task context retrieval by instructing Claude to use the task-master show command. This approach ensures Claude has access to all necessary task details before implementation begins. The command syntax "tm show ${taskId}" embedded in the prompt will direct Claude to first gather the complete task context, including description, requirements, and any existing implementation details, before proceeding with code changes.
-</info added on 2025-09-12T02:40:01.812Z>
-
-# Test Strategy:
-Verify the prompt is correctly formatted by calling the function with a sample task ID and checking that the output matches the expected template with the task ID properly inserted.

.taskmaster/tasks/task_004_tm-start.txt

@@ -1,36 +0,0 @@
-# Task ID: 4
-# Title: Implement claude-code executor
-# Status: pending
-# Dependencies: 3
-# Priority: high
-# Description: Add functionality to execute the claude-code command with the built prompt
-# Details:
-Implement the functionality to execute the claude command with the built prompt. This should use Node.js child_process.exec() to run the command directly in the terminal.
-
-```typescript
-import { exec } from 'child_process';
-
-// Inside execute method, after task validation
-private async executeClaude(prompt: string): Promise<void> {
-  console.log('Starting claude-code to implement the task...');
-  
-  try {
-    // Execute claude with the prompt
-    const claudeCommand = `claude "${prompt.replace(/"/g, '\\"')}"`;
-    
-    // Use execSync to wait for the command to complete
-    const { execSync } = require('child_process');
-    execSync(claudeCommand, { stdio: 'inherit' });
-    
-    console.log('Claude session completed.');
-  } catch (error) {
-    console.error('Error executing claude-code:', error.message);
-    process.exit(1);
-  }
-}
-```
-
-Then call this method from the execute method after building the prompt.
-
-# Test Strategy:
-Test by running the command with a valid task ID and verifying that the claude command is executed with the correct prompt. Check that the command handles errors appropriately if claude-code is not available.

.taskmaster/tasks/task_007_tm-start.txt

@@ -1,49 +0,0 @@
-# Task ID: 7
-# Title: Integrate execution flow in start command
-# Status: pending
-# Dependencies: 3, 4
-# Priority: high
-# Description: Connect all the components to implement the complete execution flow for the start command
-# Details:
-Update the execute method in the StartCommand class to integrate all the components and implement the complete execution flow as described in the PRD:
-1. Validate task exists
-2. Build standardized prompt
-3. Execute claude-code
-4. Check git status for changes
-5. Auto-mark task as done if changes detected
-
-```typescript
-public async execute(taskId: string): Promise<void> {
-  // Validate task exists
-  const core = await createTaskMasterCore();
-  const task = await core.tasks.getById(parseInt(taskId, 10));
-  
-  if (!task) {
-    console.error(`Task with ID ${taskId} not found`);
-    process.exit(1);
-  }
-  
-  // Build prompt
-  const prompt = this.buildPrompt(taskId);
-  
-  // Execute claude-code
-  await this.executeClaude(prompt);
-  
-  // Check git status
-  const changedFiles = await this.checkGitChanges();
-  
-  if (changedFiles.length > 0) {
-    console.log('\nChanges detected in the following files:');
-    changedFiles.forEach(file => console.log(`- ${file}`));
-    
-    // Auto-mark task as done
-    await this.markTaskAsDone(taskId);
-    console.log(`\nTask ${taskId} completed successfully and marked as done.`);
-  } else {
-    console.warn('\nNo changes detected after claude-code execution. Task not marked as done.');
-  }
-}
-```
-
-# Test Strategy:
-Test the complete execution flow by running the start command with a valid task ID and verifying that all steps are executed correctly. Test with both scenarios: when changes are detected and when no changes are detected.

.taskmaster/templates/example_prd_rpg.txt

@@ -1,511 +0,0 @@
-<rpg-method>
-# Repository Planning Graph (RPG) Method - PRD Template
-
-This template teaches you (AI or human) how to create structured, dependency-aware PRDs using the RPG methodology from Microsoft Research. The key insight: separate WHAT (functional) from HOW (structural), then connect them with explicit dependencies.
-
-## Core Principles
-
-1. **Dual-Semantics**: Think functional (capabilities) AND structural (code organization) separately, then map them
-2. **Explicit Dependencies**: Never assume - always state what depends on what
-3. **Topological Order**: Build foundation first, then layers on top
-4. **Progressive Refinement**: Start broad, refine iteratively
-
-## How to Use This Template
-
-- Follow the instructions in each `<instruction>` block
-- Look at `<example>` blocks to see good vs bad patterns
-- Fill in the content sections with your project details
-- The AI reading this will learn the RPG method by following along
-- Task Master will parse the resulting PRD into dependency-aware tasks
-
-## Recommended Tools for Creating PRDs
-
-When using this template to **create** a PRD (not parse it), use **code-context-aware AI assistants** for best results:
-
-**Why?** The AI needs to understand your existing codebase to make good architectural decisions about modules, dependencies, and integration points.
-
-**Recommended tools:**
-- **Claude Code** (claude-code CLI) - Best for structured reasoning and large contexts
-- **Cursor/Windsurf** - IDE integration with full codebase context
-- **Gemini CLI** (gemini-cli) - Massive context window for large codebases
-- **Codex/Grok CLI** - Strong code generation with context awareness
-
-**Note:** Once your PRD is created, `task-master parse-prd` works with any configured AI model - it just needs to read the PRD text itself, not your codebase.
-</rpg-method>
-
----
-
-<overview>
-<instruction>
-Start with the problem, not the solution. Be specific about:
-- What pain point exists?
-- Who experiences it?
-- Why existing solutions don't work?
-- What success looks like (measurable outcomes)?
-
-Keep this section focused - don't jump into implementation details yet.
-</instruction>
-
-## Problem Statement
-[Describe the core problem. Be concrete about user pain points.]
-
-## Target Users
-[Define personas, their workflows, and what they're trying to achieve.]
-
-## Success Metrics
-[Quantifiable outcomes. Examples: "80% task completion via autopilot", "< 5% manual intervention rate"]
-
-</overview>
-
----
-
-<functional-decomposition>
-<instruction>
-Now think about CAPABILITIES (what the system DOES), not code structure yet.
-
-Step 1: Identify high-level capability domains
-- Think: "What major things does this system do?"
-- Examples: Data Management, Core Processing, Presentation Layer
-
-Step 2: For each capability, enumerate specific features
-- Use explore-exploit strategy:
-  * Exploit: What features are REQUIRED for core value?
-  * Explore: What features make this domain COMPLETE?
-
-Step 3: For each feature, define:
-- Description: What it does in one sentence
-- Inputs: What data/context it needs
-- Outputs: What it produces/returns
-- Behavior: Key logic or transformations
-
-<example type="good">
-Capability: Data Validation
-  Feature: Schema validation
-    - Description: Validate JSON payloads against defined schemas
-    - Inputs: JSON object, schema definition
-    - Outputs: Validation result (pass/fail) + error details
-    - Behavior: Iterate fields, check types, enforce constraints
-
-  Feature: Business rule validation
-    - Description: Apply domain-specific validation rules
-    - Inputs: Validated data object, rule set
-    - Outputs: Boolean + list of violated rules
-    - Behavior: Execute rules sequentially, short-circuit on failure
-</example>
-
-<example type="bad">
-Capability: validation.js
-  (Problem: This is a FILE, not a CAPABILITY. Mixing structure into functional thinking.)
-
-Capability: Validation
-  Feature: Make sure data is good
-  (Problem: Too vague. No inputs/outputs. Not actionable.)
-</example>
-</instruction>
-
-## Capability Tree
-
-### Capability: [Name]
-[Brief description of what this capability domain covers]
-
-#### Feature: [Name]
-- **Description**: [One sentence]
-- **Inputs**: [What it needs]
-- **Outputs**: [What it produces]
-- **Behavior**: [Key logic]
-
-#### Feature: [Name]
-- **Description**:
-- **Inputs**:
-- **Outputs**:
-- **Behavior**:
-
-### Capability: [Name]
-...
-
-</functional-decomposition>
-
----
-
-<structural-decomposition>
-<instruction>
-NOW think about code organization. Map capabilities to actual file/folder structure.
-
-Rules:
-1. Each capability maps to a module (folder or file)
-2. Features within a capability map to functions/classes
-3. Use clear module boundaries - each module has ONE responsibility
-4. Define what each module exports (public interface)
-
-The goal: Create a clear mapping between "what it does" (functional) and "where it lives" (structural).
-
-<example type="good">
-Capability: Data Validation
-  → Maps to: src/validation/
-    ├── schema-validator.js      (Schema validation feature)
-    ├── rule-validator.js         (Business rule validation feature)
-    └── index.js                  (Public exports)
-
-Exports:
-  - validateSchema(data, schema)
-  - validateRules(data, rules)
-</example>
-
-<example type="bad">
-Capability: Data Validation
-  → Maps to: src/utils.js
-  (Problem: "utils" is not a clear module boundary. Where do I find validation logic?)
-
-Capability: Data Validation
-  → Maps to: src/validation/everything.js
-  (Problem: One giant file. Features should map to separate files for maintainability.)
-</example>
-</instruction>
-
-## Repository Structure
-
-```
-project-root/
-├── src/
-│   ├── [module-name]/       # Maps to: [Capability Name]
-│   │   ├── [file].js        # Maps to: [Feature Name]
-│   │   └── index.js         # Public exports
-│   └── [module-name]/
-├── tests/
-└── docs/
-```
-
-## Module Definitions
-
-### Module: [Name]
-- **Maps to capability**: [Capability from functional decomposition]
-- **Responsibility**: [Single clear purpose]
-- **File structure**:
-  ```
-  module-name/
-  ├── feature1.js
-  ├── feature2.js
-  └── index.js
-  ```
-- **Exports**:
-  - `functionName()` - [what it does]
-  - `ClassName` - [what it does]
-
-</structural-decomposition>
-
----
-
-<dependency-graph>
-<instruction>
-This is THE CRITICAL SECTION for Task Master parsing.
-
-Define explicit dependencies between modules. This creates the topological order for task execution.
-
-Rules:
-1. List modules in dependency order (foundation first)
-2. For each module, state what it depends on
-3. Foundation modules should have NO dependencies
-4. Every non-foundation module should depend on at least one other module
-5. Think: "What must EXIST before I can build this module?"
-
-<example type="good">
-Foundation Layer (no dependencies):
-  - error-handling: No dependencies
-  - config-manager: No dependencies
-  - base-types: No dependencies
-
-Data Layer:
-  - schema-validator: Depends on [base-types, error-handling]
-  - data-ingestion: Depends on [schema-validator, config-manager]
-
-Core Layer:
-  - algorithm-engine: Depends on [base-types, error-handling]
-  - pipeline-orchestrator: Depends on [algorithm-engine, data-ingestion]
-</example>
-
-<example type="bad">
-- validation: Depends on API
-- API: Depends on validation
-(Problem: Circular dependency. This will cause build/runtime issues.)
-
-- user-auth: Depends on everything
-(Problem: Too many dependencies. Should be more focused.)
-</example>
-</instruction>
-
-## Dependency Chain
-
-### Foundation Layer (Phase 0)
-No dependencies - these are built first.
-
-- **[Module Name]**: [What it provides]
-- **[Module Name]**: [What it provides]
-
-### [Layer Name] (Phase 1)
-- **[Module Name]**: Depends on [[module-from-phase-0], [module-from-phase-0]]
-- **[Module Name]**: Depends on [[module-from-phase-0]]
-
-### [Layer Name] (Phase 2)
-- **[Module Name]**: Depends on [[module-from-phase-1], [module-from-foundation]]
-
-[Continue building up layers...]
-
-</dependency-graph>
-
----
-
-<implementation-roadmap>
-<instruction>
-Turn the dependency graph into concrete development phases.
-
-Each phase should:
-1. Have clear entry criteria (what must exist before starting)
-2. Contain tasks that can be parallelized (no inter-dependencies within phase)
-3. Have clear exit criteria (how do we know phase is complete?)
-4. Build toward something USABLE (not just infrastructure)
-
-Phase ordering follows topological sort of dependency graph.
-
-<example type="good">
-Phase 0: Foundation
-  Entry: Clean repository
-  Tasks:
-    - Implement error handling utilities
-    - Create base type definitions
-    - Setup configuration system
-  Exit: Other modules can import foundation without errors
-
-Phase 1: Data Layer
-  Entry: Phase 0 complete
-  Tasks:
-    - Implement schema validator (uses: base types, error handling)
-    - Build data ingestion pipeline (uses: validator, config)
-  Exit: End-to-end data flow from input to validated output
-</example>
-
-<example type="bad">
-Phase 1: Build Everything
-  Tasks:
-    - API
-    - Database
-    - UI
-    - Tests
-  (Problem: No clear focus. Too broad. Dependencies not considered.)
-</example>
-</instruction>
-
-## Development Phases
-
-### Phase 0: [Foundation Name]
-**Goal**: [What foundational capability this establishes]
-
-**Entry Criteria**: [What must be true before starting]
-
-**Tasks**:
-- [ ] [Task name] (depends on: [none or list])
-  - Acceptance criteria: [How we know it's done]
-  - Test strategy: [What tests prove it works]
-
-- [ ] [Task name] (depends on: [none or list])
-
-**Exit Criteria**: [Observable outcome that proves phase complete]
-
-**Delivers**: [What can users/developers do after this phase?]
-
----
-
-### Phase 1: [Layer Name]
-**Goal**:
-
-**Entry Criteria**: Phase 0 complete
-
-**Tasks**:
-- [ ] [Task name] (depends on: [[tasks-from-phase-0]])
-- [ ] [Task name] (depends on: [[tasks-from-phase-0]])
-
-**Exit Criteria**:
-
-**Delivers**:
-
----
-
-[Continue with more phases...]
-
-</implementation-roadmap>
-
----
-
-<test-strategy>
-<instruction>
-Define how testing will be integrated throughout development (TDD approach).
-
-Specify:
-1. Test pyramid ratios (unit vs integration vs e2e)
-2. Coverage requirements
-3. Critical test scenarios
-4. Test generation guidelines for Surgical Test Generator
-
-This section guides the AI when generating tests during the RED phase of TDD.
-
-<example type="good">
-Critical Test Scenarios for Data Validation module:
-  - Happy path: Valid data passes all checks
-  - Edge cases: Empty strings, null values, boundary numbers
-  - Error cases: Invalid types, missing required fields
-  - Integration: Validator works with ingestion pipeline
-</example>
-</instruction>
-
-## Test Pyramid
-
-```
-        /\
-       /E2E\       ← [X]% (End-to-end, slow, comprehensive)
-      /------\
-     /Integration\ ← [Y]% (Module interactions)
-    /------------\
-   /  Unit Tests  \ ← [Z]% (Fast, isolated, deterministic)
-  /----------------\
-```
-
-## Coverage Requirements
-- Line coverage: [X]% minimum
-- Branch coverage: [X]% minimum
-- Function coverage: [X]% minimum
-- Statement coverage: [X]% minimum
-
-## Critical Test Scenarios
-
-### [Module/Feature Name]
-**Happy path**:
-- [Scenario description]
-- Expected: [What should happen]
-
-**Edge cases**:
-- [Scenario description]
-- Expected: [What should happen]
-
-**Error cases**:
-- [Scenario description]
-- Expected: [How system handles failure]
-
-**Integration points**:
-- [What interactions to test]
-- Expected: [End-to-end behavior]
-
-## Test Generation Guidelines
-[Specific instructions for Surgical Test Generator about what to focus on, what patterns to follow, project-specific test conventions]
-
-</test-strategy>
-
----
-
-<architecture>
-<instruction>
-Describe technical architecture, data models, and key design decisions.
-
-Keep this section AFTER functional/structural decomposition - implementation details come after understanding structure.
-</instruction>
-
-## System Components
-[Major architectural pieces and their responsibilities]
-
-## Data Models
-[Core data structures, schemas, database design]
-
-## Technology Stack
-[Languages, frameworks, key libraries]
-
-**Decision: [Technology/Pattern]**
-- **Rationale**: [Why chosen]
-- **Trade-offs**: [What we're giving up]
-- **Alternatives considered**: [What else we looked at]
-
-</architecture>
-
----
-
-<risks>
-<instruction>
-Identify risks that could derail development and how to mitigate them.
-
-Categories:
-- Technical risks (complexity, unknowns)
-- Dependency risks (blocking issues)
-- Scope risks (creep, underestimation)
-</instruction>
-
-## Technical Risks
-**Risk**: [Description]
-- **Impact**: [High/Medium/Low - effect on project]
-- **Likelihood**: [High/Medium/Low]
-- **Mitigation**: [How to address]
-- **Fallback**: [Plan B if mitigation fails]
-
-## Dependency Risks
-[External dependencies, blocking issues]
-
-## Scope Risks
-[Scope creep, underestimation, unclear requirements]
-
-</risks>
-
----
-
-<appendix>
-## References
-[Papers, documentation, similar systems]
-
-## Glossary
-[Domain-specific terms]
-
-## Open Questions
-[Things to resolve during development]
-</appendix>
-
----
-
-<task-master-integration>
-# How Task Master Uses This PRD
-
-When you run `task-master parse-prd <file>.txt`, the parser:
-
-1. **Extracts capabilities** → Main tasks
-   - Each `### Capability:` becomes a top-level task
-
-2. **Extracts features** → Subtasks
-   - Each `#### Feature:` becomes a subtask under its capability
-
-3. **Parses dependencies** → Task dependencies
-   - `Depends on: [X, Y]` sets task.dependencies = ["X", "Y"]
-
-4. **Orders by phases** → Task priorities
-   - Phase 0 tasks = highest priority
-   - Phase N tasks = lower priority, properly sequenced
-
-5. **Uses test strategy** → Test generation context
-   - Feeds test scenarios to Surgical Test Generator during implementation
-
-**Result**: A dependency-aware task graph that can be executed in topological order.
-
-## Why RPG Structure Matters
-
-Traditional flat PRDs lead to:
-- ❌ Unclear task dependencies
-- ❌ Arbitrary task ordering
-- ❌ Circular dependencies discovered late
-- ❌ Poorly scoped tasks
-
-RPG-structured PRDs provide:
-- ✅ Explicit dependency chains
-- ✅ Topological execution order
-- ✅ Clear module boundaries
-- ✅ Validated task graph before implementation
-
-## Tips for Best Results
-
-1. **Spend time on dependency graph** - This is the most valuable section for Task Master
-2. **Keep features atomic** - Each feature should be independently testable
-3. **Progressive refinement** - Start broad, use `task-master expand` to break down complex tasks
-4. **Use research mode** - `task-master parse-prd --research` leverages AI for better task generation
-</task-master-integration>

CHANGELOG.md

@@ -1,500 +1,5 @@
 # task-master-ai
 
-## 0.29.0
-
-### Minor Changes
-
-- [#1286](https://github.com/eyaltoledano/claude-task-master/pull/1286) [`f12a16d`](https://github.com/eyaltoledano/claude-task-master/commit/f12a16d09649f62148515f11f616157c7d0bd2d5) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add changelog highlights to auto-update notifications
-
-  When the CLI auto-updates to a new version, it now displays a "What's New" section.
-
-- [#1293](https://github.com/eyaltoledano/claude-task-master/pull/1293) [`3010b90`](https://github.com/eyaltoledano/claude-task-master/commit/3010b90d98f3a7d8636caa92fc33d6ee69d4bed0) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add Claude Code plugin with marketplace distribution
-
-  This release introduces official Claude Code plugin support, marking the evolution from legacy `.claude` directory copying to a modern plugin-based architecture.
-
-  ## 🎉 New: Claude Code Plugin
-
-  Task Master AI commands and agents are now distributed as a proper Claude Code plugin:
-  - **49 slash commands** with clean naming (`/taskmaster:command-name`)
-  - **3 specialized AI agents** (task-orchestrator, task-executor, task-checker)
-  - **MCP server integration** for deep Claude Code integration
-
-  **Installation:**
-
-  ```bash
-  /plugin marketplace add eyaltoledano/claude-task-master
-  /plugin install taskmaster@taskmaster
-  ```
-
-  ### The `rules add claude` command no longer copies commands and agents to `.claude/commands/` and `.claude/agents/`. Instead, it now
-  - Shows plugin installation instructions
-  - Only manages CLAUDE.md imports for agent instructions
-  - Directs users to install the official plugin
-
-  **Migration for Existing Users:**
-
-  If you previously used `rules add claude`:
-  1. The old commands in `.claude/commands/` will continue to work but won't receive updates
-  2. Install the plugin for the latest features: `/plugin install taskmaster@taskmaster`
-  3. remove old `.claude/commands/` and `.claude/agents/` directories
-
-  **Why This Change?**
-
-  Claude Code plugins provide:
-  - ✅ Automatic updates when we release new features
-  - ✅ Better command organization and naming
-  - ✅ Seamless integration with Claude Code
-  - ✅ No manual file copying or management
-
-  The plugin system is the future of Task Master AI integration with Claude Code!
-
-- [#1285](https://github.com/eyaltoledano/claude-task-master/pull/1285) [`2a910a4`](https://github.com/eyaltoledano/claude-task-master/commit/2a910a40bac375f9f61d797bf55597303d556b48) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add RPG (Repository Planning Graph) method template for structured PRD creation. The new `example_prd_rpg.txt` template teaches AI agents and developers the RPG methodology through embedded instructions, inline good/bad examples, and XML-style tags for structure. This template enables creation of dependency-aware PRDs that automatically generate topologically-ordered task graphs when parsed with Task Master.
-
-  Key features:
-  - Method-as-template: teaches RPG principles (dual-semantics, explicit dependencies, topological order) while being used
-  - Inline instructions at decision points guide AI through each section
-  - Good/bad examples for immediate pattern matching
-  - Flexible plain-text format with XML-style tags for parseability
-  - Critical dependency-graph section ensures correct task ordering
-  - Automatic inclusion during `task-master init`
-  - Comprehensive documentation at [docs.task-master.dev/capabilities/rpg-method](https://docs.task-master.dev/capabilities/rpg-method)
-  - Tool recommendations for code-context-aware PRD creation (Claude Code, Cursor, Gemini CLI, Codex/Grok)
-
-  The RPG template complements the existing `example_prd.txt` and provides a more structured approach for complex projects requiring clear module boundaries and dependency chains.
-
-- [#1287](https://github.com/eyaltoledano/claude-task-master/pull/1287) [`90e6bdc`](https://github.com/eyaltoledano/claude-task-master/commit/90e6bdcf1c59f65ad27fcdfe3b13b9dca7e77654) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Enhance `expand_all` to intelligently use complexity analysis recommendations when expanding tasks.
-
-  The expand-all operation now automatically leverages recommendations from `analyze-complexity` to determine optimal subtask counts for each task, resulting in more accurate and context-aware task breakdowns.
-
-  Key improvements:
-  - Automatic integration with complexity analysis reports
-  - Tag-aware complexity report path resolution
-  - Intelligent subtask count determination based on task complexity
-  - Falls back to defaults when complexity analysis is unavailable
-  - Enhanced logging for better visibility into expansion decisions
-
-  When you run `task-master expand --all` after `task-master analyze-complexity`, Task Master now uses the recommended subtask counts from the complexity analysis instead of applying uniform defaults, ensuring each task is broken down according to its actual complexity.
-
-### Patch Changes
-
-- [#1191](https://github.com/eyaltoledano/claude-task-master/pull/1191) [`aaf903f`](https://github.com/eyaltoledano/claude-task-master/commit/aaf903ff2f606c779a22e9a4b240ab57b3683815) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix cross-level task dependencies not being saved
-
-  Fixes an issue where adding dependencies between subtasks and top-level tasks (e.g., `task-master add-dependency --id=2.2 --depends-on=11`) would report success but fail to persist the changes. Dependencies can now be created in both directions between any task levels.
-
-- [#1299](https://github.com/eyaltoledano/claude-task-master/pull/1299) [`4c1ef2c`](https://github.com/eyaltoledano/claude-task-master/commit/4c1ef2ca94411c53bcd2a78ec710b06c500236dd) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Improve refresh token when authenticating
-
-## 0.29.0-rc.1
-
-### Patch Changes
-
-- [#1299](https://github.com/eyaltoledano/claude-task-master/pull/1299) [`a6c5152`](https://github.com/eyaltoledano/claude-task-master/commit/a6c5152f20edd8717cf1aea34e7c178b1261aa99) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Improve refresh token when authenticating
-
-## 0.29.0-rc.0
-
-### Minor Changes
-
-- [#1286](https://github.com/eyaltoledano/claude-task-master/pull/1286) [`f12a16d`](https://github.com/eyaltoledano/claude-task-master/commit/f12a16d09649f62148515f11f616157c7d0bd2d5) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add changelog highlights to auto-update notifications
-
-  When the CLI auto-updates to a new version, it now displays a "What's New" section.
-
-- [#1293](https://github.com/eyaltoledano/claude-task-master/pull/1293) [`3010b90`](https://github.com/eyaltoledano/claude-task-master/commit/3010b90d98f3a7d8636caa92fc33d6ee69d4bed0) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add Claude Code plugin with marketplace distribution
-
-  This release introduces official Claude Code plugin support, marking the evolution from legacy `.claude` directory copying to a modern plugin-based architecture.
-
-  ## 🎉 New: Claude Code Plugin
-
-  Task Master AI commands and agents are now distributed as a proper Claude Code plugin:
-  - **49 slash commands** with clean naming (`/task-master-ai:command-name`)
-  - **3 specialized AI agents** (task-orchestrator, task-executor, task-checker)
-  - **MCP server integration** for deep Claude Code integration
-
-  **Installation:**
-
-  ```bash
-  /plugin marketplace add eyaltoledano/claude-task-master
-  /plugin install taskmaster@taskmaster
-  ```
-
-  ### The `rules add claude` command no longer copies commands and agents to `.claude/commands/` and `.claude/agents/`. Instead, it now
-  - Shows plugin installation instructions
-  - Only manages CLAUDE.md imports for agent instructions
-  - Directs users to install the official plugin
-
-  **Migration for Existing Users:**
-
-  If you previously used `rules add claude`:
-  1. The old commands in `.claude/commands/` will continue to work but won't receive updates
-  2. Install the plugin for the latest features: `/plugin install taskmaster@taskmaster`
-  3. remove old `.claude/commands/` and `.claude/agents/` directories
-
-  **Why This Change?**
-
-  Claude Code plugins provide:
-  - ✅ Automatic updates when we release new features
-  - ✅ Better command organization and naming
-  - ✅ Seamless integration with Claude Code
-  - ✅ No manual file copying or management
-
-  The plugin system is the future of Task Master AI integration with Claude Code!
-
-- [#1285](https://github.com/eyaltoledano/claude-task-master/pull/1285) [`2a910a4`](https://github.com/eyaltoledano/claude-task-master/commit/2a910a40bac375f9f61d797bf55597303d556b48) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add RPG (Repository Planning Graph) method template for structured PRD creation. The new `example_prd_rpg.txt` template teaches AI agents and developers the RPG methodology through embedded instructions, inline good/bad examples, and XML-style tags for structure. This template enables creation of dependency-aware PRDs that automatically generate topologically-ordered task graphs when parsed with Task Master.
-
-  Key features:
-  - Method-as-template: teaches RPG principles (dual-semantics, explicit dependencies, topological order) while being used
-  - Inline instructions at decision points guide AI through each section
-  - Good/bad examples for immediate pattern matching
-  - Flexible plain-text format with XML-style tags for parseability
-  - Critical dependency-graph section ensures correct task ordering
-  - Automatic inclusion during `task-master init`
-  - Comprehensive documentation at [docs.task-master.dev/capabilities/rpg-method](https://docs.task-master.dev/capabilities/rpg-method)
-  - Tool recommendations for code-context-aware PRD creation (Claude Code, Cursor, Gemini CLI, Codex/Grok)
-
-  The RPG template complements the existing `example_prd.txt` and provides a more structured approach for complex projects requiring clear module boundaries and dependency chains.
-
-- [#1287](https://github.com/eyaltoledano/claude-task-master/pull/1287) [`90e6bdc`](https://github.com/eyaltoledano/claude-task-master/commit/90e6bdcf1c59f65ad27fcdfe3b13b9dca7e77654) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Enhance `expand_all` to intelligently use complexity analysis recommendations when expanding tasks.
-
-  The expand-all operation now automatically leverages recommendations from `analyze-complexity` to determine optimal subtask counts for each task, resulting in more accurate and context-aware task breakdowns.
-
-  Key improvements:
-  - Automatic integration with complexity analysis reports
-  - Tag-aware complexity report path resolution
-  - Intelligent subtask count determination based on task complexity
-  - Falls back to defaults when complexity analysis is unavailable
-  - Enhanced logging for better visibility into expansion decisions
-
-  When you run `task-master expand --all` after `task-master analyze-complexity`, Task Master now uses the recommended subtask counts from the complexity analysis instead of applying uniform defaults, ensuring each task is broken down according to its actual complexity.
-
-### Patch Changes
-
-- [#1191](https://github.com/eyaltoledano/claude-task-master/pull/1191) [`aaf903f`](https://github.com/eyaltoledano/claude-task-master/commit/aaf903ff2f606c779a22e9a4b240ab57b3683815) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix cross-level task dependencies not being saved
-
-  Fixes an issue where adding dependencies between subtasks and top-level tasks (e.g., `task-master add-dependency --id=2.2 --depends-on=11`) would report success but fail to persist the changes. Dependencies can now be created in both directions between any task levels.
-
-## 0.28.0
-
-### Minor Changes
-
-- [#1273](https://github.com/eyaltoledano/claude-task-master/pull/1273) [`b43b7ce`](https://github.com/eyaltoledano/claude-task-master/commit/b43b7ce201625eee956fb2f8cd332f238bb78c21) Thanks [@ben-vargas](https://github.com/ben-vargas)! - Add Codex CLI provider with OAuth authentication
-  - Added codex-cli provider for GPT-5 and GPT-5-Codex models (272K input / 128K output)
-  - OAuth-first authentication via `codex login` - no API key required
-  - Optional OPENAI_CODEX_API_KEY support
-  - Codebase analysis capabilities automatically enabled
-  - Command-specific settings and approval/sandbox modes
-
-- [#1215](https://github.com/eyaltoledano/claude-task-master/pull/1215) [`0079b7d`](https://github.com/eyaltoledano/claude-task-master/commit/0079b7defdad550811f704c470fdd01955d91d4d) Thanks [@joedanz](https://github.com/joedanz)! - Add Cursor IDE custom slash command support
-
-  Expose Task Master commands as Cursor slash commands by copying assets/claude/commands to .cursor/commands on profile add and cleaning up on remove.
-
-- [#1246](https://github.com/eyaltoledano/claude-task-master/pull/1246) [`18aa416`](https://github.com/eyaltoledano/claude-task-master/commit/18aa416035f44345bde1c7321490345733a5d042) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Added api keys page on docs website: docs.task-master.dev/getting-started/api-keys
-
-- [#1246](https://github.com/eyaltoledano/claude-task-master/pull/1246) [`18aa416`](https://github.com/eyaltoledano/claude-task-master/commit/18aa416035f44345bde1c7321490345733a5d042) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Move to AI SDK v5:
-  - Works better with claude-code and gemini-cli as ai providers
-  - Improved openai model family compatibility
-  - Migrate ollama provider to v2
-  - Closes #1223, #1013, #1161, #1174
-
-- [#1262](https://github.com/eyaltoledano/claude-task-master/pull/1262) [`738ec51`](https://github.com/eyaltoledano/claude-task-master/commit/738ec51c049a295a12839b2dfddaf05e23b8fede) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Migrate AI services to use generateObject for structured data generation
-
-  This update migrates all AI service calls from generateText to generateObject, ensuring more reliable and structured responses across all commands.
-
-  ### Key Changes:
-  - **Unified AI Service**: Replaced separate generateText implementations with a single generateObjectService that handles structured data generation
-  - **JSON Mode Support**: Added proper JSON mode configuration for providers that support it (OpenAI, Anthropic, Google, Groq)
-  - **Schema Validation**: Integrated Zod schemas for all AI-generated content with automatic validation
-  - **Provider Compatibility**: Maintained compatibility with all existing providers while leveraging their native structured output capabilities
-  - **Improved Reliability**: Structured output generation reduces parsing errors and ensures consistent data formats
-
-  ### Technical Improvements:
-  - Centralized provider configuration in `ai-providers-unified.js`
-  - Added `generateObject` support detection for each provider
-  - Implemented proper error handling for schema validation failures
-  - Maintained backward compatibility with existing prompt structures
-
-  ### Bug Fixes:
-  - Fixed subtask ID numbering issue where AI was generating inconsistent IDs (101-105, 601-603) instead of sequential numbering (1, 2, 3...)
-  - Enhanced prompt instructions to enforce proper ID generation patterns
-  - Ensured subtasks display correctly as X.1, X.2, X.3 format
-
-  This migration improves the reliability and consistency of AI-generated content throughout the Task Master application.
-
-- [#1112](https://github.com/eyaltoledano/claude-task-master/pull/1112) [`d67b81d`](https://github.com/eyaltoledano/claude-task-master/commit/d67b81d25ddd927fabb6f5deb368e8993519c541) Thanks [@olssonsten](https://github.com/olssonsten)! - Enhanced Roo Code profile with MCP timeout configuration for improved reliability during long-running AI operations. The Roo profile now automatically configures a 300-second timeout for MCP server operations, preventing timeouts during complex tasks like `parse-prd`, `expand-all`, `analyze-complexity`, and `research` operations. This change also replaces static MCP configuration files with programmatic generation for better maintainability.
-
-  **What's New:**
-  - 300-second timeout for MCP operations (up from default 60 seconds)
-  - Programmatic MCP configuration generation (replaces static asset files)
-  - Enhanced reliability for AI-powered operations
-  - Consistent with other AI coding assistant profiles
-
-  **Migration:** No user action required - existing Roo Code installations will automatically receive the enhanced MCP configuration on next initialization.
-
-- [#1246](https://github.com/eyaltoledano/claude-task-master/pull/1246) [`986ac11`](https://github.com/eyaltoledano/claude-task-master/commit/986ac117aee00bcd3e6830a0f76e1ad6d10e0bca) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Upgrade grok-cli ai provider to ai sdk v5
-
-### Patch Changes
-
-- [#1235](https://github.com/eyaltoledano/claude-task-master/pull/1235) [`aaacc3d`](https://github.com/eyaltoledano/claude-task-master/commit/aaacc3dae36247b4de72b2d2697f49e5df6d01e3) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Improve `analyze-complexity` cli docs and `--research` flag documentation
-
-- [#1251](https://github.com/eyaltoledano/claude-task-master/pull/1251) [`0b2c696`](https://github.com/eyaltoledano/claude-task-master/commit/0b2c6967c4605c33a100cff16f6ce8ff09ad06f0) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Change parent task back to "pending" when all subtasks are in "pending" state
-
-- [#1274](https://github.com/eyaltoledano/claude-task-master/pull/1274) [`4f984f8`](https://github.com/eyaltoledano/claude-task-master/commit/4f984f8a6965da9f9c7edd60ddfd6560ac022917) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Do a quick fix on build
-
-- [#1277](https://github.com/eyaltoledano/claude-task-master/pull/1277) [`7b5a7c4`](https://github.com/eyaltoledano/claude-task-master/commit/7b5a7c4495a68b782f7407fc5d0e0d3ae81f42f5) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix MCP connection errors caused by deprecated generateTaskFiles calls. Resolves "Cannot read properties of null (reading 'toString')" errors when using MCP tools for task management operations.
-
-- [#1276](https://github.com/eyaltoledano/claude-task-master/pull/1276) [`caee040`](https://github.com/eyaltoledano/claude-task-master/commit/caee040907f856d31a660171c9e6d966f23c632e) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix MCP server error when file parameter not provided - now properly constructs default tasks.json path instead of failing with 'tasksJsonPath is required' error.
-
-- [#1172](https://github.com/eyaltoledano/claude-task-master/pull/1172) [`b5fe723`](https://github.com/eyaltoledano/claude-task-master/commit/b5fe723f8ead928e9f2dbde13b833ee70ac3382d) Thanks [@jujax](https://github.com/jujax)! - Fix Claude Code settings validation for pathToClaudeCodeExecutable
-
-- [#1192](https://github.com/eyaltoledano/claude-task-master/pull/1192) [`2b69936`](https://github.com/eyaltoledano/claude-task-master/commit/2b69936ee7b34346d6de5175af20e077359e2e2a) Thanks [@nukunga](https://github.com/nukunga)! - Fix sonar deep research model failing, should be called `sonar-deep-research`
-
-- [#1270](https://github.com/eyaltoledano/claude-task-master/pull/1270) [`20004a3`](https://github.com/eyaltoledano/claude-task-master/commit/20004a39ea848f747e1ff48981bfe176554e4055) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix complexity score not showing for `task-master show` and `task-master list`
-  - Added complexity score on "next task" when running `task-master list`
-  - Added colors to complexity to reflect complexity (easy, medium, hard)
-
-## 0.28.0-rc.2
-
-### Minor Changes
-
-- [#1273](https://github.com/eyaltoledano/claude-task-master/pull/1273) [`b43b7ce`](https://github.com/eyaltoledano/claude-task-master/commit/b43b7ce201625eee956fb2f8cd332f238bb78c21) Thanks [@ben-vargas](https://github.com/ben-vargas)! - Add Codex CLI provider with OAuth authentication
-  - Added codex-cli provider for GPT-5 and GPT-5-Codex models (272K input / 128K output)
-  - OAuth-first authentication via `codex login` - no API key required
-  - Optional OPENAI_CODEX_API_KEY support
-  - Codebase analysis capabilities automatically enabled
-  - Command-specific settings and approval/sandbox modes
-
-### Patch Changes
-
-- [#1277](https://github.com/eyaltoledano/claude-task-master/pull/1277) [`7b5a7c4`](https://github.com/eyaltoledano/claude-task-master/commit/7b5a7c4495a68b782f7407fc5d0e0d3ae81f42f5) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix MCP connection errors caused by deprecated generateTaskFiles calls. Resolves "Cannot read properties of null (reading 'toString')" errors when using MCP tools for task management operations.
-
-- [#1276](https://github.com/eyaltoledano/claude-task-master/pull/1276) [`caee040`](https://github.com/eyaltoledano/claude-task-master/commit/caee040907f856d31a660171c9e6d966f23c632e) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix MCP server error when file parameter not provided - now properly constructs default tasks.json path instead of failing with 'tasksJsonPath is required' error.
-
-## 0.28.0-rc.1
-
-### Patch Changes
-
-- [#1274](https://github.com/eyaltoledano/claude-task-master/pull/1274) [`4f984f8`](https://github.com/eyaltoledano/claude-task-master/commit/4f984f8a6965da9f9c7edd60ddfd6560ac022917) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Do a quick fix on build
-
-## 0.28.0-rc.0
-
-### Minor Changes
-
-- [#1215](https://github.com/eyaltoledano/claude-task-master/pull/1215) [`0079b7d`](https://github.com/eyaltoledano/claude-task-master/commit/0079b7defdad550811f704c470fdd01955d91d4d) Thanks [@joedanz](https://github.com/joedanz)! - Add Cursor IDE custom slash command support
-
-  Expose Task Master commands as Cursor slash commands by copying assets/claude/commands to .cursor/commands on profile add and cleaning up on remove.
-
-- [#1246](https://github.com/eyaltoledano/claude-task-master/pull/1246) [`18aa416`](https://github.com/eyaltoledano/claude-task-master/commit/18aa416035f44345bde1c7321490345733a5d042) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Added api keys page on docs website: docs.task-master.dev/getting-started/api-keys
-
-- [#1246](https://github.com/eyaltoledano/claude-task-master/pull/1246) [`18aa416`](https://github.com/eyaltoledano/claude-task-master/commit/18aa416035f44345bde1c7321490345733a5d042) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Move to AI SDK v5:
-  - Works better with claude-code and gemini-cli as ai providers
-  - Improved openai model family compatibility
-  - Migrate ollama provider to v2
-  - Closes #1223, #1013, #1161, #1174
-
-- [#1262](https://github.com/eyaltoledano/claude-task-master/pull/1262) [`738ec51`](https://github.com/eyaltoledano/claude-task-master/commit/738ec51c049a295a12839b2dfddaf05e23b8fede) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Migrate AI services to use generateObject for structured data generation
-
-  This update migrates all AI service calls from generateText to generateObject, ensuring more reliable and structured responses across all commands.
-
-  ### Key Changes:
-  - **Unified AI Service**: Replaced separate generateText implementations with a single generateObjectService that handles structured data generation
-  - **JSON Mode Support**: Added proper JSON mode configuration for providers that support it (OpenAI, Anthropic, Google, Groq)
-  - **Schema Validation**: Integrated Zod schemas for all AI-generated content with automatic validation
-  - **Provider Compatibility**: Maintained compatibility with all existing providers while leveraging their native structured output capabilities
-  - **Improved Reliability**: Structured output generation reduces parsing errors and ensures consistent data formats
-
-  ### Technical Improvements:
-  - Centralized provider configuration in `ai-providers-unified.js`
-  - Added `generateObject` support detection for each provider
-  - Implemented proper error handling for schema validation failures
-  - Maintained backward compatibility with existing prompt structures
-
-  ### Bug Fixes:
-  - Fixed subtask ID numbering issue where AI was generating inconsistent IDs (101-105, 601-603) instead of sequential numbering (1, 2, 3...)
-  - Enhanced prompt instructions to enforce proper ID generation patterns
-  - Ensured subtasks display correctly as X.1, X.2, X.3 format
-
-  This migration improves the reliability and consistency of AI-generated content throughout the Task Master application.
-
-- [#1112](https://github.com/eyaltoledano/claude-task-master/pull/1112) [`d67b81d`](https://github.com/eyaltoledano/claude-task-master/commit/d67b81d25ddd927fabb6f5deb368e8993519c541) Thanks [@olssonsten](https://github.com/olssonsten)! - Enhanced Roo Code profile with MCP timeout configuration for improved reliability during long-running AI operations. The Roo profile now automatically configures a 300-second timeout for MCP server operations, preventing timeouts during complex tasks like `parse-prd`, `expand-all`, `analyze-complexity`, and `research` operations. This change also replaces static MCP configuration files with programmatic generation for better maintainability.
-
-  **What's New:**
-  - 300-second timeout for MCP operations (up from default 60 seconds)
-  - Programmatic MCP configuration generation (replaces static asset files)
-  - Enhanced reliability for AI-powered operations
-  - Consistent with other AI coding assistant profiles
-
-  **Migration:** No user action required - existing Roo Code installations will automatically receive the enhanced MCP configuration on next initialization.
-
-- [#1246](https://github.com/eyaltoledano/claude-task-master/pull/1246) [`986ac11`](https://github.com/eyaltoledano/claude-task-master/commit/986ac117aee00bcd3e6830a0f76e1ad6d10e0bca) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Upgrade grok-cli ai provider to ai sdk v5
-
-### Patch Changes
-
-- [#1235](https://github.com/eyaltoledano/claude-task-master/pull/1235) [`aaacc3d`](https://github.com/eyaltoledano/claude-task-master/commit/aaacc3dae36247b4de72b2d2697f49e5df6d01e3) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Improve `analyze-complexity` cli docs and `--research` flag documentation
-
-- [#1251](https://github.com/eyaltoledano/claude-task-master/pull/1251) [`0b2c696`](https://github.com/eyaltoledano/claude-task-master/commit/0b2c6967c4605c33a100cff16f6ce8ff09ad06f0) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Change parent task back to "pending" when all subtasks are in "pending" state
-
-- [#1172](https://github.com/eyaltoledano/claude-task-master/pull/1172) [`b5fe723`](https://github.com/eyaltoledano/claude-task-master/commit/b5fe723f8ead928e9f2dbde13b833ee70ac3382d) Thanks [@jujax](https://github.com/jujax)! - Fix Claude Code settings validation for pathToClaudeCodeExecutable
-
-- [#1192](https://github.com/eyaltoledano/claude-task-master/pull/1192) [`2b69936`](https://github.com/eyaltoledano/claude-task-master/commit/2b69936ee7b34346d6de5175af20e077359e2e2a) Thanks [@nukunga](https://github.com/nukunga)! - Fix sonar deep research model failing, should be called `sonar-deep-research`
-
-- [#1270](https://github.com/eyaltoledano/claude-task-master/pull/1270) [`20004a3`](https://github.com/eyaltoledano/claude-task-master/commit/20004a39ea848f747e1ff48981bfe176554e4055) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix complexity score not showing for `task-master show` and `task-master list`
-  - Added complexity score on "next task" when running `task-master list`
-  - Added colors to complexity to reflect complexity (easy, medium, hard)
-
-## 0.27.3
-
-### Patch Changes
-
-- [#1254](https://github.com/eyaltoledano/claude-task-master/pull/1254) [`af53525`](https://github.com/eyaltoledano/claude-task-master/commit/af53525cbc660a595b67d4bb90d906911c71f45d) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fixed issue where `tm show` command could not find subtasks using dotted notation IDs (e.g., '8.1').
-  - The command now properly searches within parent task subtasks and returns the correct subtask information.
-
-## 0.27.2
-
-### Patch Changes
-
-- [#1248](https://github.com/eyaltoledano/claude-task-master/pull/1248) [`044a7bf`](https://github.com/eyaltoledano/claude-task-master/commit/044a7bfc98049298177bc655cf341d7a8b6a0011) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix set-status for subtasks:
-  - Parent tasks are now set as `done` when subtasks are all `done`
-  - Parent tasks are now set as `in-progress` when at least one subtask is `in-progress` or `done`
-
-## 0.27.1
-
-### Patch Changes
-
-- [#1232](https://github.com/eyaltoledano/claude-task-master/pull/1232) [`f487736`](https://github.com/eyaltoledano/claude-task-master/commit/f487736670ef8c484059f676293777eabb249c9e) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix module not found for new 0.27.0 release
-
-- [#1233](https://github.com/eyaltoledano/claude-task-master/pull/1233) [`c911608`](https://github.com/eyaltoledano/claude-task-master/commit/c911608f60454253f4e024b57ca84e5a5a53f65c) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix Zed MCP configuration by adding required "source" property
-  - Add "source": "custom" property to task-master-ai server in Zed settings.json
-
-## 0.27.1-rc.1
-
-### Patch Changes
-
-- [#1233](https://github.com/eyaltoledano/claude-task-master/pull/1233) [`1a18794`](https://github.com/eyaltoledano/claude-task-master/commit/1a1879483b86c118a4e46c02cbf4acebfcf6bcf9) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - One last testing final final
-
-## 0.27.1-rc.0
-
-### Patch Changes
-
-- [#1232](https://github.com/eyaltoledano/claude-task-master/pull/1232) [`f487736`](https://github.com/eyaltoledano/claude-task-master/commit/f487736670ef8c484059f676293777eabb249c9e) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Fix module not found for new 0.27.0 release
-
-## 0.27.0
-
-### Minor Changes
-
-- [#1220](https://github.com/eyaltoledano/claude-task-master/pull/1220) [`4e12643`](https://github.com/eyaltoledano/claude-task-master/commit/4e126430a092fb54afb035514fb3d46115714f97) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - No longer need --package=task-master-ai in mcp server
-  - A lot of users were having issues with Taskmaster and usually a simple fix was to remove --package from your mcp.json
-  - we now bundle our whole package, so we no longer need the --package
-
-- [#1200](https://github.com/eyaltoledano/claude-task-master/pull/1200) [`fce8414`](https://github.com/eyaltoledano/claude-task-master/commit/fce841490a9ebbf1801a42dd8a29397379cf1142) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Add new `task-master start` command for automated task execution with Claude Code
-  - You can now start working on tasks directly by running `task-master start <task-id>` which will automatically launch Claude Code with a comprehensive prompt containing all task details, implementation guidelines, and context.
-  - `task-master start` will automatically detect next-task when no ID is provided.
-
-- [#1200](https://github.com/eyaltoledano/claude-task-master/pull/1200) [`fce8414`](https://github.com/eyaltoledano/claude-task-master/commit/fce841490a9ebbf1801a42dd8a29397379cf1142) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Move from javascript to typescript, not a full refactor but we now have a typescript environment and are moving our javascript commands slowly into typescript
-
-- [#1200](https://github.com/eyaltoledano/claude-task-master/pull/1200) [`fce8414`](https://github.com/eyaltoledano/claude-task-master/commit/fce841490a9ebbf1801a42dd8a29397379cf1142) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Add grok-cli as a provider with full codebase context support. You can now use Grok models (grok-2, grok-3, grok-4, etc.) with Task Master for AI operations that have access to your entire codebase context, enabling more informed task generation and PRD parsing.
-
-  ## Setup Instructions
-  1. **Get your Grok API key** from [console.x.ai](https://console.x.ai)
-  2. **Set the environment variable**:
-     ```bash
-     export GROK_CLI_API_KEY="your-api-key-here"
-     ```
-  3. **Configure Task Master to use Grok**:
-     ```bash
-     task-master models --set-main grok-beta
-     # or
-     task-master models --set-research grok-beta
-     # or
-     task-master models --set-fallback grok-beta
-     ```
-
-  ## Key Features
-  - **Full codebase context**: Grok models can analyze your entire project when generating tasks or parsing PRDs
-  - **xAI model access**: Support for latest Grok models (grok-2, grok-3, grok-4, etc.)
-  - **Code-aware task generation**: Create more accurate and contextual tasks based on your actual codebase
-  - **Intelligent PRD parsing**: Parse requirements with understanding of your existing code structure
-
-  ## Available Models
-  - `grok-beta` - Latest Grok model with codebase context
-  - `grok-vision-beta` - Grok with vision capabilities and codebase context
-
-  The Grok CLI provider integrates with xAI's Grok models via grok-cli and can also use the local Grok CLI configuration file (`~/.grok/user-settings.json`) if available.
-
-  ## Credits
-
-  Built using the [grok-cli](https://github.com/superagent-ai/grok-cli) by Superagent AI for seamless integration with xAI's Grok models.
-
-- [#1225](https://github.com/eyaltoledano/claude-task-master/pull/1225) [`a621ff0`](https://github.com/eyaltoledano/claude-task-master/commit/a621ff05eafb51a147a9aabd7b37ddc0e45b0869) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Improve taskmaster ai provider defaults
-  - moving from main anthropic 3.7 to anthropic sonnet 4
-  - moving from fallback anthropic 3.5 to anthropic 3.7
-
-- [#1217](https://github.com/eyaltoledano/claude-task-master/pull/1217) [`e6de285`](https://github.com/eyaltoledano/claude-task-master/commit/e6de285ceacb0a397e952a63435cd32a9c731515) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - @tm/cli: add auto-update functionality to every command
-
-- [#1200](https://github.com/eyaltoledano/claude-task-master/pull/1200) [`fce8414`](https://github.com/eyaltoledano/claude-task-master/commit/fce841490a9ebbf1801a42dd8a29397379cf1142) Thanks [@eyaltoledano](https://github.com/eyaltoledano)! - Fix Grok model configuration validation and update deprecated Claude fallback model. Grok models now properly support their full 131K token capacity, and the fallback model has been upgraded to Claude Sonnet 4 for better performance and future compatibility.
-
-## 0.27.0-rc.2
-
-### Minor Changes
-
-- [#1217](https://github.com/eyaltoledano/claude-task-master/pull/1217) [`e6de285`](https://github.com/eyaltoledano/claude-task-master/commit/e6de285ceacb0a397e952a63435cd32a9c731515) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - @tm/cli: add auto-update functionality to every command
-
-## 0.27.0-rc.1
-
-### Minor Changes
-
-- [`255b9f0`](https://github.com/eyaltoledano/claude-task-master/commit/255b9f0334555b0063280abde701445cd62fa11b) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Testing one more pre-release iteration
-
-## 0.27.0-rc.0
-
-### Minor Changes
-
-- [#1213](https://github.com/eyaltoledano/claude-task-master/pull/1213) [`137ef36`](https://github.com/eyaltoledano/claude-task-master/commit/137ef362789a9cdfdb1925e35e0438c1fa6c69ee) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Test out the RC
-
-### Patch Changes
-
-- Updated dependencies [[`137ef36`](https://github.com/eyaltoledano/claude-task-master/commit/137ef362789a9cdfdb1925e35e0438c1fa6c69ee)]:
-  - @tm/cli@0.27.0-rc.0
-
-## 0.26.0
-
-### Minor Changes
-
-- [#1133](https://github.com/eyaltoledano/claude-task-master/pull/1133) [`df26c65`](https://github.com/eyaltoledano/claude-task-master/commit/df26c65632000874a73504963b08f18c46283144) Thanks [@neonwatty](https://github.com/neonwatty)! - Restore Taskmaster claude-code commands and move clear commands under /remove to avoid collision with the claude-code /clear command.
-
-- [#1163](https://github.com/eyaltoledano/claude-task-master/pull/1163) [`37af0f1`](https://github.com/eyaltoledano/claude-task-master/commit/37af0f191227a68d119b7f89a377bf932ee3ac66) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Enhanced Gemini CLI provider with codebase-aware task generation
-
-  Added automatic codebase analysis for Gemini CLI provider in parse-prd, and analyze-complexity, add-task, udpate-task, update, update-subtask commands
-  When using Gemini CLI 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
-
-- [#1165](https://github.com/eyaltoledano/claude-task-master/pull/1165) [`c4f92f6`](https://github.com/eyaltoledano/claude-task-master/commit/c4f92f6a0aee3435c56eb8d27d9aa9204284833e) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Add configurable codebase analysis feature flag with multiple configuration sources
-
-  Users can now control whether codebase analysis features (Claude Code and Gemini CLI integration) are enabled through environment variables, MCP configuration, or project config files.
-
-  Priority order: .env > MCP session env > .taskmaster/config.json.
-
-  Set `TASKMASTER_ENABLE_CODEBASE_ANALYSIS=false` in `.env` to disable codebase analysis prompts and tool integration.
-
-- [#1135](https://github.com/eyaltoledano/claude-task-master/pull/1135) [`8783708`](https://github.com/eyaltoledano/claude-task-master/commit/8783708e5e3389890a78fcf685d3da0580e73b3f) Thanks [@mm-parthy](https://github.com/mm-parthy)! - feat(move): improve cross-tag move UX and safety
-  - CLI: print "Next Steps" tips after cross-tag moves that used --ignore-dependencies (validate/fix guidance)
-  - CLI: show dedicated help block on ID collisions (destination tag already has the ID)
-  - Core: add structured suggestions to TASK_ALREADY_EXISTS errors
-  - MCP: map ID collision errors to TASK_ALREADY_EXISTS and include suggestions
-  - Tests: cover MCP options, error suggestions, CLI tips printing, and integration error payload suggestions
-
-  ***
-
-- [#1162](https://github.com/eyaltoledano/claude-task-master/pull/1162) [`4dad2fd`](https://github.com/eyaltoledano/claude-task-master/commit/4dad2fd613ceac56a65ae9d3c1c03092b8860ac9) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - Enhanced Claude Code and Google CLI integration with automatic codebase analysis for task operations
-
-  When using Claude Code as the AI provider, task management commands now automatically analyze your codebase before generating or updating tasks. This provides more accurate, context-aware implementation details that align with your project's existing architecture and patterns.
-
-  Commands contextualised:
-  - add-task
-  - update-subtask
-  - update-task
-  - update
-
-### Patch Changes
-
-- [#1135](https://github.com/eyaltoledano/claude-task-master/pull/1135) [`8783708`](https://github.com/eyaltoledano/claude-task-master/commit/8783708e5e3389890a78fcf685d3da0580e73b3f) Thanks [@mm-parthy](https://github.com/mm-parthy)! - docs(move): clarify cross-tag move docs; deprecate "force"; add explicit --with-dependencies/--ignore-dependencies examples
-
 ## 0.26.0-rc.1
 
 ### Minor Changes

CLAUDE.md

@@ -4,28 +4,6 @@
 **Import Task Master's development workflow commands and guidelines, treat as if import is in the main CLAUDE.md file.**
 @./.taskmaster/CLAUDE.md
 
-## Test Guidelines
-
-### Synchronous Tests
-- **NEVER use async/await in test functions** unless testing actual asynchronous operations
-- Use synchronous top-level imports instead of dynamic `await import()`
-- Test bodies should be synchronous whenever possible
-- Example:
-  ```javascript
-  // ✅ CORRECT - Synchronous imports
-  import { MyClass } from '../src/my-class.js';
-
-  it('should verify behavior', () => {
-    expect(new MyClass().property).toBe(value);
-  });
-
-  // ❌ INCORRECT - Async imports
-  it('should verify behavior', async () => {
-    const { MyClass } = await import('../src/my-class.js');
-    expect(new MyClass().property).toBe(value);
-  });
-  ```
-
 ## 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.

CLAUDE_CODE_PLUGIN.md

@@ -1,140 +0,0 @@
-# Taskmaster AI - Claude Code Marketplace
-
-This repository includes a Claude Code plugin marketplace in `.claude-plugin/marketplace.json`.
-
-## Installation
-
-### From GitHub (Public Repository)
-
-Once this repository is pushed to GitHub, users can install with:
-
-```bash
-# Add the marketplace
-/plugin marketplace add eyaltoledano/claude-task-master
-
-# Install the plugin
-/plugin install taskmaster@taskmaster
-```
-
-### Local Development/Testing
-
-```bash
-# From the project root directory
-cd /path/to/claude-task-master
-
-# Build the plugin first
-cd packages/claude-code-plugin
-npm run build
-cd ../..
-
-# In Claude Code
-/plugin marketplace add .
-/plugin install taskmaster@taskmaster
-```
-
-## Marketplace Structure
-
-```
-claude-task-master/
-├── .claude-plugin/
-│   └── marketplace.json        # Marketplace manifest (at repo root)
-│
-├── packages/claude-code-plugin/
-│   ├── src/build.ts           # Build tooling
-│   └── [generated plugin files]
-│
-└── assets/claude/              # Plugin source files
-    ├── commands/
-    └── agents/
-```
-
-## Available Plugins
-
-### taskmaster
-
-AI-powered task management system for ambitious development workflows.
-
-**Features:**
-
-- 49 slash commands for comprehensive task management
-- 3 specialized AI agents (orchestrator, executor, checker)
-- MCP server integration
-- Complexity analysis and auto-expansion
-- Dependency management and validation
-- Automated workflow capabilities
-
-**Quick Start:**
-
-```bash
-/tm:init
-/tm:parse-prd
-/tm:next
-```
-
-## For Contributors
-
-### Adding New Plugins
-
-To add more plugins to this marketplace:
-
-1. **Update marketplace.json**:
-
-   ```json
-   {
-     "plugins": [
-       {
-         "name": "new-plugin",
-         "source": "./path/to/plugin",
-         "description": "Plugin description",
-         "version": "1.0.0"
-       }
-     ]
-   }
-   ```
-
-2. **Commit and push** the changes
-
-3. **Users update** with: `/plugin marketplace update taskmaster`
-
-### Marketplace Versioning
-
-The marketplace version is tracked in `.claude-plugin/marketplace.json`:
-
-```json
-{
-  "metadata": {
-    "version": "1.0.0"
-  }
-}
-```
-
-Increment the version when adding or updating plugins.
-
-## Team Configuration
-
-Organizations can auto-install this marketplace for all team members by adding to `.claude/settings.json`:
-
-```json
-{
-  "extraKnownMarketplaces": {
-    "task-master": {
-      "source": {
-        "source": "github",
-        "repo": "eyaltoledano/claude-task-master"
-      }
-    }
-  },
-  "enabledPlugins": {
-    "taskmaster": {
-      "marketplace": "taskmaster"
-    }
-  }
-}
-```
-
-Team members who trust the repository folder will automatically get the marketplace and plugins installed.
-
-## Documentation
-
-- [Claude Code Plugin Docs](https://docs.claude.com/en/docs/claude-code/plugins)
-- [Marketplace Documentation](https://docs.claude.com/en/docs/claude-code/plugin-marketplaces)

README.md

@@ -60,19 +60,6 @@ The following documentation is also available in the `docs` directory:
 
 > **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.
 
-#### Claude Code Quick Install
-
-For Claude Code users:
-
-```bash
-claude mcp add taskmaster-ai -- npx -y task-master-ai
-```
-
-Don't forget to add your API keys to the configuration:
-- in the root .env of your Project
-- in the "env" section of your mcp config for taskmaster-ai
-
-
 ## Requirements
 
 Taskmaster utilizes AI across several commands, and those require a separate API key. You can use a variety of models from different AI providers provided you add your API keys. For example, if you want to use Claude 3.7, you'll need an Anthropic API key.
@@ -88,9 +75,8 @@ At least one (1) of the following is required:
 - xAI API Key (for research or main model)
 - OpenRouter API Key (for research or main model)
 - Claude Code (no API key required - requires Claude Code CLI)
-- Codex CLI (OAuth via ChatGPT subscription - requires Codex CLI)
 
-Using the research model is optional but highly recommended. You will need at least ONE API key (unless using Claude Code or Codex CLI with OAuth). Adding all API keys enables you to seamlessly switch between model providers at will.
+Using the research model is optional but highly recommended. You will need at least ONE API key (unless using Claude Code). Adding all API keys enables you to seamlessly switch between model providers at will.
 
 ## Quick Start
 
@@ -106,18 +92,17 @@ MCP (Model Control Protocol) lets you run Task Master directly from your editor.
 |              | 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`    |
-| **Q CLI**    | Global  | `~/.aws/amazonq/mcp.json`             |                                                   | `mcpServers` |
 
 ##### Manual Configuration
 
-###### Cursor & Windsurf & Q Developer CLI (`mcpServers`)
+###### Cursor & Windsurf (`mcpServers`)
 
 ```json
 {
   "mcpServers": {
     "task-master-ai": {
       "command": "npx",
-      "args": ["-y", "task-master-ai"],
+      "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",
@@ -137,7 +122,7 @@ MCP (Model Control Protocol) lets you run Task Master directly from your editor.
 
 > 🔑 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, restart your editor and check that your API keys are correctly configured.
+> **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`)
 
@@ -146,7 +131,7 @@ MCP (Model Control Protocol) lets you run Task Master directly from your editor.
   "servers": {
     "task-master-ai": {
       "command": "npx",
-      "args": ["-y", "task-master-ai"],
+      "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",
@@ -310,12 +295,6 @@ cd claude-task-master
 node scripts/init.js
 ```
 
-## Join Our Team
-
-<a href="https://tryhamster.com" target="_blank">
-  <img src="./images/hamster-hiring.png" alt="Join Hamster's founding team" />
-</a>
-
 ## Contributors
 
 <a href="https://github.com/eyaltoledano/claude-task-master/graphs/contributors">

apps/cli/CHANGELOG.md

@@ -1,41 +0,0 @@
-# @tm/cli
-
-## null
-
-### Patch Changes
-
-- Updated dependencies []:
-  - @tm/core@null
-
-## null
-
-### Patch Changes
-
-- Updated dependencies []:
-  - @tm/core@null
-
-## null
-
-### Patch Changes
-
-- Updated dependencies []:
-  - @tm/core@null
-
-## 0.27.0
-
-### Patch Changes
-
-- Updated dependencies []:
-  - @tm/core@0.26.1
-
-## 0.27.0-rc.0
-
-### Minor Changes
-
-- [#1213](https://github.com/eyaltoledano/claude-task-master/pull/1213) [`137ef36`](https://github.com/eyaltoledano/claude-task-master/commit/137ef362789a9cdfdb1925e35e0438c1fa6c69ee) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - testing this stuff out to see how the release candidate works with monorepo
-
-## 1.1.0-rc.0
-
-### Minor Changes
-
-- [#1213](https://github.com/eyaltoledano/claude-task-master/pull/1213) [`cd90b4d`](https://github.com/eyaltoledano/claude-task-master/commit/cd90b4d65fc2f04bdad9fb73aba320b58a124240) Thanks [@Crunchyman-ralph](https://github.com/Crunchyman-ralph)! - testing this stuff out to see how the release candidate works with monorepo

apps/cli/package.json

@@ -1,41 +1,44 @@
 {
 	"name": "@tm/cli",
+	"version": "1.0.0",
 	"description": "Task Master CLI - Command line interface for task management",
 	"type": "module",
-	"private": true,
 	"main": "./dist/index.js",
-	"types": "./src/index.ts",
+	"types": "./dist/index.d.ts",
 	"exports": {
-		".": "./src/index.ts"
+		".": {
+			"types": "./src/index.ts",
+			"import": "./dist/index.js",
+			"require": "./dist/index.js"
+		}
 	},
 	"files": ["dist", "README.md"],
 	"scripts": {
+		"build": "tsup",
+		"dev": "tsup --watch",
 		"typecheck": "tsc --noEmit",
 		"lint": "biome check src",
 		"format": "biome format --write src",
 		"test": "vitest run",
-		"test:watch": "vitest",
-		"test:coverage": "vitest run --coverage",
-		"test:unit": "vitest run -t unit",
-		"test:integration": "vitest run -t integration",
-		"test:e2e": "vitest run --dir tests/e2e",
-		"test:ci": "vitest run --coverage --reporter=dot"
+		"test:watch": "vitest"
 	},
 	"dependencies": {
 		"@tm/core": "*",
-		"boxen": "^8.0.1",
-		"chalk": "5.6.2",
+		"boxen": "^7.1.1",
+		"chalk": "^5.3.0",
 		"cli-table3": "^0.6.5",
 		"commander": "^12.1.0",
-		"inquirer": "^12.5.0",
-		"ora": "^8.2.0"
+		"inquirer": "^9.2.10",
+		"open": "^10.2.0",
+		"ora": "^8.1.0"
 	},
 	"devDependencies": {
 		"@biomejs/biome": "^1.9.4",
 		"@types/inquirer": "^9.0.3",
 		"@types/node": "^22.10.5",
+		"tsup": "^8.3.0",
 		"tsx": "^4.20.4",
-		"typescript": "^5.9.2",
+		"typescript": "^5.7.3",
 		"vitest": "^2.1.8"
 	},
 	"engines": {
@@ -43,11 +46,5 @@
 	},
 	"keywords": ["task-master", "cli", "task-management", "productivity"],
 	"author": "",
-	"license": "MIT",
-	"typesVersions": {
-		"*": {
-			"*": ["src/*"]
-		}
-	},
-	"version": ""
+	"license": "MIT"
 }

apps/cli/src/command-registry.ts

@@ -1,255 +0,0 @@
-/**
- * @fileoverview Centralized Command Registry
- * Provides a single location for registering all CLI commands
- */
-
-import { Command } from 'commander';
-
-// Import all commands
-import { ListTasksCommand } from './commands/list.command.js';
-import { ShowCommand } from './commands/show.command.js';
-import { AuthCommand } from './commands/auth.command.js';
-import { ContextCommand } from './commands/context.command.js';
-import { StartCommand } from './commands/start.command.js';
-import { SetStatusCommand } from './commands/set-status.command.js';
-import { ExportCommand } from './commands/export.command.js';
-
-/**
- * Command metadata for registration
- */
-export interface CommandMetadata {
-	name: string;
-	description: string;
-	commandClass: typeof Command;
-	category?: 'task' | 'auth' | 'utility' | 'development';
-}
-
-/**
- * Registry of all available commands
- */
-export class CommandRegistry {
-	/**
-	 * All available commands with their metadata
-	 */
-	private static commands: CommandMetadata[] = [
-		// Task Management Commands
-		{
-			name: 'list',
-			description: 'List all tasks with filtering and status overview',
-			commandClass: ListTasksCommand as any,
-			category: 'task'
-		},
-		{
-			name: 'show',
-			description: 'Display detailed information about a specific task',
-			commandClass: ShowCommand as any,
-			category: 'task'
-		},
-		{
-			name: 'start',
-			description: 'Start working on a task with claude-code',
-			commandClass: StartCommand as any,
-			category: 'task'
-		},
-		{
-			name: 'set-status',
-			description: 'Update the status of one or more tasks',
-			commandClass: SetStatusCommand as any,
-			category: 'task'
-		},
-		{
-			name: 'export',
-			description: 'Export tasks to external systems',
-			commandClass: ExportCommand as any,
-			category: 'task'
-		},
-
-		// Authentication & Context Commands
-		{
-			name: 'auth',
-			description: 'Manage authentication with tryhamster.com',
-			commandClass: AuthCommand as any,
-			category: 'auth'
-		},
-		{
-			name: 'context',
-			description: 'Manage workspace context (organization/brief)',
-			commandClass: ContextCommand as any,
-			category: 'auth'
-		}
-	];
-
-	/**
-	 * Register all commands on a program instance
-	 * @param program - Commander program to register commands on
-	 */
-	static registerAll(program: Command): void {
-		for (const cmd of this.commands) {
-			this.registerCommand(program, cmd);
-		}
-	}
-
-	/**
-	 * Register specific commands by category
-	 * @param program - Commander program to register commands on
-	 * @param category - Category of commands to register
-	 */
-	static registerByCategory(
-		program: Command,
-		category: 'task' | 'auth' | 'utility' | 'development'
-	): void {
-		const categoryCommands = this.commands.filter(
-			(cmd) => cmd.category === category
-		);
-
-		for (const cmd of categoryCommands) {
-			this.registerCommand(program, cmd);
-		}
-	}
-
-	/**
-	 * Register a single command by name
-	 * @param program - Commander program to register the command on
-	 * @param name - Name of the command to register
-	 */
-	static registerByName(program: Command, name: string): void {
-		const cmd = this.commands.find((c) => c.name === name);
-		if (cmd) {
-			this.registerCommand(program, cmd);
-		} else {
-			throw new Error(`Command '${name}' not found in registry`);
-		}
-	}
-
-	/**
-	 * Register a single command
-	 * @param program - Commander program to register the command on
-	 * @param metadata - Command metadata
-	 */
-	private static registerCommand(
-		program: Command,
-		metadata: CommandMetadata
-	): void {
-		const CommandClass = metadata.commandClass as any;
-
-		// Use the static registration method that all commands have
-		if (CommandClass.registerOn) {
-			CommandClass.registerOn(program);
-		} else if (CommandClass.register) {
-			CommandClass.register(program);
-		} else {
-			// Fallback to creating instance and adding
-			const instance = new CommandClass();
-			program.addCommand(instance);
-		}
-	}
-
-	/**
-	 * Get all registered command names
-	 */
-	static getCommandNames(): string[] {
-		return this.commands.map((cmd) => cmd.name);
-	}
-
-	/**
-	 * Get commands by category
-	 */
-	static getCommandsByCategory(
-		category: 'task' | 'auth' | 'utility' | 'development'
-	): CommandMetadata[] {
-		return this.commands.filter((cmd) => cmd.category === category);
-	}
-
-	/**
-	 * Add a new command to the registry
-	 * @param metadata - Command metadata to add
-	 */
-	static addCommand(metadata: CommandMetadata): void {
-		// Check if command already exists
-		if (this.commands.some((cmd) => cmd.name === metadata.name)) {
-			throw new Error(`Command '${metadata.name}' already exists in registry`);
-		}
-
-		this.commands.push(metadata);
-	}
-
-	/**
-	 * Remove a command from the registry
-	 * @param name - Name of the command to remove
-	 */
-	static removeCommand(name: string): boolean {
-		const index = this.commands.findIndex((cmd) => cmd.name === name);
-		if (index >= 0) {
-			this.commands.splice(index, 1);
-			return true;
-		}
-		return false;
-	}
-
-	/**
-	 * Get command metadata by name
-	 * @param name - Name of the command
-	 */
-	static getCommand(name: string): CommandMetadata | undefined {
-		return this.commands.find((cmd) => cmd.name === name);
-	}
-
-	/**
-	 * Check if a command exists
-	 * @param name - Name of the command
-	 */
-	static hasCommand(name: string): boolean {
-		return this.commands.some((cmd) => cmd.name === name);
-	}
-
-	/**
-	 * Get a formatted list of all commands for display
-	 */
-	static getFormattedCommandList(): string {
-		const categories = {
-			task: 'Task Management',
-			auth: 'Authentication & Context',
-			utility: 'Utilities',
-			development: 'Development'
-		};
-
-		let output = '';
-
-		for (const [category, title] of Object.entries(categories)) {
-			const cmds = this.getCommandsByCategory(
-				category as keyof typeof categories
-			);
-			if (cmds.length > 0) {
-				output += `\n${title}:\n`;
-				for (const cmd of cmds) {
-					output += `  ${cmd.name.padEnd(20)} ${cmd.description}\n`;
-				}
-			}
-		}
-
-		return output;
-	}
-}
-
-/**
- * Convenience function to register all CLI commands
- * @param program - Commander program instance
- */
-export function registerAllCommands(program: Command): void {
-	CommandRegistry.registerAll(program);
-}
-
-/**
- * Convenience function to register commands by category
- * @param program - Commander program instance
- * @param category - Category to register
- */
-export function registerCommandsByCategory(
-	program: Command,
-	category: 'task' | 'auth' | 'utility' | 'development'
-): void {
-	CommandRegistry.registerByCategory(program, category);
-}
-
-// Export the registry for direct access if needed
-export default CommandRegistry;

apps/cli/src/commands/auth.command.ts

@@ -143,7 +143,7 @@ export class AuthCommand extends Command {
 	 */
 	private async executeStatus(): Promise<void> {
 		try {
-			const result = await this.displayStatus();
+			const result = this.displayStatus();
 			this.setLastResult(result);
 		} catch (error: any) {
 			this.handleError(error);
@@ -171,8 +171,8 @@ export class AuthCommand extends Command {
 	/**
 	 * Display authentication status
 	 */
-	private async displayStatus(): Promise<AuthResult> {
-		const credentials = await this.authManager.getCredentials();
+	private displayStatus(): AuthResult {
+		const credentials = this.authManager.getCredentials();
 
 		console.log(chalk.cyan('\n🔐 Authentication Status\n'));
 
@@ -187,29 +187,19 @@ export class AuthCommand extends Command {
 			if (credentials.expiresAt) {
 				const expiresAt = new Date(credentials.expiresAt);
 				const now = new Date();
-				const timeRemaining = expiresAt.getTime() - now.getTime();
-				const hoursRemaining = Math.floor(timeRemaining / (1000 * 60 * 60));
-				const minutesRemaining = Math.floor(timeRemaining / (1000 * 60));
+				const hoursRemaining = Math.floor(
+					(expiresAt.getTime() - now.getTime()) / (1000 * 60 * 60)
+				);
 
-				if (timeRemaining > 0) {
-					// Token is still valid
-					if (hoursRemaining > 0) {
-						console.log(
-							chalk.gray(
-								`  Expires at: ${expiresAt.toLocaleString()} (${hoursRemaining} hours remaining)`
-							)
-						);
-					} else {
-						console.log(
-							chalk.gray(
-								`  Expires at: ${expiresAt.toLocaleString()} (${minutesRemaining} minutes remaining)`
-							)
-						);
-					}
-				} else {
-					// Token has expired
+				if (hoursRemaining > 0) {
 					console.log(
-						chalk.yellow(`  Expired at: ${expiresAt.toLocaleString()}`)
+						chalk.gray(
+							`  Expires: ${expiresAt.toLocaleString()} (${hoursRemaining} hours remaining)`
+						)
+					);
+				} else {
+					console.log(
+						chalk.yellow(`  Token expired at: ${expiresAt.toLocaleString()}`)
 					);
 				}
 			} else {
@@ -325,7 +315,7 @@ export class AuthCommand extends Command {
 			]);
 
 			if (!continueAuth) {
-				const credentials = await this.authManager.getCredentials();
+				const credentials = this.authManager.getCredentials();
 				ui.displaySuccess('Using existing authentication');
 
 				if (credentials) {
@@ -490,7 +480,7 @@ export class AuthCommand extends Command {
 	/**
 	 * Get current credentials (for programmatic usage)
 	 */
-	getCredentials(): Promise<AuthCredentials | null> {
+	getCredentials(): AuthCredentials | null {
 		return this.authManager.getCredentials();
 	}
 
@@ -503,7 +493,18 @@ export class AuthCommand extends Command {
 	}
 
 	/**
-	 * Register this command on an existing program
+	 * Static method to register this command on an existing program
+	 * This is for gradual migration - allows commands.js to use this
+	 */
+	static registerOn(program: Command): Command {
+		const authCommand = new AuthCommand();
+		program.addCommand(authCommand);
+		return authCommand;
+	}
+
+	/**
+	 * Alternative registration that returns the command for chaining
+	 * Can also configure the command name if needed
 	 */
 	static register(program: Command, name?: string): AuthCommand {
 		const authCommand = new AuthCommand(name);

apps/cli/src/commands/context.command.ts

@@ -1,704 +0,0 @@
-/**
- * @fileoverview Context command for managing org/brief selection
- * Provides a clean interface for workspace context management
- */
-
-import { Command } from 'commander';
-import chalk from 'chalk';
-import inquirer from 'inquirer';
-import ora, { Ora } from 'ora';
-import {
-	AuthManager,
-	AuthenticationError,
-	type UserContext
-} from '@tm/core/auth';
-import * as ui from '../utils/ui.js';
-
-/**
- * Result type from context command
- */
-export interface ContextResult {
-	success: boolean;
-	action: 'show' | 'select-org' | 'select-brief' | 'clear' | 'set';
-	context?: UserContext;
-	message?: string;
-}
-
-/**
- * ContextCommand extending Commander's Command class
- * Manages user's workspace context (org/brief selection)
- */
-export class ContextCommand extends Command {
-	private authManager: AuthManager;
-	private lastResult?: ContextResult;
-
-	constructor(name?: string) {
-		super(name || 'context');
-
-		// Initialize auth manager
-		this.authManager = AuthManager.getInstance();
-
-		// Configure the command
-		this.description(
-			'Manage workspace context (organization and brief selection)'
-		);
-
-		// Add subcommands
-		this.addOrgCommand();
-		this.addBriefCommand();
-		this.addClearCommand();
-		this.addSetCommand();
-
-		// Accept optional positional argument for brief ID or Hamster URL
-		this.argument('[briefOrUrl]', 'Brief ID or Hamster brief URL');
-
-		// Default action: if an argument is provided, resolve and set context; else show
-		this.action(async (briefOrUrl?: string) => {
-			if (briefOrUrl && briefOrUrl.trim().length > 0) {
-				await this.executeSetFromBriefInput(briefOrUrl.trim());
-				return;
-			}
-			await this.executeShow();
-		});
-	}
-
-	/**
-	 * Add org selection subcommand
-	 */
-	private addOrgCommand(): void {
-		this.command('org')
-			.description('Select an organization')
-			.action(async () => {
-				await this.executeSelectOrg();
-			});
-	}
-
-	/**
-	 * Add brief selection subcommand
-	 */
-	private addBriefCommand(): void {
-		this.command('brief')
-			.description('Select a brief within the current organization')
-			.action(async () => {
-				await this.executeSelectBrief();
-			});
-	}
-
-	/**
-	 * Add clear subcommand
-	 */
-	private addClearCommand(): void {
-		this.command('clear')
-			.description('Clear all context selections')
-			.action(async () => {
-				await this.executeClear();
-			});
-	}
-
-	/**
-	 * Add set subcommand for direct context setting
-	 */
-	private addSetCommand(): void {
-		this.command('set')
-			.description('Set context directly')
-			.option('--org <id>', 'Organization ID')
-			.option('--org-name <name>', 'Organization name')
-			.option('--brief <id>', 'Brief ID')
-			.option('--brief-name <name>', 'Brief name')
-			.action(async (options) => {
-				await this.executeSet(options);
-			});
-	}
-
-	/**
-	 * Execute show current context
-	 */
-	private async executeShow(): Promise<void> {
-		try {
-			const result = await this.displayContext();
-			this.setLastResult(result);
-		} catch (error: any) {
-			this.handleError(error);
-			process.exit(1);
-		}
-	}
-
-	/**
-	 * Display current context
-	 */
-	private async displayContext(): Promise<ContextResult> {
-		// Check authentication first
-		if (!this.authManager.isAuthenticated()) {
-			console.log(chalk.yellow('✗ Not authenticated'));
-			console.log(chalk.gray('\n  Run "tm auth login" to authenticate first'));
-
-			return {
-				success: false,
-				action: 'show',
-				message: 'Not authenticated'
-			};
-		}
-
-		const context = await this.authManager.getContext();
-
-		console.log(chalk.cyan('\n🌍 Workspace Context\n'));
-
-		if (context && (context.orgId || context.briefId)) {
-			if (context.orgName || context.orgId) {
-				console.log(chalk.green('✓ Organization'));
-				if (context.orgName) {
-					console.log(chalk.white(`  ${context.orgName}`));
-				}
-				if (context.orgId) {
-					console.log(chalk.gray(`  ID: ${context.orgId}`));
-				}
-			}
-
-			if (context.briefName || context.briefId) {
-				console.log(chalk.green('\n✓ Brief'));
-				if (context.briefName) {
-					console.log(chalk.white(`  ${context.briefName}`));
-				}
-				if (context.briefId) {
-					console.log(chalk.gray(`  ID: ${context.briefId}`));
-				}
-			}
-
-			if (context.updatedAt) {
-				console.log(
-					chalk.gray(
-						`\n  Last updated: ${new Date(context.updatedAt).toLocaleString()}`
-					)
-				);
-			}
-
-			return {
-				success: true,
-				action: 'show',
-				context,
-				message: 'Context loaded'
-			};
-		} else {
-			console.log(chalk.yellow('✗ No context selected'));
-			console.log(
-				chalk.gray('\n  Run "tm context org" to select an organization')
-			);
-			console.log(chalk.gray('  Run "tm context brief" to select a brief'));
-
-			return {
-				success: true,
-				action: 'show',
-				message: 'No context selected'
-			};
-		}
-	}
-
-	/**
-	 * Execute org selection
-	 */
-	private async executeSelectOrg(): Promise<void> {
-		try {
-			// Check authentication
-			if (!this.authManager.isAuthenticated()) {
-				ui.displayError('Not authenticated. Run "tm auth login" first.');
-				process.exit(1);
-			}
-
-			const result = await this.selectOrganization();
-			this.setLastResult(result);
-
-			if (!result.success) {
-				process.exit(1);
-			}
-		} catch (error: any) {
-			this.handleError(error);
-			process.exit(1);
-		}
-	}
-
-	/**
-	 * Select an organization interactively
-	 */
-	private async selectOrganization(): Promise<ContextResult> {
-		const spinner = ora('Fetching organizations...').start();
-
-		try {
-			// Fetch organizations from API
-			const organizations = await this.authManager.getOrganizations();
-			spinner.stop();
-
-			if (organizations.length === 0) {
-				ui.displayWarning('No organizations available');
-				return {
-					success: false,
-					action: 'select-org',
-					message: 'No organizations available'
-				};
-			}
-
-			// Prompt for selection
-			const { selectedOrg } = await inquirer.prompt([
-				{
-					type: 'list',
-					name: 'selectedOrg',
-					message: 'Select an organization:',
-					choices: organizations.map((org) => ({
-						name: org.name,
-						value: org
-					}))
-				}
-			]);
-
-			// Update context
-			await this.authManager.updateContext({
-				orgId: selectedOrg.id,
-				orgName: selectedOrg.name,
-				// Clear brief when changing org
-				briefId: undefined,
-				briefName: undefined
-			});
-
-			ui.displaySuccess(`Selected organization: ${selectedOrg.name}`);
-
-			return {
-				success: true,
-				action: 'select-org',
-				context: (await this.authManager.getContext()) || undefined,
-				message: `Selected organization: ${selectedOrg.name}`
-			};
-		} catch (error) {
-			spinner.fail('Failed to fetch organizations');
-			throw error;
-		}
-	}
-
-	/**
-	 * Execute brief selection
-	 */
-	private async executeSelectBrief(): Promise<void> {
-		try {
-			// Check authentication
-			if (!this.authManager.isAuthenticated()) {
-				ui.displayError('Not authenticated. Run "tm auth login" first.');
-				process.exit(1);
-			}
-
-			// Check if org is selected
-			const context = await this.authManager.getContext();
-			if (!context?.orgId) {
-				ui.displayError(
-					'No organization selected. Run "tm context org" first.'
-				);
-				process.exit(1);
-			}
-
-			const result = await this.selectBrief(context.orgId);
-			this.setLastResult(result);
-
-			if (!result.success) {
-				process.exit(1);
-			}
-		} catch (error: any) {
-			this.handleError(error);
-			process.exit(1);
-		}
-	}
-
-	/**
-	 * Select a brief within the current organization
-	 */
-	private async selectBrief(orgId: string): Promise<ContextResult> {
-		const spinner = ora('Fetching briefs...').start();
-
-		try {
-			// Fetch briefs from API
-			const briefs = await this.authManager.getBriefs(orgId);
-			spinner.stop();
-
-			if (briefs.length === 0) {
-				ui.displayWarning('No briefs available in this organization');
-				return {
-					success: false,
-					action: 'select-brief',
-					message: 'No briefs available'
-				};
-			}
-
-			// Prompt for selection
-			const { selectedBrief } = await inquirer.prompt([
-				{
-					type: 'list',
-					name: 'selectedBrief',
-					message: 'Select a brief:',
-					choices: [
-						{ name: '(No brief - organization level)', value: null },
-						...briefs.map((brief) => ({
-							name: `Brief ${brief.id} (${new Date(brief.createdAt).toLocaleDateString()})`,
-							value: brief
-						}))
-					]
-				}
-			]);
-
-			if (selectedBrief) {
-				// Update context with brief
-				const briefName = `Brief ${selectedBrief.id.slice(0, 8)}`;
-				await this.authManager.updateContext({
-					briefId: selectedBrief.id,
-					briefName: briefName
-				});
-
-				ui.displaySuccess(`Selected brief: ${briefName}`);
-
-				return {
-					success: true,
-					action: 'select-brief',
-					context: (await this.authManager.getContext()) || undefined,
-					message: `Selected brief: ${selectedBrief.name}`
-				};
-			} else {
-				// Clear brief selection
-				await this.authManager.updateContext({
-					briefId: undefined,
-					briefName: undefined
-				});
-
-				ui.displaySuccess('Cleared brief selection (organization level)');
-
-				return {
-					success: true,
-					action: 'select-brief',
-					context: (await this.authManager.getContext()) || undefined,
-					message: 'Cleared brief selection'
-				};
-			}
-		} catch (error) {
-			spinner.fail('Failed to fetch briefs');
-			throw error;
-		}
-	}
-
-	/**
-	 * Execute clear context
-	 */
-	private async executeClear(): Promise<void> {
-		try {
-			// Check authentication
-			if (!this.authManager.isAuthenticated()) {
-				ui.displayError('Not authenticated. Run "tm auth login" first.');
-				process.exit(1);
-			}
-
-			const result = await this.clearContext();
-			this.setLastResult(result);
-
-			if (!result.success) {
-				process.exit(1);
-			}
-		} catch (error: any) {
-			this.handleError(error);
-			process.exit(1);
-		}
-	}
-
-	/**
-	 * Clear all context selections
-	 */
-	private async clearContext(): Promise<ContextResult> {
-		try {
-			await this.authManager.clearContext();
-			ui.displaySuccess('Context cleared');
-
-			return {
-				success: true,
-				action: 'clear',
-				message: 'Context cleared'
-			};
-		} catch (error) {
-			ui.displayError(`Failed to clear context: ${(error as Error).message}`);
-
-			return {
-				success: false,
-				action: 'clear',
-				message: `Failed to clear context: ${(error as Error).message}`
-			};
-		}
-	}
-
-	/**
-	 * Execute set context with options
-	 */
-	private async executeSet(options: any): Promise<void> {
-		try {
-			// Check authentication
-			if (!this.authManager.isAuthenticated()) {
-				ui.displayError('Not authenticated. Run "tm auth login" first.');
-				process.exit(1);
-			}
-
-			const result = await this.setContext(options);
-			this.setLastResult(result);
-
-			if (!result.success) {
-				process.exit(1);
-			}
-		} catch (error: any) {
-			this.handleError(error);
-			process.exit(1);
-		}
-	}
-
-	/**
-	 * Execute setting context from a brief ID or Hamster URL
-	 */
-	private async executeSetFromBriefInput(briefOrUrl: string): Promise<void> {
-		let spinner: Ora | undefined;
-		try {
-			// Check authentication
-			if (!this.authManager.isAuthenticated()) {
-				ui.displayError('Not authenticated. Run "tm auth login" first.');
-				process.exit(1);
-			}
-
-			spinner = ora('Resolving brief...');
-			spinner.start();
-
-			// Extract brief ID
-			const briefId = this.extractBriefId(briefOrUrl);
-			if (!briefId) {
-				spinner.fail('Could not extract a brief ID from the provided input');
-				ui.displayError(
-					`Provide a valid brief ID or a Hamster brief URL, e.g. https://${process.env.TM_PUBLIC_BASE_DOMAIN}/home/hamster/briefs/<id>`
-				);
-				process.exit(1);
-			}
-
-			// Fetch brief and resolve its organization
-			const brief = await this.authManager.getBrief(briefId);
-			if (!brief) {
-				spinner.fail('Brief not found or you do not have access');
-				process.exit(1);
-			}
-
-			// Fetch org to get a friendly name (optional)
-			let orgName: string | undefined;
-			try {
-				const org = await this.authManager.getOrganization(brief.accountId);
-				orgName = org?.name;
-			} catch {
-				// Non-fatal if org lookup fails
-			}
-
-			// Update context: set org and brief
-			const briefName = `Brief ${brief.id.slice(0, 8)}`;
-			await this.authManager.updateContext({
-				orgId: brief.accountId,
-				orgName,
-				briefId: brief.id,
-				briefName
-			});
-
-			spinner.succeed('Context set from brief');
-			console.log(
-				chalk.gray(
-					`  Organization: ${orgName || brief.accountId}\n  Brief: ${briefName}`
-				)
-			);
-
-			this.setLastResult({
-				success: true,
-				action: 'set',
-				context: (await this.authManager.getContext()) || undefined,
-				message: 'Context set from brief'
-			});
-		} catch (error: any) {
-			try {
-				if (spinner?.isSpinning) spinner.stop();
-			} catch {}
-			this.handleError(error);
-			process.exit(1);
-		}
-	}
-
-	/**
-	 * Extract a brief ID from raw input (ID or Hamster URL)
-	 */
-	private extractBriefId(input: string): string | null {
-		const raw = input?.trim() ?? '';
-		if (!raw) return null;
-
-		const parseUrl = (s: string): URL | null => {
-			try {
-				return new URL(s);
-			} catch {}
-			try {
-				return new URL(`https://${s}`);
-			} catch {}
-			return null;
-		};
-
-		const fromParts = (path: string): string | null => {
-			const parts = path.split('/').filter(Boolean);
-			const briefsIdx = parts.lastIndexOf('briefs');
-			const candidate =
-				briefsIdx >= 0 && parts.length > briefsIdx + 1
-					? parts[briefsIdx + 1]
-					: parts[parts.length - 1];
-			return candidate?.trim() || null;
-		};
-
-		// 1) URL (absolute or scheme‑less)
-		const url = parseUrl(raw);
-		if (url) {
-			const qId = url.searchParams.get('id') || url.searchParams.get('briefId');
-			const candidate = (qId || fromParts(url.pathname)) ?? null;
-			if (candidate) {
-				// Light sanity check; let API be the final validator
-				if (this.isLikelyId(candidate) || candidate.length >= 8)
-					return candidate;
-			}
-		}
-
-		// 2) Looks like a path without scheme
-		if (raw.includes('/')) {
-			const candidate = fromParts(raw);
-			if (candidate && (this.isLikelyId(candidate) || candidate.length >= 8)) {
-				return candidate;
-			}
-		}
-
-		// 3) Fallback: raw token
-		return raw;
-	}
-
-	/**
-	 * Heuristic to check if a string looks like a brief ID (UUID-like)
-	 */
-	private isLikelyId(value: string): boolean {
-		const uuidRegex =
-			/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/;
-		const ulidRegex = /^[0-9A-HJKMNP-TV-Z]{26}$/i; // ULID
-		const slugRegex = /^[A-Za-z0-9_-]{16,}$/; // general token
-		return (
-			uuidRegex.test(value) || ulidRegex.test(value) || slugRegex.test(value)
-		);
-	}
-
-	/**
-	 * Set context directly from options
-	 */
-	private async setContext(options: any): Promise<ContextResult> {
-		try {
-			const context: Partial<UserContext> = {};
-
-			if (options.org) {
-				context.orgId = options.org;
-			}
-			if (options.orgName) {
-				context.orgName = options.orgName;
-			}
-			if (options.brief) {
-				context.briefId = options.brief;
-			}
-			if (options.briefName) {
-				context.briefName = options.briefName;
-			}
-
-			if (Object.keys(context).length === 0) {
-				ui.displayWarning('No context options provided');
-				return {
-					success: false,
-					action: 'set',
-					message: 'No context options provided'
-				};
-			}
-
-			await this.authManager.updateContext(context);
-			ui.displaySuccess('Context updated');
-
-			// Display what was set
-			if (context.orgName || context.orgId) {
-				console.log(
-					chalk.gray(`  Organization: ${context.orgName || context.orgId}`)
-				);
-			}
-			if (context.briefName || context.briefId) {
-				console.log(
-					chalk.gray(`  Brief: ${context.briefName || context.briefId}`)
-				);
-			}
-
-			return {
-				success: true,
-				action: 'set',
-				context: (await this.authManager.getContext()) || undefined,
-				message: 'Context updated'
-			};
-		} catch (error) {
-			ui.displayError(`Failed to set context: ${(error as Error).message}`);
-
-			return {
-				success: false,
-				action: 'set',
-				message: `Failed to set context: ${(error as Error).message}`
-			};
-		}
-	}
-
-	/**
-	 * Handle errors
-	 */
-	private handleError(error: any): void {
-		if (error instanceof AuthenticationError) {
-			console.error(chalk.red(`\n✗ ${error.message}`));
-
-			if (error.code === 'NOT_AUTHENTICATED') {
-				ui.displayWarning('Please authenticate first: tm auth login');
-			}
-		} else {
-			const msg = error?.message ?? String(error);
-			console.error(chalk.red(`Error: ${msg}`));
-
-			if (error.stack && process.env.DEBUG) {
-				console.error(chalk.gray(error.stack));
-			}
-		}
-	}
-
-	/**
-	 * Set the last result for programmatic access
-	 */
-	private setLastResult(result: ContextResult): void {
-		this.lastResult = result;
-	}
-
-	/**
-	 * Get the last result (for programmatic usage)
-	 */
-	getLastResult(): ContextResult | undefined {
-		return this.lastResult;
-	}
-
-	/**
-	 * Get current context (for programmatic usage)
-	 */
-	getContext(): Promise<UserContext | null> {
-		return this.authManager.getContext();
-	}
-
-	/**
-	 * Clean up resources
-	 */
-	async cleanup(): Promise<void> {
-		// No resources to clean up for context command
-	}
-
-	/**
-	 * Register this command on an existing program
-	 */
-	static register(program: Command, name?: string): ContextCommand {
-		const contextCommand = new ContextCommand(name);
-		program.addCommand(contextCommand);
-		return contextCommand;
-	}
-}

apps/cli/src/commands/export.command.ts

@@ -1,379 +0,0 @@
-/**
- * @fileoverview Export command for exporting tasks to external systems
- * Provides functionality to export tasks to Hamster briefs
- */
-
-import { Command } from 'commander';
-import chalk from 'chalk';
-import inquirer from 'inquirer';
-import ora, { Ora } from 'ora';
-import {
-	AuthManager,
-	AuthenticationError,
-	type UserContext
-} from '@tm/core/auth';
-import { TaskMasterCore, type ExportResult } from '@tm/core';
-import * as ui from '../utils/ui.js';
-
-/**
- * Result type from export command
- */
-export interface ExportCommandResult {
-	success: boolean;
-	action: 'export' | 'validate' | 'cancelled';
-	result?: ExportResult;
-	message?: string;
-}
-
-/**
- * ExportCommand extending Commander's Command class
- * Handles task export to external systems
- */
-export class ExportCommand extends Command {
-	private authManager: AuthManager;
-	private taskMasterCore?: TaskMasterCore;
-	private lastResult?: ExportCommandResult;
-
-	constructor(name?: string) {
-		super(name || 'export');
-
-		// Initialize auth manager
-		this.authManager = AuthManager.getInstance();
-
-		// Configure the command
-		this.description('Export tasks to external systems (e.g., Hamster briefs)');
-
-		// Add options
-		this.option('--org <id>', 'Organization ID to export to');
-		this.option('--brief <id>', 'Brief ID to export tasks to');
-		this.option('--tag <tag>', 'Export tasks from a specific tag');
-		this.option(
-			'--status <status>',
-			'Filter tasks by status (pending, in-progress, done, etc.)'
-		);
-		this.option('--exclude-subtasks', 'Exclude subtasks from export');
-		this.option('-y, --yes', 'Skip confirmation prompt');
-
-		// Accept optional positional argument for brief ID or Hamster URL
-		this.argument('[briefOrUrl]', 'Brief ID or Hamster brief URL');
-
-		// Default action
-		this.action(async (briefOrUrl?: string, options?: any) => {
-			await this.executeExport(briefOrUrl, options);
-		});
-	}
-
-	/**
-	 * Initialize the TaskMasterCore
-	 */
-	private async initializeServices(): Promise<void> {
-		if (this.taskMasterCore) {
-			return;
-		}
-
-		try {
-			// Initialize TaskMasterCore
-			this.taskMasterCore = await TaskMasterCore.create({
-				projectPath: process.cwd()
-			});
-		} catch (error) {
-			throw new Error(
-				`Failed to initialize services: ${(error as Error).message}`
-			);
-		}
-	}
-
-	/**
-	 * Execute the export command
-	 */
-	private async executeExport(
-		briefOrUrl?: string,
-		options?: any
-	): Promise<void> {
-		let spinner: Ora | undefined;
-
-		try {
-			// Check authentication
-			if (!this.authManager.isAuthenticated()) {
-				ui.displayError('Not authenticated. Run "tm auth login" first.');
-				process.exit(1);
-			}
-
-			// Initialize services
-			await this.initializeServices();
-
-			// Get current context
-			const context = await this.authManager.getContext();
-
-			// Determine org and brief IDs
-			let orgId = options?.org || context?.orgId;
-			let briefId = options?.brief || briefOrUrl || context?.briefId;
-
-			// If a URL/ID was provided as argument, resolve it
-			if (briefOrUrl && !options?.brief) {
-				spinner = ora('Resolving brief...').start();
-				const resolvedBrief = await this.resolveBriefInput(briefOrUrl);
-				if (resolvedBrief) {
-					briefId = resolvedBrief.briefId;
-					orgId = resolvedBrief.orgId;
-					spinner.succeed('Brief resolved');
-				} else {
-					spinner.fail('Could not resolve brief');
-					process.exit(1);
-				}
-			}
-
-			// Validate we have necessary IDs
-			if (!orgId) {
-				ui.displayError(
-					'No organization selected. Run "tm context org" or use --org flag.'
-				);
-				process.exit(1);
-			}
-
-			if (!briefId) {
-				ui.displayError(
-					'No brief specified. Run "tm context brief", provide a brief ID/URL, or use --brief flag.'
-				);
-				process.exit(1);
-			}
-
-			// Confirm export if not auto-confirmed
-			if (!options?.yes) {
-				const confirmed = await this.confirmExport(orgId, briefId, context);
-				if (!confirmed) {
-					ui.displayWarning('Export cancelled');
-					this.lastResult = {
-						success: false,
-						action: 'cancelled',
-						message: 'User cancelled export'
-					};
-					process.exit(0);
-				}
-			}
-
-			// Perform export
-			spinner = ora('Exporting tasks...').start();
-
-			const exportResult = await this.taskMasterCore!.exportTasks({
-				orgId,
-				briefId,
-				tag: options?.tag,
-				status: options?.status,
-				excludeSubtasks: options?.excludeSubtasks || false
-			});
-
-			if (exportResult.success) {
-				spinner.succeed(
-					`Successfully exported ${exportResult.taskCount} task(s) to brief`
-				);
-
-				// Display summary
-				console.log(chalk.cyan('\n📤 Export Summary\n'));
-				console.log(chalk.white(`  Organization: ${orgId}`));
-				console.log(chalk.white(`  Brief: ${briefId}`));
-				console.log(chalk.white(`  Tasks exported: ${exportResult.taskCount}`));
-				if (options?.tag) {
-					console.log(chalk.gray(`  Tag: ${options.tag}`));
-				}
-				if (options?.status) {
-					console.log(chalk.gray(`  Status filter: ${options.status}`));
-				}
-
-				if (exportResult.message) {
-					console.log(chalk.gray(`\n  ${exportResult.message}`));
-				}
-			} else {
-				spinner.fail('Export failed');
-				if (exportResult.error) {
-					console.error(chalk.red(`\n✗ ${exportResult.error.message}`));
-				}
-			}
-
-			this.lastResult = {
-				success: exportResult.success,
-				action: 'export',
-				result: exportResult
-			};
-		} catch (error: any) {
-			if (spinner?.isSpinning) spinner.fail('Export failed');
-			this.handleError(error);
-			process.exit(1);
-		}
-	}
-
-	/**
-	 * Resolve brief input to get brief and org IDs
-	 */
-	private async resolveBriefInput(
-		briefOrUrl: string
-	): Promise<{ briefId: string; orgId: string } | null> {
-		try {
-			// Extract brief ID from input
-			const briefId = this.extractBriefId(briefOrUrl);
-			if (!briefId) {
-				return null;
-			}
-
-			// Fetch brief to get organization
-			const brief = await this.authManager.getBrief(briefId);
-			if (!brief) {
-				ui.displayError('Brief not found or you do not have access');
-				return null;
-			}
-
-			return {
-				briefId: brief.id,
-				orgId: brief.accountId
-			};
-		} catch (error) {
-			console.error(chalk.red(`Failed to resolve brief: ${error}`));
-			return null;
-		}
-	}
-
-	/**
-	 * Extract a brief ID from raw input (ID or URL)
-	 */
-	private extractBriefId(input: string): string | null {
-		const raw = input?.trim() ?? '';
-		if (!raw) return null;
-
-		const parseUrl = (s: string): URL | null => {
-			try {
-				return new URL(s);
-			} catch {}
-			try {
-				return new URL(`https://${s}`);
-			} catch {}
-			return null;
-		};
-
-		const fromParts = (path: string): string | null => {
-			const parts = path.split('/').filter(Boolean);
-			const briefsIdx = parts.lastIndexOf('briefs');
-			const candidate =
-				briefsIdx >= 0 && parts.length > briefsIdx + 1
-					? parts[briefsIdx + 1]
-					: parts[parts.length - 1];
-			return candidate?.trim() || null;
-		};
-
-		// Try URL parsing
-		const url = parseUrl(raw);
-		if (url) {
-			const qId = url.searchParams.get('id') || url.searchParams.get('briefId');
-			const candidate = (qId || fromParts(url.pathname)) ?? null;
-			if (candidate) {
-				if (this.isLikelyId(candidate) || candidate.length >= 8) {
-					return candidate;
-				}
-			}
-		}
-
-		// Check if it looks like a path
-		if (raw.includes('/')) {
-			const candidate = fromParts(raw);
-			if (candidate && (this.isLikelyId(candidate) || candidate.length >= 8)) {
-				return candidate;
-			}
-		}
-
-		// Return raw if it looks like an ID
-		return raw;
-	}
-
-	/**
-	 * Check if a string looks like a brief ID
-	 */
-	private isLikelyId(value: string): boolean {
-		const uuidRegex =
-			/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/;
-		const ulidRegex = /^[0-9A-HJKMNP-TV-Z]{26}$/i;
-		const slugRegex = /^[A-Za-z0-9_-]{16,}$/;
-		return (
-			uuidRegex.test(value) || ulidRegex.test(value) || slugRegex.test(value)
-		);
-	}
-
-	/**
-	 * Confirm export with the user
-	 */
-	private async confirmExport(
-		orgId: string,
-		briefId: string,
-		context: UserContext | null
-	): Promise<boolean> {
-		console.log(chalk.cyan('\n📤 Export Tasks\n'));
-
-		// Show org name if available
-		if (context?.orgName) {
-			console.log(chalk.white(`  Organization: ${context.orgName}`));
-			console.log(chalk.gray(`  ID: ${orgId}`));
-		} else {
-			console.log(chalk.white(`  Organization ID: ${orgId}`));
-		}
-
-		// Show brief info
-		if (context?.briefName) {
-			console.log(chalk.white(`\n  Brief: ${context.briefName}`));
-			console.log(chalk.gray(`  ID: ${briefId}`));
-		} else {
-			console.log(chalk.white(`\n  Brief ID: ${briefId}`));
-		}
-
-		const { confirmed } = await inquirer.prompt([
-			{
-				type: 'confirm',
-				name: 'confirmed',
-				message: 'Do you want to proceed with export?',
-				default: true
-			}
-		]);
-
-		return confirmed;
-	}
-
-	/**
-	 * Handle errors
-	 */
-	private handleError(error: any): void {
-		if (error instanceof AuthenticationError) {
-			console.error(chalk.red(`\n✗ ${error.message}`));
-
-			if (error.code === 'NOT_AUTHENTICATED') {
-				ui.displayWarning('Please authenticate first: tm auth login');
-			}
-		} else {
-			const msg = error?.message ?? String(error);
-			console.error(chalk.red(`Error: ${msg}`));
-
-			if (error.stack && process.env.DEBUG) {
-				console.error(chalk.gray(error.stack));
-			}
-		}
-	}
-
-	/**
-	 * Get the last export result (useful for testing)
-	 */
-	public getLastResult(): ExportCommandResult | undefined {
-		return this.lastResult;
-	}
-
-	/**
-	 * Clean up resources
-	 */
-	async cleanup(): Promise<void> {
-		// No resources to clean up
-	}
-
-	/**
-	 * Register this command on an existing program
-	 */
-	static register(program: Command, name?: string): ExportCommand {
-		const exportCommand = new ExportCommand(name);
-		program.addCommand(exportCommand);
-		return exportCommand;
-	}
-}

apps/cli/src/commands/list.command.ts

@@ -15,20 +15,7 @@ import {
 	STATUS_ICONS,
 	type OutputFormat
 } from '@tm/core';
-import type { StorageType } from '@tm/core/types';
 import * as ui from '../utils/ui.js';
-import {
-	displayHeader,
-	displayDashboards,
-	calculateTaskStatistics,
-	calculateSubtaskStatistics,
-	calculateDependencyStatistics,
-	getPriorityBreakdown,
-	displayRecommendedNextTask,
-	getTaskDescription,
-	displaySuggestedNextSteps,
-	type NextTaskInfo
-} from '../ui/index.js';
 
 /**
  * Options interface for the list command
@@ -50,7 +37,7 @@ export interface ListTasksResult {
 	total: number;
 	filtered: number;
 	tag?: string;
-	storageType: Exclude<StorageType, 'auto'>;
+	storageType: 'file' | 'api';
 }
 
 /**
@@ -246,7 +233,7 @@ export class ListTasksCommand extends Command {
 				task.subtasks.forEach((subtask) => {
 					const subIcon = STATUS_ICONS[subtask.status];
 					console.log(
-						`  ${chalk.gray(String(subtask.id))} ${subIcon} ${chalk.gray(subtask.title)}`
+						`  ${chalk.gray(`${task.id}.${subtask.id}`)} ${subIcon} ${chalk.gray(subtask.title)}`
 					);
 				});
 			}
@@ -257,16 +244,19 @@ export class ListTasksCommand extends Command {
 	 * Display in text format with tables
 	 */
 	private displayText(data: ListTasksResult, withSubtasks?: boolean): void {
-		const { tasks, tag } = data;
+		const { tasks, total, filtered, tag, storageType } = data;
 
-		// Get file path for display
-		const filePath = this.tmCore ? `.taskmaster/tasks/tasks.json` : undefined;
+		// Header
+		ui.displayBanner(`Task List${tag ? ` (${tag})` : ''}`);
 
-		// Display header without banner (banner already shown by main CLI)
-		displayHeader({
-			tag: tag || 'master',
-			filePath: filePath
-		});
+		// Statistics
+		console.log(chalk.blue.bold('\n📊 Statistics:\n'));
+		console.log(`  Total tasks: ${chalk.cyan(total)}`);
+		console.log(`  Filtered: ${chalk.cyan(filtered)}`);
+		if (tag) {
+			console.log(`  Tag: ${chalk.cyan(tag)}`);
+		}
+		console.log(`  Storage: ${chalk.cyan(storageType)}`);
 
 		// No tasks message
 		if (tasks.length === 0) {
@@ -274,57 +264,21 @@ export class ListTasksCommand extends Command {
 			return;
 		}
 
-		// Calculate statistics
-		const taskStats = calculateTaskStatistics(tasks);
-		const subtaskStats = calculateSubtaskStatistics(tasks);
-		const depStats = calculateDependencyStatistics(tasks);
-		const priorityBreakdown = getPriorityBreakdown(tasks);
-
-		// Find next task following the same logic as findNextTask
-		const nextTaskInfo = this.findNextTask(tasks);
-
-		// Get the full task object with complexity data already included
-		const nextTask = nextTaskInfo
-			? tasks.find((t) => String(t.id) === String(nextTaskInfo.id))
-			: undefined;
-
-		// Display dashboard boxes (nextTask already has complexity from storage enrichment)
-		displayDashboards(
-			taskStats,
-			subtaskStats,
-			priorityBreakdown,
-			depStats,
-			nextTask
-		);
-
 		// Task table
+		console.log(chalk.blue.bold(`\n📋 Tasks (${tasks.length}):\n`));
 		console.log(
 			ui.createTaskTable(tasks, {
 				showSubtasks: withSubtasks,
-				showDependencies: true,
-				showComplexity: true // Enable complexity column
+				showDependencies: true
 			})
 		);
 
-		// Display recommended next task section immediately after table
-		if (nextTask) {
-			const description = getTaskDescription(nextTask);
-
-			displayRecommendedNextTask({
-				id: nextTask.id,
-				title: nextTask.title,
-				priority: nextTask.priority,
-				status: nextTask.status,
-				dependencies: nextTask.dependencies,
-				description,
-				complexity: nextTask.complexity as number | undefined
-			});
-		} else {
-			displayRecommendedNextTask(undefined);
-		}
-
-		// Display suggested next steps at the end
-		displaySuggestedNextSteps();
+		// Progress bar
+		const completedCount = tasks.filter(
+			(t: Task) => t.status === 'done'
+		).length;
+		console.log(chalk.blue.bold('\n📊 Overall Progress:\n'));
+		console.log(`  ${ui.createProgressBar(completedCount, tasks.length)}`);
 	}
 
 	/**
@@ -334,128 +288,6 @@ export class ListTasksCommand extends Command {
 		this.lastResult = result;
 	}
 
-	/**
-	 * Find the next task to work on
-	 * Implements the same logic as scripts/modules/task-manager/find-next-task.js
-	 */
-	private findNextTask(tasks: Task[]): NextTaskInfo | undefined {
-		const priorityValues: Record<string, number> = {
-			critical: 4,
-			high: 3,
-			medium: 2,
-			low: 1
-		};
-
-		// Build set of completed task IDs (including subtasks)
-		const completedIds = new Set<string>();
-		tasks.forEach((t) => {
-			if (t.status === 'done' || t.status === 'completed') {
-				completedIds.add(String(t.id));
-			}
-			if (t.subtasks) {
-				t.subtasks.forEach((st) => {
-					if (st.status === 'done' || st.status === 'completed') {
-						completedIds.add(`${t.id}.${st.id}`);
-					}
-				});
-			}
-		});
-
-		// First, look for eligible subtasks in in-progress parent tasks
-		const candidateSubtasks: NextTaskInfo[] = [];
-
-		tasks
-			.filter(
-				(t) => t.status === 'in-progress' && t.subtasks && t.subtasks.length > 0
-			)
-			.forEach((parent) => {
-				parent.subtasks!.forEach((st) => {
-					const stStatus = (st.status || 'pending').toLowerCase();
-					if (stStatus !== 'pending' && stStatus !== 'in-progress') return;
-
-					// Check if dependencies are satisfied
-					const fullDeps =
-						st.dependencies?.map((d) => {
-							// Handle both numeric and string IDs
-							if (typeof d === 'string' && d.includes('.')) {
-								return d;
-							}
-							return `${parent.id}.${d}`;
-						}) ?? [];
-
-					const depsSatisfied =
-						fullDeps.length === 0 ||
-						fullDeps.every((depId) => completedIds.has(String(depId)));
-
-					if (depsSatisfied) {
-						candidateSubtasks.push({
-							id: `${parent.id}.${st.id}`,
-							title: st.title || `Subtask ${st.id}`,
-							priority: st.priority || parent.priority || 'medium',
-							dependencies: fullDeps.map((d) => String(d))
-						});
-					}
-				});
-			});
-
-		if (candidateSubtasks.length > 0) {
-			// Sort by priority, then by dependencies count, then by ID
-			candidateSubtasks.sort((a, b) => {
-				const pa = priorityValues[a.priority || 'medium'] ?? 2;
-				const pb = priorityValues[b.priority || 'medium'] ?? 2;
-				if (pb !== pa) return pb - pa;
-
-				const depCountA = a.dependencies?.length || 0;
-				const depCountB = b.dependencies?.length || 0;
-				if (depCountA !== depCountB) return depCountA - depCountB;
-
-				return String(a.id).localeCompare(String(b.id));
-			});
-			return candidateSubtasks[0];
-		}
-
-		// Fall back to finding eligible top-level tasks
-		const eligibleTasks = tasks.filter((task) => {
-			// Skip non-eligible statuses
-			const status = (task.status || 'pending').toLowerCase();
-			if (status !== 'pending' && status !== 'in-progress') return false;
-
-			// Check dependencies
-			const deps = task.dependencies || [];
-			const depsSatisfied =
-				deps.length === 0 ||
-				deps.every((depId) => completedIds.has(String(depId)));
-
-			return depsSatisfied;
-		});
-
-		if (eligibleTasks.length === 0) return undefined;
-
-		// Sort eligible tasks
-		eligibleTasks.sort((a, b) => {
-			// Priority (higher first)
-			const pa = priorityValues[a.priority || 'medium'] ?? 2;
-			const pb = priorityValues[b.priority || 'medium'] ?? 2;
-			if (pb !== pa) return pb - pa;
-
-			// Dependencies count (fewer first)
-			const depCountA = a.dependencies?.length || 0;
-			const depCountB = b.dependencies?.length || 0;
-			if (depCountA !== depCountB) return depCountA - depCountB;
-
-			// ID (lower first)
-			return Number(a.id) - Number(b.id);
-		});
-
-		const nextTask = eligibleTasks[0];
-		return {
-			id: nextTask.id,
-			title: nextTask.title,
-			priority: nextTask.priority,
-			dependencies: nextTask.dependencies?.map((d) => String(d))
-		};
-	}
-
 	/**
 	 * Get the last result (for programmatic usage)
 	 */
@@ -474,7 +306,18 @@ export class ListTasksCommand extends Command {
 	}
 
 	/**
-	 * Register this command on an existing program
+	 * Static method to register this command on an existing program
+	 * This is for gradual migration - allows commands.js to use this
+	 */
+	static registerOn(program: Command): Command {
+		const listCommand = new ListTasksCommand();
+		program.addCommand(listCommand);
+		return listCommand;
+	}
+
+	/**
+	 * Alternative registration that returns the command for chaining
+	 * Can also configure the command name if needed
 	 */
 	static register(program: Command, name?: string): ListTasksCommand {
 		const listCommand = new ListTasksCommand(name);

apps/cli/src/commands/set-status.command.ts

@@ -1,304 +0,0 @@
-/**
- * @fileoverview SetStatusCommand using Commander's native class pattern
- * Extends Commander.Command for better integration with the framework
- */
-
-import { Command } from 'commander';
-import chalk from 'chalk';
-import boxen from 'boxen';
-import {
-	createTaskMasterCore,
-	type TaskMasterCore,
-	type TaskStatus
-} from '@tm/core';
-import type { StorageType } from '@tm/core/types';
-
-/**
- * Valid task status values for validation
- */
-const VALID_TASK_STATUSES: TaskStatus[] = [
-	'pending',
-	'in-progress',
-	'done',
-	'deferred',
-	'cancelled',
-	'blocked',
-	'review'
-];
-
-/**
- * Options interface for the set-status command
- */
-export interface SetStatusCommandOptions {
-	id?: string;
-	status?: TaskStatus;
-	format?: 'text' | 'json';
-	silent?: boolean;
-	project?: string;
-}
-
-/**
- * Result type from set-status command
- */
-export interface SetStatusResult {
-	success: boolean;
-	updatedTasks: Array<{
-		taskId: string;
-		oldStatus: TaskStatus;
-		newStatus: TaskStatus;
-	}>;
-	storageType: Exclude<StorageType, 'auto'>;
-}
-
-/**
- * SetStatusCommand extending Commander's Command class
- * This is a thin presentation layer over @tm/core
- */
-export class SetStatusCommand extends Command {
-	private tmCore?: TaskMasterCore;
-	private lastResult?: SetStatusResult;
-
-	constructor(name?: string) {
-		super(name || 'set-status');
-
-		// Configure the command
-		this.description('Update the status of one or more tasks')
-			.requiredOption(
-				'-i, --id <id>',
-				'Task ID(s) to update (comma-separated for multiple, supports subtasks like 5.2)'
-			)
-			.requiredOption(
-				'-s, --status <status>',
-				`New status (${VALID_TASK_STATUSES.join(', ')})`
-			)
-			.option('-f, --format <format>', 'Output format (text, json)', 'text')
-			.option('--silent', 'Suppress output (useful for programmatic usage)')
-			.option('-p, --project <path>', 'Project root directory', process.cwd())
-			.action(async (options: SetStatusCommandOptions) => {
-				await this.executeCommand(options);
-			});
-	}
-
-	/**
-	 * Execute the set-status command
-	 */
-	private async executeCommand(
-		options: SetStatusCommandOptions
-	): Promise<void> {
-		try {
-			// Validate required options
-			if (!options.id) {
-				console.error(chalk.red('Error: Task ID is required. Use -i or --id'));
-				process.exit(1);
-			}
-
-			if (!options.status) {
-				console.error(
-					chalk.red('Error: Status is required. Use -s or --status')
-				);
-				process.exit(1);
-			}
-
-			// Validate status
-			if (!VALID_TASK_STATUSES.includes(options.status)) {
-				console.error(
-					chalk.red(
-						`Error: Invalid status "${options.status}". Valid options: ${VALID_TASK_STATUSES.join(', ')}`
-					)
-				);
-				process.exit(1);
-			}
-
-			// Initialize TaskMaster core
-			this.tmCore = await createTaskMasterCore({
-				projectPath: options.project || process.cwd()
-			});
-
-			// Parse task IDs (handle comma-separated values)
-			const taskIds = options.id.split(',').map((id) => id.trim());
-
-			// Update each task
-			const updatedTasks: Array<{
-				taskId: string;
-				oldStatus: TaskStatus;
-				newStatus: TaskStatus;
-			}> = [];
-
-			for (const taskId of taskIds) {
-				try {
-					const result = await this.tmCore.updateTaskStatus(
-						taskId,
-						options.status
-					);
-					updatedTasks.push({
-						taskId: result.taskId,
-						oldStatus: result.oldStatus,
-						newStatus: result.newStatus
-					});
-				} catch (error) {
-					const errorMessage =
-						error instanceof Error ? error.message : String(error);
-
-					if (!options.silent) {
-						console.error(
-							chalk.red(`Failed to update task ${taskId}: ${errorMessage}`)
-						);
-					}
-					if (options.format === 'json') {
-						console.log(
-							JSON.stringify({
-								success: false,
-								error: errorMessage,
-								taskId,
-								timestamp: new Date().toISOString()
-							})
-						);
-					}
-					process.exit(1);
-				}
-			}
-
-			// Store result for potential reuse
-			this.lastResult = {
-				success: true,
-				updatedTasks,
-				storageType: this.tmCore.getStorageType() as Exclude<
-					StorageType,
-					'auto'
-				>
-			};
-
-			// Display results
-			this.displayResults(this.lastResult, options);
-		} catch (error) {
-			const errorMessage =
-				error instanceof Error ? error.message : 'Unknown error occurred';
-
-			if (!options.silent) {
-				console.error(chalk.red(`Error: ${errorMessage}`));
-			}
-
-			if (options.format === 'json') {
-				console.log(JSON.stringify({ success: false, error: errorMessage }));
-			}
-
-			process.exit(1);
-		} finally {
-			// Clean up resources
-			if (this.tmCore) {
-				await this.tmCore.close();
-			}
-		}
-	}
-
-	/**
-	 * Display results based on format
-	 */
-	private displayResults(
-		result: SetStatusResult,
-		options: SetStatusCommandOptions
-	): void {
-		const format = options.format || 'text';
-
-		switch (format) {
-			case 'json':
-				console.log(JSON.stringify(result, null, 2));
-				break;
-
-			case 'text':
-			default:
-				if (!options.silent) {
-					this.displayTextResults(result);
-				}
-				break;
-		}
-	}
-
-	/**
-	 * Display results in text format
-	 */
-	private displayTextResults(result: SetStatusResult): void {
-		if (result.updatedTasks.length === 1) {
-			// Single task update
-			const update = result.updatedTasks[0];
-			console.log(
-				boxen(
-					chalk.white.bold(`✅ Successfully updated task ${update.taskId}`) +
-						'\n\n' +
-						`${chalk.blue('From:')} ${this.getStatusDisplay(update.oldStatus)}\n` +
-						`${chalk.blue('To:')}   ${this.getStatusDisplay(update.newStatus)}`,
-					{
-						padding: 1,
-						borderColor: 'green',
-						borderStyle: 'round',
-						margin: { top: 1 }
-					}
-				)
-			);
-		} else {
-			// Multiple task updates
-			console.log(
-				boxen(
-					chalk.white.bold(
-						`✅ Successfully updated ${result.updatedTasks.length} tasks`
-					) +
-						'\n\n' +
-						result.updatedTasks
-							.map(
-								(update) =>
-									`${chalk.cyan(update.taskId)}: ${this.getStatusDisplay(update.oldStatus)} → ${this.getStatusDisplay(update.newStatus)}`
-							)
-							.join('\n'),
-					{
-						padding: 1,
-						borderColor: 'green',
-						borderStyle: 'round',
-						margin: { top: 1 }
-					}
-				)
-			);
-		}
-	}
-
-	/**
-	 * Get colored status display
-	 */
-	private getStatusDisplay(status: TaskStatus): string {
-		const statusColors: Record<TaskStatus, (text: string) => string> = {
-			pending: chalk.yellow,
-			'in-progress': chalk.blue,
-			done: chalk.green,
-			deferred: chalk.gray,
-			cancelled: chalk.red,
-			blocked: chalk.red,
-			review: chalk.magenta,
-			completed: chalk.green
-		};
-
-		const colorFn = statusColors[status] || chalk.white;
-		return colorFn(status);
-	}
-
-	/**
-	 * Get the last command result (useful for testing or chaining)
-	 */
-	getLastResult(): SetStatusResult | undefined {
-		return this.lastResult;
-	}
-
-	/**
-	 * Register this command on an existing program
-	 */
-	static register(program: Command, name?: string): SetStatusCommand {
-		const setStatusCommand = new SetStatusCommand(name);
-		program.addCommand(setStatusCommand);
-		return setStatusCommand;
-	}
-}
-
-/**
- * Factory function to create and configure the set-status command
- */
-export function createSetStatusCommand(): SetStatusCommand {
-	return new SetStatusCommand();
-}

apps/cli/src/commands/show.command.ts

@@ -1,332 +0,0 @@
-/**
- * @fileoverview ShowCommand using Commander's native class pattern
- * Extends Commander.Command for better integration with the framework
- */
-
-import { Command } from 'commander';
-import chalk from 'chalk';
-import boxen from 'boxen';
-import { createTaskMasterCore, type Task, type TaskMasterCore } from '@tm/core';
-import type { StorageType } from '@tm/core/types';
-import * as ui from '../utils/ui.js';
-import { displayTaskDetails } from '../ui/components/task-detail.component.js';
-
-/**
- * Options interface for the show command
- */
-export interface ShowCommandOptions {
-	id?: string;
-	status?: string;
-	format?: 'text' | 'json';
-	silent?: boolean;
-	project?: string;
-}
-
-/**
- * Result type from show command
- */
-export interface ShowTaskResult {
-	task: Task | null;
-	found: boolean;
-	storageType: Exclude<StorageType, 'auto'>;
-}
-
-/**
- * Result type for multiple tasks
- */
-export interface ShowMultipleTasksResult {
-	tasks: Task[];
-	notFound: string[];
-	storageType: Exclude<StorageType, 'auto'>;
-}
-
-/**
- * ShowCommand extending Commander's Command class
- * This is a thin presentation layer over @tm/core
- */
-export class ShowCommand extends Command {
-	private tmCore?: TaskMasterCore;
-	private lastResult?: ShowTaskResult | ShowMultipleTasksResult;
-
-	constructor(name?: string) {
-		super(name || 'show');
-
-		// Configure the command
-		this.description('Display detailed information about one or more tasks')
-			.argument('[id]', 'Task ID(s) to show (comma-separated for multiple)')
-			.option(
-				'-i, --id <id>',
-				'Task ID(s) to show (comma-separated for multiple)'
-			)
-			.option('-s, --status <status>', 'Filter subtasks by status')
-			.option('-f, --format <format>', 'Output format (text, json)', 'text')
-			.option('--silent', 'Suppress output (useful for programmatic usage)')
-			.option('-p, --project <path>', 'Project root directory', process.cwd())
-			.action(
-				async (taskId: string | undefined, options: ShowCommandOptions) => {
-					await this.executeCommand(taskId, options);
-				}
-			);
-	}
-
-	/**
-	 * Execute the show command
-	 */
-	private async executeCommand(
-		taskId: string | undefined,
-		options: ShowCommandOptions
-	): Promise<void> {
-		try {
-			// Validate options
-			if (!this.validateOptions(options)) {
-				process.exit(1);
-			}
-
-			// Initialize tm-core
-			await this.initializeCore(options.project || process.cwd());
-
-			// Get the task ID from argument or option
-			const idArg = taskId || options.id;
-			if (!idArg) {
-				console.error(chalk.red('Error: Please provide a task ID'));
-				process.exit(1);
-			}
-
-			// Check if multiple IDs are provided (comma-separated)
-			const taskIds = idArg
-				.split(',')
-				.map((id) => id.trim())
-				.filter((id) => id.length > 0);
-
-			// Get tasks from core
-			const result =
-				taskIds.length > 1
-					? await this.getMultipleTasks(taskIds, options)
-					: await this.getSingleTask(taskIds[0], options);
-
-			// Store result for programmatic access
-			this.setLastResult(result);
-
-			// Display results
-			if (!options.silent) {
-				this.displayResults(result, options);
-			}
-		} catch (error: any) {
-			const msg = error?.getSanitizedDetails?.() ?? {
-				message: error?.message ?? String(error)
-			};
-			console.error(chalk.red(`Error: ${msg.message || 'Unexpected error'}`));
-			if (error.stack && process.env.DEBUG) {
-				console.error(chalk.gray(error.stack));
-			}
-			process.exit(1);
-		}
-	}
-
-	/**
-	 * Validate command options
-	 */
-	private validateOptions(options: ShowCommandOptions): boolean {
-		// Validate format
-		if (options.format && !['text', 'json'].includes(options.format)) {
-			console.error(chalk.red(`Invalid format: ${options.format}`));
-			console.error(chalk.gray(`Valid formats: text, json`));
-			return false;
-		}
-
-		return true;
-	}
-
-	/**
-	 * Initialize TaskMasterCore
-	 */
-	private async initializeCore(projectRoot: string): Promise<void> {
-		if (!this.tmCore) {
-			this.tmCore = await createTaskMasterCore({ projectPath: projectRoot });
-		}
-	}
-
-	/**
-	 * Get a single task from tm-core
-	 */
-	private async getSingleTask(
-		taskId: string,
-		_options: ShowCommandOptions
-	): Promise<ShowTaskResult> {
-		if (!this.tmCore) {
-			throw new Error('TaskMasterCore not initialized');
-		}
-
-		// Get the task
-		const task = await this.tmCore.getTask(taskId);
-
-		// Get storage type
-		const storageType = this.tmCore.getStorageType();
-
-		return {
-			task,
-			found: task !== null,
-			storageType: storageType as Exclude<StorageType, 'auto'>
-		};
-	}
-
-	/**
-	 * Get multiple tasks from tm-core
-	 */
-	private async getMultipleTasks(
-		taskIds: string[],
-		_options: ShowCommandOptions
-	): Promise<ShowMultipleTasksResult> {
-		if (!this.tmCore) {
-			throw new Error('TaskMasterCore not initialized');
-		}
-
-		const tasks: Task[] = [];
-		const notFound: string[] = [];
-
-		// Get each task individually
-		for (const taskId of taskIds) {
-			const task = await this.tmCore.getTask(taskId);
-			if (task) {
-				tasks.push(task);
-			} else {
-				notFound.push(taskId);
-			}
-		}
-
-		// Get storage type
-		const storageType = this.tmCore.getStorageType();
-
-		return {
-			tasks,
-			notFound,
-			storageType: storageType as Exclude<StorageType, 'auto'>
-		};
-	}
-
-	/**
-	 * Display results based on format
-	 */
-	private displayResults(
-		result: ShowTaskResult | ShowMultipleTasksResult,
-		options: ShowCommandOptions
-	): void {
-		const format = options.format || 'text';
-
-		switch (format) {
-			case 'json':
-				this.displayJson(result);
-				break;
-
-			case 'text':
-			default:
-				if ('task' in result) {
-					// Single task result
-					this.displaySingleTask(result, options);
-				} else {
-					// Multiple tasks result
-					this.displayMultipleTasks(result, options);
-				}
-				break;
-		}
-	}
-
-	/**
-	 * Display in JSON format
-	 */
-	private displayJson(result: ShowTaskResult | ShowMultipleTasksResult): void {
-		console.log(JSON.stringify(result, null, 2));
-	}
-
-	/**
-	 * Display a single task in text format
-	 */
-	private displaySingleTask(
-		result: ShowTaskResult,
-		options: ShowCommandOptions
-	): void {
-		if (!result.found || !result.task) {
-			console.log(
-				boxen(chalk.yellow(`Task not found!`), {
-					padding: { top: 0, bottom: 0, left: 1, right: 1 },
-					borderColor: 'yellow',
-					borderStyle: 'round',
-					margin: { top: 1 }
-				})
-			);
-			return;
-		}
-
-		// Use the global task details display function
-		displayTaskDetails(result.task, {
-			statusFilter: options.status,
-			showSuggestedActions: true
-		});
-	}
-
-	/**
-	 * Display multiple tasks in text format
-	 */
-	private displayMultipleTasks(
-		result: ShowMultipleTasksResult,
-		_options: ShowCommandOptions
-	): void {
-		// Header
-		ui.displayBanner(`Tasks (${result.tasks.length} found)`);
-
-		if (result.notFound.length > 0) {
-			console.log(chalk.yellow(`\n⚠ Not found: ${result.notFound.join(', ')}`));
-		}
-
-		if (result.tasks.length === 0) {
-			ui.displayWarning('No tasks found matching the criteria.');
-			return;
-		}
-
-		// Task table
-		console.log(chalk.blue.bold(`\n📋 Tasks:\n`));
-		console.log(
-			ui.createTaskTable(result.tasks, {
-				showSubtasks: true,
-				showDependencies: true
-			})
-		);
-
-		console.log(`\n${chalk.gray('Storage: ' + result.storageType)}`);
-	}
-
-	/**
-	 * Set the last result for programmatic access
-	 */
-	private setLastResult(
-		result: ShowTaskResult | ShowMultipleTasksResult
-	): void {
-		this.lastResult = result;
-	}
-
-	/**
-	 * Get the last result (for programmatic usage)
-	 */
-	getLastResult(): ShowTaskResult | ShowMultipleTasksResult | undefined {
-		return this.lastResult;
-	}
-
-	/**
-	 * Clean up resources
-	 */
-	async cleanup(): Promise<void> {
-		if (this.tmCore) {
-			await this.tmCore.close();
-			this.tmCore = undefined;
-		}
-	}
-
-	/**
-	 * Register this command on an existing program
-	 */
-	static register(program: Command, name?: string): ShowCommand {
-		const showCommand = new ShowCommand(name);
-		program.addCommand(showCommand);
-		return showCommand;
-	}
-}

apps/cli/src/commands/start.command.ts

@@ -1,503 +0,0 @@
-/**
- * @fileoverview StartCommand using Commander's native class pattern
- * Extends Commander.Command for better integration with the framework
- * This is a thin presentation layer over @tm/core's TaskExecutionService
- */
-
-import { Command } from 'commander';
-import chalk from 'chalk';
-import boxen from 'boxen';
-import ora, { type Ora } from 'ora';
-import { spawn } from 'child_process';
-import {
-	createTaskMasterCore,
-	type TaskMasterCore,
-	type StartTaskResult as CoreStartTaskResult
-} from '@tm/core';
-import { displayTaskDetails } from '../ui/components/task-detail.component.js';
-import * as ui from '../utils/ui.js';
-
-/**
- * CLI-specific options interface for the start command
- */
-export interface StartCommandOptions {
-	id?: string;
-	format?: 'text' | 'json';
-	project?: string;
-	dryRun?: boolean;
-	force?: boolean;
-	noStatusUpdate?: boolean;
-}
-
-/**
- * CLI-specific result type from start command
- * Extends the core result with CLI-specific display information
- */
-export interface StartCommandResult extends CoreStartTaskResult {
-	storageType?: string;
-}
-
-/**
- * StartCommand extending Commander's Command class
- * This is a thin presentation layer over @tm/core's TaskExecutionService
- */
-export class StartCommand extends Command {
-	private tmCore?: TaskMasterCore;
-	private lastResult?: StartCommandResult;
-
-	constructor(name?: string) {
-		super(name || 'start');
-
-		// Configure the command
-		this.description(
-			'Start working on a task by launching claude-code with context'
-		)
-			.argument('[id]', 'Task ID to start working on')
-			.option('-i, --id <id>', 'Task ID to start working on')
-			.option('-f, --format <format>', 'Output format (text, json)', 'text')
-			.option('-p, --project <path>', 'Project root directory', process.cwd())
-			.option(
-				'--dry-run',
-				'Show what would be executed without launching claude-code'
-			)
-			.option(
-				'--force',
-				'Force start even if another task is already in-progress'
-			)
-			.option(
-				'--no-status-update',
-				'Do not automatically update task status to in-progress'
-			)
-			.action(
-				async (taskId: string | undefined, options: StartCommandOptions) => {
-					await this.executeCommand(taskId, options);
-				}
-			);
-	}
-
-	/**
-	 * Execute the start command
-	 */
-	private async executeCommand(
-		taskId: string | undefined,
-		options: StartCommandOptions
-	): Promise<void> {
-		let spinner: Ora | null = null;
-
-		try {
-			// Validate options
-			if (!this.validateOptions(options)) {
-				process.exit(1);
-			}
-
-			// Initialize tm-core with spinner
-			spinner = ora('Initializing Task Master...').start();
-			await this.initializeCore(options.project || process.cwd());
-			spinner.succeed('Task Master initialized');
-
-			// Get the task ID from argument or option, or find next available task
-			const idArg = taskId || options.id || null;
-			let targetTaskId = idArg;
-
-			if (!targetTaskId) {
-				spinner = ora('Finding next available task...').start();
-				targetTaskId = await this.performGetNextTask();
-				if (targetTaskId) {
-					spinner.succeed(`Found next task: #${targetTaskId}`);
-				} else {
-					spinner.fail('No available tasks found');
-				}
-			}
-
-			if (!targetTaskId) {
-				ui.displayError('No task ID provided and no available tasks found');
-				process.exit(1);
-			}
-
-			// Show pre-launch message (no spinner needed, it's just display)
-			if (!options.dryRun) {
-				await this.showPreLaunchMessage(targetTaskId);
-			}
-
-			// Use tm-core's startTask method with spinner
-			spinner = ora('Preparing task execution...').start();
-			const coreResult = await this.performStartTask(targetTaskId, options);
-
-			if (coreResult.started) {
-				spinner.succeed(
-					options.dryRun
-						? 'Dry run completed'
-						: 'Task prepared - launching Claude...'
-				);
-			} else {
-				spinner.fail('Task execution failed');
-			}
-
-			// Execute command if we have one and it's not a dry run
-			if (!options.dryRun && coreResult.command) {
-				// Stop any remaining spinners before launching Claude
-				if (spinner && !spinner.isSpinning) {
-					// Clear the line to make room for Claude
-					console.log();
-				}
-				await this.executeChildProcess(coreResult.command);
-			}
-
-			// Convert core result to CLI result with storage type
-			const result: StartCommandResult = {
-				...coreResult,
-				storageType: this.tmCore?.getStorageType()
-			};
-
-			// Store result for programmatic access
-			this.setLastResult(result);
-
-			// Display results (only for dry run or if execution failed)
-			if (options.dryRun || !coreResult.started) {
-				this.displayResults(result, options);
-			}
-		} catch (error: any) {
-			if (spinner) {
-				spinner.fail('Operation failed');
-			}
-			this.handleError(error);
-			process.exit(1);
-		}
-	}
-
-	/**
-	 * Validate command options
-	 */
-	private validateOptions(options: StartCommandOptions): boolean {
-		// Validate format
-		if (options.format && !['text', 'json'].includes(options.format)) {
-			console.error(chalk.red(`Invalid format: ${options.format}`));
-			console.error(chalk.gray(`Valid formats: text, json`));
-			return false;
-		}
-
-		return true;
-	}
-
-	/**
-	 * Initialize TaskMasterCore
-	 */
-	private async initializeCore(projectRoot: string): Promise<void> {
-		if (!this.tmCore) {
-			this.tmCore = await createTaskMasterCore({ projectPath: projectRoot });
-		}
-	}
-
-	/**
-	 * Get the next available task using tm-core
-	 */
-	private async performGetNextTask(): Promise<string | null> {
-		if (!this.tmCore) {
-			throw new Error('TaskMasterCore not initialized');
-		}
-		return this.tmCore.getNextAvailableTask();
-	}
-
-	/**
-	 * Show pre-launch message using tm-core data
-	 */
-	private async showPreLaunchMessage(targetTaskId: string): Promise<void> {
-		if (!this.tmCore) return;
-
-		const { task, subtask, subtaskId } =
-			await this.tmCore.getTaskWithSubtask(targetTaskId);
-		if (task) {
-			const workItemText = subtask
-				? `Subtask #${task.id}.${subtaskId} - ${subtask.title}`
-				: `Task #${task.id} - ${task.title}`;
-
-			console.log(
-				chalk.green('🚀 Starting: ') + chalk.white.bold(workItemText)
-			);
-			console.log(chalk.gray('Launching Claude Code...'));
-			console.log(); // Empty line
-		}
-	}
-
-	/**
-	 * Perform start task using tm-core business logic
-	 */
-	private async performStartTask(
-		targetTaskId: string,
-		options: StartCommandOptions
-	): Promise<CoreStartTaskResult> {
-		if (!this.tmCore) {
-			throw new Error('TaskMasterCore not initialized');
-		}
-
-		// Show spinner for status update if enabled
-		let statusSpinner: Ora | null = null;
-		if (!options.noStatusUpdate && !options.dryRun) {
-			statusSpinner = ora('Updating task status to in-progress...').start();
-		}
-
-		// Get execution command from tm-core (instead of executing directly)
-		const result = await this.tmCore.startTask(targetTaskId, {
-			dryRun: options.dryRun,
-			force: options.force,
-			updateStatus: !options.noStatusUpdate
-		});
-
-		if (statusSpinner) {
-			if (result.started) {
-				statusSpinner.succeed('Task status updated');
-			} else {
-				statusSpinner.warn('Task status update skipped');
-			}
-		}
-
-		if (!result) {
-			throw new Error('Failed to start task - core result is undefined');
-		}
-
-		// Don't execute here - let the main executeCommand method handle it
-		return result;
-	}
-
-	/**
-	 * Execute the child process directly in the main thread for better process control
-	 */
-	private async executeChildProcess(command: {
-		executable: string;
-		args: string[];
-		cwd: string;
-	}): Promise<void> {
-		return new Promise((resolve, reject) => {
-			// Don't show the full command with args as it can be very long
-			console.log(chalk.green('🚀 Launching Claude Code...'));
-			console.log(); // Add space before Claude takes over
-
-			const childProcess = spawn(command.executable, command.args, {
-				cwd: command.cwd,
-				stdio: 'inherit', // Inherit stdio from parent process
-				shell: false
-			});
-
-			childProcess.on('close', (code) => {
-				if (code === 0) {
-					resolve();
-				} else {
-					reject(new Error(`Process exited with code ${code}`));
-				}
-			});
-
-			childProcess.on('error', (error) => {
-				reject(new Error(`Failed to spawn process: ${error.message}`));
-			});
-
-			// Handle process termination signals gracefully
-			const cleanup = () => {
-				if (childProcess && !childProcess.killed) {
-					childProcess.kill('SIGTERM');
-				}
-			};
-
-			process.on('SIGINT', cleanup);
-			process.on('SIGTERM', cleanup);
-			process.on('exit', cleanup);
-		});
-	}
-
-	/**
-	 * Display results based on format
-	 */
-	private displayResults(
-		result: StartCommandResult,
-		options: StartCommandOptions
-	): void {
-		const format = options.format || 'text';
-
-		switch (format) {
-			case 'json':
-				this.displayJson(result);
-				break;
-
-			case 'text':
-			default:
-				this.displayTextResult(result, options);
-				break;
-		}
-	}
-
-	/**
-	 * Display in JSON format
-	 */
-	private displayJson(result: StartCommandResult): void {
-		console.log(JSON.stringify(result, null, 2));
-	}
-
-	/**
-	 * Display result in text format
-	 */
-	private displayTextResult(
-		result: StartCommandResult,
-		options: StartCommandOptions
-	): void {
-		if (!result.found || !result.task) {
-			console.log(
-				boxen(chalk.yellow(`Task not found!`), {
-					padding: { top: 0, bottom: 0, left: 1, right: 1 },
-					borderColor: 'yellow',
-					borderStyle: 'round',
-					margin: { top: 1 }
-				})
-			);
-			return;
-		}
-
-		const task = result.task;
-
-		if (options.dryRun) {
-			// For dry run, show full details since Claude Code won't be launched
-			let headerText = `Dry Run: Starting Task #${task.id} - ${task.title}`;
-
-			// If working on a specific subtask, highlight it in the header
-			if (result.subtask && result.subtaskId) {
-				headerText = `Dry Run: Starting Subtask #${task.id}.${result.subtaskId} - ${result.subtask.title}`;
-			}
-
-			displayTaskDetails(task, {
-				customHeader: headerText,
-				headerColor: 'yellow'
-			});
-
-			// Show claude-code prompt
-			if (result.executionOutput) {
-				console.log(); // Empty line for spacing
-				console.log(
-					boxen(
-						chalk.white.bold('Claude-Code Prompt:') +
-							'\n\n' +
-							result.executionOutput,
-						{
-							padding: 1,
-							borderStyle: 'round',
-							borderColor: 'cyan',
-							width: process.stdout.columns * 0.95 || 100
-						}
-					)
-				);
-			}
-
-			console.log(); // Empty line for spacing
-			console.log(
-				boxen(
-					chalk.yellow(
-						'🔍 Dry run - claude-code would be launched with the above prompt'
-					),
-					{
-						padding: { top: 0, bottom: 0, left: 1, right: 1 },
-						borderColor: 'yellow',
-						borderStyle: 'round'
-					}
-				)
-			);
-		} else {
-			// For actual execution, show minimal info since Claude Code will clear the terminal
-			if (result.started) {
-				// Determine what was worked on - task or subtask
-				let workItemText = `Task: #${task.id} - ${task.title}`;
-				let statusTarget = task.id;
-
-				if (result.subtask && result.subtaskId) {
-					workItemText = `Subtask: #${task.id}.${result.subtaskId} - ${result.subtask.title}`;
-					statusTarget = `${task.id}.${result.subtaskId}`;
-				}
-
-				// Post-execution message (shown after Claude Code exits)
-				console.log(
-					boxen(
-						chalk.green.bold('🎉 Task Session Complete!') +
-							'\n\n' +
-							chalk.white(workItemText) +
-							'\n\n' +
-							chalk.cyan('Next steps:') +
-							'\n' +
-							`• Run ${chalk.yellow('tm show ' + task.id)} to review task details\n` +
-							`• Run ${chalk.yellow('tm set-status --id=' + statusTarget + ' --status=done')} when complete\n` +
-							`• Run ${chalk.yellow('tm next')} to find the next available task\n` +
-							`• Run ${chalk.yellow('tm start')} to begin the next task`,
-						{
-							padding: 1,
-							borderStyle: 'round',
-							borderColor: 'green',
-							width: process.stdout.columns * 0.95 || 100,
-							margin: { top: 1 }
-						}
-					)
-				);
-			} else {
-				// Error case
-				console.log(
-					boxen(
-						chalk.red(
-							'❌ Failed to launch claude-code' +
-								(result.error ? `\nError: ${result.error}` : '')
-						),
-						{
-							padding: { top: 0, bottom: 0, left: 1, right: 1 },
-							borderColor: 'red',
-							borderStyle: 'round'
-						}
-					)
-				);
-			}
-		}
-
-		console.log(`\n${chalk.gray('Storage: ' + result.storageType)}`);
-	}
-
-	/**
-	 * Handle general errors
-	 */
-	private handleError(error: any): void {
-		const msg = error?.getSanitizedDetails?.() ?? {
-			message: error?.message ?? String(error)
-		};
-		console.error(chalk.red(`Error: ${msg.message || 'Unexpected error'}`));
-
-		// Show stack trace in development mode or when DEBUG is set
-		const isDevelopment = process.env.NODE_ENV !== 'production';
-		if ((isDevelopment || process.env.DEBUG) && error.stack) {
-			console.error(chalk.gray(error.stack));
-		}
-	}
-
-	/**
-	 * Set the last result for programmatic access
-	 */
-	private setLastResult(result: StartCommandResult): void {
-		this.lastResult = result;
-	}
-
-	/**
-	 * Get the last result (for programmatic usage)
-	 */
-	getLastResult(): StartCommandResult | undefined {
-		return this.lastResult;
-	}
-
-	/**
-	 * Clean up resources
-	 */
-	async cleanup(): Promise<void> {
-		if (this.tmCore) {
-			await this.tmCore.close();
-			this.tmCore = undefined;
-		}
-	}
-
-	/**
-	 * Register this command on an existing program
-	 */
-	static register(program: Command, name?: string): StartCommand {
-		const startCommand = new StartCommand(name);
-		program.addCommand(startCommand);
-		return startCommand;
-	}
-}

apps/cli/src/index.ts

@@ -5,32 +5,11 @@
 
 // Commands
 export { ListTasksCommand } from './commands/list.command.js';
-export { ShowCommand } from './commands/show.command.js';
 export { AuthCommand } from './commands/auth.command.js';
-export { ContextCommand } from './commands/context.command.js';
-export { StartCommand } from './commands/start.command.js';
-export { SetStatusCommand } from './commands/set-status.command.js';
-export { ExportCommand } from './commands/export.command.js';
-
-// Command Registry
-export {
-	CommandRegistry,
-	registerAllCommands,
-	registerCommandsByCategory,
-	type CommandMetadata
-} from './command-registry.js';
 
 // UI utilities (for other commands to use)
 export * as ui from './utils/ui.js';
 
-// Auto-update utilities
-export {
-	checkForUpdate,
-	performAutoUpdate,
-	displayUpgradeNotification,
-	compareVersions
-} from './utils/auto-update.js';
-
 // Re-export commonly used types from tm-core
 export type {
 	Task,

apps/cli/src/ui/components/dashboard.component.ts

@@ -1,568 +0,0 @@
-/**
- * @fileoverview Dashboard components for Task Master CLI
- * Displays project statistics and dependency information
- */
-
-import chalk from 'chalk';
-import boxen from 'boxen';
-import type { Task, TaskPriority } from '@tm/core/types';
-import { getComplexityWithColor } from '../../utils/ui.js';
-
-/**
- * Statistics for task collection
- */
-export interface TaskStatistics {
-	total: number;
-	done: number;
-	inProgress: number;
-	pending: number;
-	blocked: number;
-	deferred: number;
-	cancelled: number;
-	review?: number;
-	completionPercentage: number;
-}
-
-/**
- * Statistics for dependencies
- */
-export interface DependencyStatistics {
-	tasksWithNoDeps: number;
-	tasksReadyToWork: number;
-	tasksBlockedByDeps: number;
-	mostDependedOnTaskId?: number;
-	mostDependedOnCount?: number;
-	avgDependenciesPerTask: number;
-}
-
-/**
- * Next task information
- */
-export interface NextTaskInfo {
-	id: string | number;
-	title: string;
-	priority?: TaskPriority;
-	dependencies?: (string | number)[];
-	complexity?: number | string;
-}
-
-/**
- * Status breakdown for progress bars
- */
-export interface StatusBreakdown {
-	'in-progress'?: number;
-	pending?: number;
-	blocked?: number;
-	deferred?: number;
-	cancelled?: number;
-	review?: number;
-}
-
-/**
- * Create a progress bar with color-coded status segments
- */
-function createProgressBar(
-	completionPercentage: number,
-	width: number = 30,
-	statusBreakdown?: StatusBreakdown
-): string {
-	// If no breakdown provided, use simple green bar
-	if (!statusBreakdown) {
-		const filled = Math.round((completionPercentage / 100) * width);
-		const empty = width - filled;
-		return chalk.green('█').repeat(filled) + chalk.gray('░').repeat(empty);
-	}
-
-	// Build the bar with different colored sections
-	// Order matches the status display: Done, Cancelled, Deferred, In Progress, Review, Pending, Blocked
-	let bar = '';
-	let charsUsed = 0;
-
-	// 1. Green filled blocks for completed tasks (done)
-	const completedChars = Math.round((completionPercentage / 100) * width);
-	if (completedChars > 0) {
-		bar += chalk.green('█').repeat(completedChars);
-		charsUsed += completedChars;
-	}
-
-	// 2. Gray filled blocks for cancelled (won't be done)
-	if (statusBreakdown.cancelled && charsUsed < width) {
-		const cancelledChars = Math.round(
-			(statusBreakdown.cancelled / 100) * width
-		);
-		const actualChars = Math.min(cancelledChars, width - charsUsed);
-		if (actualChars > 0) {
-			bar += chalk.gray('█').repeat(actualChars);
-			charsUsed += actualChars;
-		}
-	}
-
-	// 3. Gray filled blocks for deferred (won't be done now)
-	if (statusBreakdown.deferred && charsUsed < width) {
-		const deferredChars = Math.round((statusBreakdown.deferred / 100) * width);
-		const actualChars = Math.min(deferredChars, width - charsUsed);
-		if (actualChars > 0) {
-			bar += chalk.gray('█').repeat(actualChars);
-			charsUsed += actualChars;
-		}
-	}
-
-	// 4. Blue filled blocks for in-progress (actively working)
-	if (statusBreakdown['in-progress'] && charsUsed < width) {
-		const inProgressChars = Math.round(
-			(statusBreakdown['in-progress'] / 100) * width
-		);
-		const actualChars = Math.min(inProgressChars, width - charsUsed);
-		if (actualChars > 0) {
-			bar += chalk.blue('█').repeat(actualChars);
-			charsUsed += actualChars;
-		}
-	}
-
-	// 5. Magenta empty blocks for review (almost done)
-	if (statusBreakdown.review && charsUsed < width) {
-		const reviewChars = Math.round((statusBreakdown.review / 100) * width);
-		const actualChars = Math.min(reviewChars, width - charsUsed);
-		if (actualChars > 0) {
-			bar += chalk.magenta('░').repeat(actualChars);
-			charsUsed += actualChars;
-		}
-	}
-
-	// 6. Yellow empty blocks for pending (ready to start)
-	if (statusBreakdown.pending && charsUsed < width) {
-		const pendingChars = Math.round((statusBreakdown.pending / 100) * width);
-		const actualChars = Math.min(pendingChars, width - charsUsed);
-		if (actualChars > 0) {
-			bar += chalk.yellow('░').repeat(actualChars);
-			charsUsed += actualChars;
-		}
-	}
-
-	// 7. Red empty blocks for blocked (can't start yet)
-	if (statusBreakdown.blocked && charsUsed < width) {
-		const blockedChars = Math.round((statusBreakdown.blocked / 100) * width);
-		const actualChars = Math.min(blockedChars, width - charsUsed);
-		if (actualChars > 0) {
-			bar += chalk.red('░').repeat(actualChars);
-			charsUsed += actualChars;
-		}
-	}
-
-	// Fill any remaining space with gray empty yellow blocks
-	if (charsUsed < width) {
-		bar += chalk.yellow('░').repeat(width - charsUsed);
-	}
-
-	return bar;
-}
-
-/**
- * Calculate task statistics from a list of tasks
- */
-export function calculateTaskStatistics(tasks: Task[]): TaskStatistics {
-	const stats: TaskStatistics = {
-		total: tasks.length,
-		done: 0,
-		inProgress: 0,
-		pending: 0,
-		blocked: 0,
-		deferred: 0,
-		cancelled: 0,
-		review: 0,
-		completionPercentage: 0
-	};
-
-	tasks.forEach((task) => {
-		switch (task.status) {
-			case 'done':
-				stats.done++;
-				break;
-			case 'in-progress':
-				stats.inProgress++;
-				break;
-			case 'pending':
-				stats.pending++;
-				break;
-			case 'blocked':
-				stats.blocked++;
-				break;
-			case 'deferred':
-				stats.deferred++;
-				break;
-			case 'cancelled':
-				stats.cancelled++;
-				break;
-			case 'review':
-				stats.review = (stats.review || 0) + 1;
-				break;
-		}
-	});
-
-	stats.completionPercentage =
-		stats.total > 0 ? Math.round((stats.done / stats.total) * 100) : 0;
-
-	return stats;
-}
-
-/**
- * Calculate subtask statistics from tasks
- */
-export function calculateSubtaskStatistics(tasks: Task[]): TaskStatistics {
-	const stats: TaskStatistics = {
-		total: 0,
-		done: 0,
-		inProgress: 0,
-		pending: 0,
-		blocked: 0,
-		deferred: 0,
-		cancelled: 0,
-		review: 0,
-		completionPercentage: 0
-	};
-
-	tasks.forEach((task) => {
-		if (task.subtasks && task.subtasks.length > 0) {
-			task.subtasks.forEach((subtask) => {
-				stats.total++;
-				switch (subtask.status) {
-					case 'done':
-						stats.done++;
-						break;
-					case 'in-progress':
-						stats.inProgress++;
-						break;
-					case 'pending':
-						stats.pending++;
-						break;
-					case 'blocked':
-						stats.blocked++;
-						break;
-					case 'deferred':
-						stats.deferred++;
-						break;
-					case 'cancelled':
-						stats.cancelled++;
-						break;
-					case 'review':
-						stats.review = (stats.review || 0) + 1;
-						break;
-				}
-			});
-		}
-	});
-
-	stats.completionPercentage =
-		stats.total > 0 ? Math.round((stats.done / stats.total) * 100) : 0;
-
-	return stats;
-}
-
-/**
- * Calculate dependency statistics
- */
-export function calculateDependencyStatistics(
-	tasks: Task[]
-): DependencyStatistics {
-	const completedTaskIds = new Set(
-		tasks.filter((t) => t.status === 'done').map((t) => t.id)
-	);
-
-	const tasksWithNoDeps = tasks.filter(
-		(t) =>
-			t.status !== 'done' && (!t.dependencies || t.dependencies.length === 0)
-	).length;
-
-	const tasksWithAllDepsSatisfied = tasks.filter(
-		(t) =>
-			t.status !== 'done' &&
-			t.dependencies &&
-			t.dependencies.length > 0 &&
-			t.dependencies.every((depId) => completedTaskIds.has(depId))
-	).length;
-
-	const tasksBlockedByDeps = tasks.filter(
-		(t) =>
-			t.status !== 'done' &&
-			t.dependencies &&
-			t.dependencies.length > 0 &&
-			!t.dependencies.every((depId) => completedTaskIds.has(depId))
-	).length;
-
-	// Calculate most depended-on task
-	const dependencyCount: Record<string, number> = {};
-	tasks.forEach((task) => {
-		if (task.dependencies && task.dependencies.length > 0) {
-			task.dependencies.forEach((depId) => {
-				const key = String(depId);
-				dependencyCount[key] = (dependencyCount[key] || 0) + 1;
-			});
-		}
-	});
-
-	let mostDependedOnTaskId: number | undefined;
-	let mostDependedOnCount = 0;
-
-	for (const [taskId, count] of Object.entries(dependencyCount)) {
-		if (count > mostDependedOnCount) {
-			mostDependedOnCount = count;
-			mostDependedOnTaskId = parseInt(taskId);
-		}
-	}
-
-	// Calculate average dependencies
-	const totalDependencies = tasks.reduce(
-		(sum, task) => sum + (task.dependencies ? task.dependencies.length : 0),
-		0
-	);
-	const avgDependenciesPerTask =
-		tasks.length > 0 ? totalDependencies / tasks.length : 0;
-
-	return {
-		tasksWithNoDeps,
-		tasksReadyToWork: tasksWithNoDeps + tasksWithAllDepsSatisfied,
-		tasksBlockedByDeps,
-		mostDependedOnTaskId,
-		mostDependedOnCount,
-		avgDependenciesPerTask
-	};
-}
-
-/**
- * Get priority counts
- */
-export function getPriorityBreakdown(
-	tasks: Task[]
-): Record<TaskPriority, number> {
-	const breakdown: Record<TaskPriority, number> = {
-		critical: 0,
-		high: 0,
-		medium: 0,
-		low: 0
-	};
-
-	tasks.forEach((task) => {
-		const priority = task.priority || 'medium';
-		breakdown[priority]++;
-	});
-
-	return breakdown;
-}
-
-/**
- * Calculate status breakdown as percentages
- */
-function calculateStatusBreakdown(stats: TaskStatistics): StatusBreakdown {
-	if (stats.total === 0) return {};
-
-	return {
-		'in-progress': (stats.inProgress / stats.total) * 100,
-		pending: (stats.pending / stats.total) * 100,
-		blocked: (stats.blocked / stats.total) * 100,
-		deferred: (stats.deferred / stats.total) * 100,
-		cancelled: (stats.cancelled / stats.total) * 100,
-		review: ((stats.review || 0) / stats.total) * 100
-	};
-}
-
-/**
- * Format status counts in the correct order with colors
- * @param stats - The statistics object containing counts
- * @param isSubtask - Whether this is for subtasks (affects "Done" vs "Completed" label)
- */
-function formatStatusLine(
-	stats: TaskStatistics,
-	isSubtask: boolean = false
-): string {
-	const parts: string[] = [];
-
-	// Order: Done, Cancelled, Deferred, In Progress, Review, Pending, Blocked
-	if (isSubtask) {
-		parts.push(`Completed: ${chalk.green(`${stats.done}/${stats.total}`)}`);
-	} else {
-		parts.push(`Done: ${chalk.green(stats.done)}`);
-	}
-
-	parts.push(`Cancelled: ${chalk.gray(stats.cancelled)}`);
-	parts.push(`Deferred: ${chalk.gray(stats.deferred)}`);
-
-	// Add line break for second row
-	const firstLine = parts.join('  ');
-	parts.length = 0;
-
-	parts.push(`In Progress: ${chalk.blue(stats.inProgress)}`);
-	parts.push(`Review: ${chalk.magenta(stats.review || 0)}`);
-	parts.push(`Pending: ${chalk.yellow(stats.pending)}`);
-	parts.push(`Blocked: ${chalk.red(stats.blocked)}`);
-
-	const secondLine = parts.join('  ');
-
-	return firstLine + '\n' + secondLine;
-}
-
-/**
- * Display the project dashboard box
- */
-export function displayProjectDashboard(
-	taskStats: TaskStatistics,
-	subtaskStats: TaskStatistics,
-	priorityBreakdown: Record<TaskPriority, number>
-): string {
-	// Calculate status breakdowns using the helper function
-	const taskStatusBreakdown = calculateStatusBreakdown(taskStats);
-	const subtaskStatusBreakdown = calculateStatusBreakdown(subtaskStats);
-
-	// Create progress bars with the breakdowns
-	const taskProgressBar = createProgressBar(
-		taskStats.completionPercentage,
-		30,
-		taskStatusBreakdown
-	);
-	const subtaskProgressBar = createProgressBar(
-		subtaskStats.completionPercentage,
-		30,
-		subtaskStatusBreakdown
-	);
-
-	const taskPercentage = `${taskStats.completionPercentage}% ${taskStats.done}/${taskStats.total}`;
-	const subtaskPercentage = `${subtaskStats.completionPercentage}% ${subtaskStats.done}/${subtaskStats.total}`;
-
-	const content =
-		chalk.white.bold('Project Dashboard') +
-		'\n' +
-		`Tasks Progress: ${taskProgressBar} ${chalk.yellow(taskPercentage)}\n` +
-		formatStatusLine(taskStats, false) +
-		'\n\n' +
-		`Subtasks Progress: ${subtaskProgressBar} ${chalk.cyan(subtaskPercentage)}\n` +
-		formatStatusLine(subtaskStats, true) +
-		'\n\n' +
-		chalk.cyan.bold('Priority Breakdown:') +
-		'\n' +
-		`${chalk.red('•')} ${chalk.white('High priority:')} ${priorityBreakdown.high}\n` +
-		`${chalk.yellow('•')} ${chalk.white('Medium priority:')} ${priorityBreakdown.medium}\n` +
-		`${chalk.green('•')} ${chalk.white('Low priority:')} ${priorityBreakdown.low}`;
-
-	return content;
-}
-
-/**
- * Display the dependency dashboard box
- */
-export function displayDependencyDashboard(
-	depStats: DependencyStatistics,
-	nextTask?: NextTaskInfo
-): string {
-	const content =
-		chalk.white.bold('Dependency Status & Next Task') +
-		'\n' +
-		chalk.cyan.bold('Dependency Metrics:') +
-		'\n' +
-		`${chalk.green('•')} ${chalk.white('Tasks with no dependencies:')} ${depStats.tasksWithNoDeps}\n` +
-		`${chalk.green('•')} ${chalk.white('Tasks ready to work on:')} ${depStats.tasksReadyToWork}\n` +
-		`${chalk.yellow('•')} ${chalk.white('Tasks blocked by dependencies:')} ${depStats.tasksBlockedByDeps}\n` +
-		`${chalk.magenta('•')} ${chalk.white('Most depended-on task:')} ${
-			depStats.mostDependedOnTaskId
-				? chalk.cyan(
-						`#${depStats.mostDependedOnTaskId} (${depStats.mostDependedOnCount} dependents)`
-					)
-				: chalk.gray('None')
-		}\n` +
-		`${chalk.blue('•')} ${chalk.white('Avg dependencies per task:')} ${depStats.avgDependenciesPerTask.toFixed(1)}\n\n` +
-		chalk.cyan.bold('Next Task to Work On:') +
-		'\n' +
-		`ID: ${nextTask ? chalk.cyan(String(nextTask.id)) : chalk.gray('N/A')} - ${
-			nextTask
-				? chalk.white.bold(nextTask.title)
-				: chalk.yellow('No task available')
-		}\n` +
-		`Priority: ${nextTask?.priority || chalk.gray('N/A')}  Dependencies: ${
-			nextTask?.dependencies?.length
-				? chalk.cyan(nextTask.dependencies.join(', '))
-				: chalk.gray('None')
-		}\n` +
-		`Complexity: ${nextTask?.complexity !== undefined ? getComplexityWithColor(nextTask.complexity) : chalk.gray('N/A')}`;
-
-	return content;
-}
-
-/**
- * Display dashboard boxes side by side or stacked
- */
-export function displayDashboards(
-	taskStats: TaskStatistics,
-	subtaskStats: TaskStatistics,
-	priorityBreakdown: Record<TaskPriority, number>,
-	depStats: DependencyStatistics,
-	nextTask?: NextTaskInfo
-): void {
-	const projectDashboardContent = displayProjectDashboard(
-		taskStats,
-		subtaskStats,
-		priorityBreakdown
-	);
-	const dependencyDashboardContent = displayDependencyDashboard(
-		depStats,
-		nextTask
-	);
-
-	// Get terminal width
-	const terminalWidth = process.stdout.columns || 80;
-	const minDashboardWidth = 50;
-	const minDependencyWidth = 50;
-	const totalMinWidth = minDashboardWidth + minDependencyWidth + 4;
-
-	// If terminal is wide enough, show side by side
-	if (terminalWidth >= totalMinWidth) {
-		const halfWidth = Math.floor(terminalWidth / 2);
-		const boxContentWidth = halfWidth - 4;
-
-		const dashboardBox = boxen(projectDashboardContent, {
-			padding: 1,
-			borderColor: 'blue',
-			borderStyle: 'round',
-			width: boxContentWidth,
-			dimBorder: false
-		});
-
-		const dependencyBox = boxen(dependencyDashboardContent, {
-			padding: 1,
-			borderColor: 'magenta',
-			borderStyle: 'round',
-			width: boxContentWidth,
-			dimBorder: false
-		});
-
-		// Create side-by-side layout
-		const dashboardLines = dashboardBox.split('\n');
-		const dependencyLines = dependencyBox.split('\n');
-		const maxHeight = Math.max(dashboardLines.length, dependencyLines.length);
-
-		const combinedLines = [];
-		for (let i = 0; i < maxHeight; i++) {
-			const dashLine = i < dashboardLines.length ? dashboardLines[i] : '';
-			const depLine = i < dependencyLines.length ? dependencyLines[i] : '';
-			const paddedDashLine = dashLine.padEnd(halfWidth, ' ');
-			combinedLines.push(paddedDashLine + depLine);
-		}
-
-		console.log(combinedLines.join('\n'));
-	} else {
-		// Show stacked vertically
-		const dashboardBox = boxen(projectDashboardContent, {
-			padding: 1,
-			borderColor: 'blue',
-			borderStyle: 'round',
-			margin: { top: 0, bottom: 1 }
-		});
-
-		const dependencyBox = boxen(dependencyDashboardContent, {
-			padding: 1,
-			borderColor: 'magenta',
-			borderStyle: 'round',
-			margin: { top: 0, bottom: 1 }
-		});
-
-		console.log(dashboardBox);
-		console.log(dependencyBox);
-	}
-}