docs: auto-update documentation based on changes in next branch

This PR was automatically generated to update documentation based on recent changes. Original commit: fix: improve docs and command help for analzye-complexity (#1235)\n\n\n Co-authored-by: Claude <claude-assistant@anthropic.com>
2025-09-23 16:34:00 +00:00
340 changed files with 16558 additions and 15747 deletions
--- a/.changeset/README.md
+++ b/.changeset/README.md
@@ -58,9 +58,9 @@ Examples:
 ```md
 # Good

-Added new `--research` flag to the `expand` command that uses Perplexity AI
-to provide research-backed task expansions. Requires PERPLEXITY_API_KEY
-environment variable.
+Added new `--research` flag to the `expand` command that uses your configured research model
+to provide research-backed task expansions. Requires appropriate API key
+for your research model.

 # Not Good

--- a/.changeset/auto-update-changelog-highlights.md
+++ b/.changeset/auto-update-changelog-highlights.md
@@ -1,7 +0,0 @@
---
-"task-master-ai": minor
---
-
-Add changelog highlights to auto-update notifications
-
-When the CLI auto-updates to a new version, it now displays a "What's New" section.
--- a/.changeset/chore-fix-docs.md
+++ b/.changeset/chore-fix-docs.md
@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Improve `analyze-complexity` cli docs and `--research` flag documentation
--- a/.changeset/config.json
+++ b/.changeset/config.json
@@ -11,6 +11,9 @@
  "access": "public",
  "baseBranch": "main",
  "ignore": [
-    "docs"
+    "docs",
+    "@tm/cli",
+    "@tm/core",
+    "@tm/build-config"
  ]
 }
--- a/.changeset/mcp-timeout-configuration.md
+++ b/.changeset/mcp-timeout-configuration.md
@@ -0,0 +1,13 @@
+---
+"task-master-ai": minor
+---
+
+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.
--- a/.changeset/mean-planes-wave.md
+++ b/.changeset/mean-planes-wave.md
@@ -1,47 +0,0 @@
---
-"task-master-ai": minor
---
-
-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!
--- a/.changeset/nice-ways-hope.md
+++ b/.changeset/nice-ways-hope.md
@@ -1,17 +0,0 @@
---
-"task-master-ai": minor
---
-
-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.
--- a/.changeset/petite-ideas-grab.md
+++ b/.changeset/petite-ideas-grab.md
@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Fix Claude Code settings validation for pathToClaudeCodeExecutable
--- a/.changeset/plain-falcons-serve.md
+++ b/.changeset/plain-falcons-serve.md
@@ -1,7 +0,0 @@
---
-"task-master-ai": patch
---
-
-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.
--- a/.changeset/silly-pandas-find.md
+++ b/.changeset/silly-pandas-find.md
@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Fix sonar deep research model failing, should be called `sonar-deep-research`
--- a/.changeset/smart-owls-relax.md
+++ b/.changeset/smart-owls-relax.md
@@ -1,16 +0,0 @@
---
-"task-master-ai": minor
---
-
-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.
--- a/.claude-plugin/marketplace.json
+++ b/.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"
-		}
-	]
-}
--- a/packages/claude-code-plugin/agents/task-checker.md
+++ b/packages/claude-code-plugin/agents/task-checker.md
--- a/.claude/agents/task-executor.md
+++ b/.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.
--- a/.claude/agents/task-orchestrator.md
+++ b/.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.
--- a/packages/claude-code-plugin/commands/add-dependency.md
+++ b/packages/claude-code-plugin/commands/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
--- a/packages/claude-code-plugin/commands/add-subtask.md
+++ b/packages/claude-code-plugin/commands/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  
--- a/packages/claude-code-plugin/commands/convert-task-to-subtask.md
+++ b/packages/claude-code-plugin/commands/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
--- a/packages/claude-code-plugin/commands/add-task.md
+++ b/packages/claude-code-plugin/commands/add-task.md
--- a/.claude/commands/tm/analyze-complexity/analyze-complexity.md
+++ b/.claude/commands/tm/analyze-complexity/analyze-complexity.md
@@ -16,7 +16,7 @@ task-master analyze-complexity [--research] [--threshold=5]

 ## Analysis Parameters

- `--research` → Use research AI for deeper analysis
+- `--research` → Use configured research model for deeper analysis
 - `--threshold=5` → Only flag tasks above complexity 5
 - Default: Analyze all pending tasks

@@ -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
 ```
--- a/.claude/commands/tm/complexity-report/complexity-report.md
+++ b/.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
 ```
--- a/packages/claude-code-plugin/commands/expand-all-tasks.md
+++ b/packages/claude-code-plugin/commands/expand-all-tasks.md
--- a/packages/claude-code-plugin/commands/expand-task.md
+++ b/packages/claude-code-plugin/commands/expand-task.md
--- a/.claude/commands/tm/fix-dependencies/fix-dependencies.md
+++ b/.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
--- a/packages/claude-code-plugin/commands/generate-tasks.md
+++ b/packages/claude-code-plugin/commands/generate-tasks.md
--- a/.claude/commands/tm/help.md
+++ b/.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>`
--- a/packages/claude-code-plugin/commands/init-project-quick.md
+++ b/packages/claude-code-plugin/commands/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!
--- a/packages/claude-code-plugin/commands/init-project.md
+++ b/packages/claude-code-plugin/commands/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
 ```
--- a/packages/claude-code-plugin/commands/learn.md
+++ b/packages/claude-code-plugin/commands/learn.md
--- a/packages/claude-code-plugin/commands/list-tasks-by-status.md
+++ b/packages/claude-code-plugin/commands/list-tasks-by-status.md
--- a/packages/claude-code-plugin/commands/list-tasks-with-subtasks.md
+++ b/packages/claude-code-plugin/commands/list-tasks-with-subtasks.md
--- a/packages/claude-code-plugin/commands/list-tasks.md
+++ b/packages/claude-code-plugin/commands/list-tasks.md
--- a/packages/claude-code-plugin/commands/setup-models.md
+++ b/packages/claude-code-plugin/commands/setup-models.md
--- a/packages/claude-code-plugin/commands/view-models.md
+++ b/packages/claude-code-plugin/commands/view-models.md
--- a/packages/claude-code-plugin/commands/next-task.md
+++ b/packages/claude-code-plugin/commands/next-task.md
--- a/packages/claude-code-plugin/commands/parse-prd-with-research.md
+++ b/packages/claude-code-plugin/commands/parse-prd-with-research.md
--- a/packages/claude-code-plugin/commands/parse-prd.md
+++ b/packages/claude-code-plugin/commands/parse-prd.md
--- a/.claude/commands/tm/remove-dependency/remove-dependency.md
+++ b/.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
--- a/packages/claude-code-plugin/commands/remove-subtask.md
+++ b/packages/claude-code-plugin/commands/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
--- a/packages/claude-code-plugin/commands/remove-all-subtasks.md
+++ b/packages/claude-code-plugin/commands/remove-all-subtasks.md
--- a/packages/claude-code-plugin/commands/remove-subtasks.md
+++ b/packages/claude-code-plugin/commands/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
--- a/packages/claude-code-plugin/commands/remove-task.md
+++ b/packages/claude-code-plugin/commands/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
--- a/packages/claude-code-plugin/commands/to-cancelled.md
+++ b/packages/claude-code-plugin/commands/to-cancelled.md
--- a/packages/claude-code-plugin/commands/to-deferred.md
+++ b/packages/claude-code-plugin/commands/to-deferred.md
--- a/packages/claude-code-plugin/commands/to-done.md
+++ b/packages/claude-code-plugin/commands/to-done.md
--- a/packages/claude-code-plugin/commands/to-in-progress.md
+++ b/packages/claude-code-plugin/commands/to-in-progress.md
--- a/packages/claude-code-plugin/commands/to-pending.md
+++ b/packages/claude-code-plugin/commands/to-pending.md
--- a/packages/claude-code-plugin/commands/to-review.md
+++ b/packages/claude-code-plugin/commands/to-review.md
--- a/packages/claude-code-plugin/commands/install-taskmaster.md
+++ b/packages/claude-code-plugin/commands/install-taskmaster.md
--- a/packages/claude-code-plugin/commands/quick-install-taskmaster.md
+++ b/packages/claude-code-plugin/commands/quick-install-taskmaster.md
--- a/packages/claude-code-plugin/commands/show-task.md
+++ b/packages/claude-code-plugin/commands/show-task.md
--- a/packages/claude-code-plugin/commands/project-status.md
+++ b/packages/claude-code-plugin/commands/project-status.md
--- a/packages/claude-code-plugin/commands/sync-readme.md
+++ b/packages/claude-code-plugin/commands/sync-readme.md
--- a/packages/claude-code-plugin/commands/tm-main.md
+++ b/packages/claude-code-plugin/commands/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
--- a/packages/claude-code-plugin/commands/update-single-task.md
+++ b/packages/claude-code-plugin/commands/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
--- a/packages/claude-code-plugin/commands/update-task.md
+++ b/packages/claude-code-plugin/commands/update-task.md
--- a/packages/claude-code-plugin/commands/update-tasks-from-id.md
+++ b/packages/claude-code-plugin/commands/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
--- a/packages/claude-code-plugin/commands/analyze-project.md
+++ b/packages/claude-code-plugin/commands/analyze-project.md
--- a/.claude/commands/tm/validate-dependencies/validate-dependencies.md
+++ b/.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
--- a/packages/claude-code-plugin/commands/auto-implement-tasks.md
+++ b/packages/claude-code-plugin/commands/auto-implement-tasks.md
--- a/packages/claude-code-plugin/commands/command-pipeline.md
+++ b/packages/claude-code-plugin/commands/command-pipeline.md
--- a/packages/claude-code-plugin/commands/smart-workflow.md
+++ b/packages/claude-code-plugin/commands/smart-workflow.md
--- a/.cursor/rules/dev_workflow.mdc
+++ b/.cursor/rules/dev_workflow.mdc
@@ -231,7 +231,7 @@ Taskmaster offers two primary ways to interact:

 -   Use `expand_task` / `task-master expand --id=<id>`. It automatically uses the complexity report if found, otherwise generates default number of subtasks.
 -   Use `--num=<number>` to specify an explicit number of subtasks, overriding defaults or complexity report recommendations.
-   Add `--research` flag to leverage Perplexity AI for research-backed expansion.
+-   Add `--research` flag to leverage your configured research model for research-backed expansion.
 -   Add `--force` flag to clear existing subtasks before generating new ones (default is to append).
 -   Use `--prompt="<context>"` to provide additional context when needed.
 -   Review and adjust generated subtasks as necessary.
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -6,6 +6,9 @@ on:
      - main
      - next
  pull_request:
+    branches:
+      - main
+      - next
  workflow_dispatch:

 concurrency:
--- a/.github/workflows/extension-ci.yml
+++ b/.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

--- a/.github/workflows/extension-release.yml
+++ b/.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

--- a/.kiro/steering/dev_workflow.md
+++ b/.kiro/steering/dev_workflow.md
@@ -229,7 +229,7 @@ Taskmaster offers two primary ways to interact:

 -   Use `expand_task` / `task-master expand --id=<id>`. It automatically uses the complexity report if found, otherwise generates default number of subtasks.
 -   Use `--num=<number>` to specify an explicit number of subtasks, overriding defaults or complexity report recommendations.
-   Add `--research` flag to leverage Perplexity AI for research-backed expansion.
+-   Add `--research` flag to leverage your configured research model for research-backed expansion.
 -   Add `--force` flag to clear existing subtasks before generating new ones (default is to append).
 -   Use `--prompt="<context>"` to provide additional context when needed.
 -   Review and adjust generated subtasks as necessary.
--- a/.manypkg.json
+++ b/.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"]
-}
--- a/.taskmaster/docs/README.md
+++ b/.taskmaster/docs/README.md
@@ -12,7 +12,7 @@ In an AI-driven development process—particularly with tools like [Cursor](http
 4. **Generate** individual task files (e.g., `task_001.txt`) for easy reference or to feed into an AI coding workflow.
 5. **Set task status**—mark tasks as `done`, `pending`, or `deferred` based on progress.
 6. **Expand** tasks with subtasks—break down complex tasks into smaller, more manageable subtasks.
-7. **Research-backed subtask generation**—use Perplexity AI to generate more informed and contextually relevant subtasks.
+7. **Research-backed subtask generation**—use your configured research model to generate more informed and contextually relevant subtasks.
 8. **Clear subtasks**—remove subtasks from specified tasks to allow regeneration or restructuring.
 9. **Show task details**—display detailed information about a specific task and its subtasks.

@@ -29,7 +29,7 @@ The script can be configured through environment variables in a `.env` file at t
 - `MODEL`: Specify which Claude model to use (default: "claude-3-7-sonnet-20250219")
 - `MAX_TOKENS`: Maximum tokens for model responses (default: 4000)
 - `TEMPERATURE`: Temperature for model responses (default: 0.7)
- `PERPLEXITY_API_KEY`: Your Perplexity API key for research-backed subtask generation
+- `PERPLEXITY_API_KEY`: Your Perplexity API key for research-backed subtask generation (if using Perplexity as your research model)
 - `PERPLEXITY_MODEL`: Specify which Perplexity model to use (default: "sonar-medium-online")
 - `DEBUG`: Enable debug logging (default: false)
 - `TASKMASTER_LOG_LEVEL`: Log level - debug, info, warn, error (default: info)
@@ -97,7 +97,7 @@ node scripts/dev.js update --from=4 --prompt="Refactor tasks from ID 4 onward to
 # Update all tasks (default from=1)
 node scripts/dev.js update --prompt="Add authentication to all relevant tasks"

-# With research-backed updates using Perplexity AI
+# With research-backed updates using your configured research model
 node scripts/dev.js update --from=4 --prompt="Integrate OAuth 2.0" --research

 # Specify a different tasks file
@@ -109,7 +109,7 @@ Notes:
 - The `--prompt` parameter is required and should explain the changes or new context
 - Only tasks that aren't marked as 'done' will be updated
 - Tasks with ID >= the specified --from value will be updated
- The `--research` flag uses Perplexity AI for more informed updates when available
+- The `--research` flag uses your configured research model for more informed updates when available

 ## Updating a Single Task

@@ -119,7 +119,7 @@ The `update-task` command allows you to update a specific task instead of multip
 # Update a specific task with new information
 node scripts/dev.js update-task --id=4 --prompt="Use JWT for authentication"

-# With research-backed updates using Perplexity AI
+# With research-backed updates using your configured research model
 node scripts/dev.js update-task --id=4 --prompt="Use JWT for authentication" --research
 ```

@@ -178,10 +178,10 @@ node scripts/dev.js expand --all
 # Force regeneration of subtasks for all pending tasks
 node scripts/dev.js expand --all --force

-# Use Perplexity AI for research-backed subtask generation
+# Use your configured research model for research-backed subtask generation
 node scripts/dev.js expand --id=3 --research

-# Use Perplexity AI for research-backed generation on all pending tasks
+# Use your configured research model for research-backed generation on all pending tasks
 node scripts/dev.js expand --all --research
 ```

@@ -211,17 +211,16 @@ Notes:

 The script integrates with two AI services:

-1. **Anthropic Claude**: Used for parsing PRDs, generating tasks, and creating subtasks.
-2. **Perplexity AI**: Used for research-backed subtask generation when the `--research` flag is specified.
+1. **Main AI Model**: Used for parsing PRDs, generating tasks, and creating subtasks (typically Anthropic Claude).
+2. **Research Model**: Used for research-backed subtask generation when the `--research` flag is specified.

-The Perplexity integration uses the OpenAI client to connect to Perplexity's API, which provides enhanced research capabilities for generating more informed subtasks. If the Perplexity API is unavailable or encounters an error, the script will automatically fall back to using Anthropic's Claude.
+The research integration provides enhanced research capabilities for generating more informed subtasks. You can configure different models for research (like Perplexity, which has access to current information) vs. main tasks. If the research model is unavailable or encounters an error, the script will automatically fall back to using your main model.

-To use the Perplexity integration:
+To use research-backed features:

-1. Obtain a Perplexity API key
-2. Add `PERPLEXITY_API_KEY` to your `.env` file
-3. Optionally specify `PERPLEXITY_MODEL` in your `.env` file (default: "sonar-medium-online")
-4. Use the `--research` flag with the `expand` command
+1. Configure your research model using `task-master models --setup`
+2. Ensure you have the appropriate API key in your `.env` file (e.g., `PERPLEXITY_API_KEY` if using Perplexity)
+3. Use the `--research` flag with supported commands

 ## Logging

@@ -342,13 +341,13 @@ node scripts/dev.js analyze-complexity --model=claude-3-opus-20240229
 # Set a custom complexity threshold (1-10)
 node scripts/dev.js analyze-complexity --threshold=6

-# Use Perplexity AI for research-backed complexity analysis
+# Use your configured research model for research-backed complexity analysis
 node scripts/dev.js analyze-complexity --research
 ```

 Notes:

- The command uses Claude to analyze each task's complexity (or Perplexity with --research flag)
+- The command uses your main model to analyze each task's complexity (or your configured research model with --research flag)
 - Tasks are scored on a scale of 1-10
 - Each task receives a recommended number of subtasks based on DEFAULT_SUBTASKS configuration
 - The default output path is `scripts/task-complexity-report.json`
--- a/.taskmaster/templates/example_prd_rpg.txt
+++ b/.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>
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,209 +1,5 @@
 # task-master-ai

-## 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
--- a/CLAUDE.md
+++ b/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.
--- a/CLAUDE_CODE_PLUGIN.md
+++ b/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)
--- a/README-task-master.md
+++ b/README-task-master.md
@@ -301,7 +301,7 @@ The agent will execute:
 task-master expand --all
 ```

-For research-backed subtask generation using Perplexity AI:
+For research-backed subtask generation using your configured research model:

 ```
 Please break down task 5 using research-backed generation.
@@ -450,7 +450,7 @@ task-master analyze-complexity --threshold=6
 # Use an alternative tasks file
 task-master analyze-complexity --file=custom-tasks.json

-# Use Perplexity AI for research-backed complexity analysis
+# Use your configured research model for research-backed complexity analysis
 task-master analyze-complexity --research
 ```

--- a/README.md
+++ b/README.md
@@ -88,9 +88,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,11 +105,10 @@ 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
 {
--- a/apps/cli/CHANGELOG.md
+++ b/apps/cli/CHANGELOG.md
@@ -1,19 +1,5 @@
 # @tm/cli

-## null
-
-### Patch Changes
-
- Updated dependencies []:
-  - @tm/core@null
-
-## null
-
-### Patch Changes
-
- Updated dependencies []:
-  - @tm/core@null
-
 ## 0.27.0

 ### Patch Changes
--- a/apps/cli/package.json
+++ b/apps/cli/package.json
@@ -1,5 +1,6 @@
 {
 	"name": "@tm/cli",
+	"version": "0.27.0",
 	"description": "Task Master CLI - Command line interface for task management",
 	"type": "module",
 	"private": true,
@@ -23,19 +24,19 @@
 	},
 	"dependencies": {
 		"@tm/core": "*",
-		"boxen": "^8.0.1",
+		"boxen": "^7.1.1",
 		"chalk": "5.6.2",
 		"cli-table3": "^0.6.5",
 		"commander": "^12.1.0",
-		"inquirer": "^12.5.0",
-		"ora": "^8.2.0"
+		"inquirer": "^9.2.10",
+		"ora": "^8.1.0"
 	},
 	"devDependencies": {
 		"@biomejs/biome": "^1.9.4",
 		"@types/inquirer": "^9.0.3",
 		"@types/node": "^22.10.5",
 		"tsx": "^4.20.4",
-		"typescript": "^5.9.2",
+		"typescript": "^5.7.3",
 		"vitest": "^2.1.8"
 	},
 	"engines": {
@@ -48,6 +49,5 @@
 		"*": {
 			"*": ["src/*"]
 		}
-	},
-	"version": ""
+	}
 }
--- a/apps/cli/src/command-registry.ts
+++ b/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;
--- a/apps/cli/src/commands/auth.command.ts
+++ b/apps/cli/src/commands/auth.command.ts
@@ -493,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);
--- a/apps/cli/src/commands/context.command.ts
+++ b/apps/cli/src/commands/context.command.ts
@@ -694,7 +694,16 @@ export class ContextCommand extends Command {
 	}

 	/**
-	 * Register this command on an existing program
+	 * Static method to register this command on an existing program
+	 */
+	static registerOn(program: Command): Command {
+		const contextCommand = new ContextCommand();
+		program.addCommand(contextCommand);
+		return contextCommand;
+	}
+
+	/**
+	 * Alternative registration that returns the command for chaining
 	 */
 	static register(program: Command, name?: string): ContextCommand {
 		const contextCommand = new ContextCommand(name);
--- a/apps/cli/src/commands/export.command.ts
+++ b/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 = 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;
-	}
-}
--- a/apps/cli/src/commands/list.command.ts
+++ b/apps/cli/src/commands/list.command.ts
@@ -246,7 +246,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)}`
 					);
 				});
 			}
@@ -281,14 +281,9 @@ export class ListTasksCommand extends Command {
 		const priorityBreakdown = getPriorityBreakdown(tasks);

 		// Find next task following the same logic as findNextTask
-		const nextTaskInfo = this.findNextTask(tasks);
+		const nextTask = 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)
+		// Display dashboard boxes
 		displayDashboards(
 			taskStats,
 			subtaskStats,
@@ -297,7 +292,7 @@ export class ListTasksCommand extends Command {
 			nextTask
 		);

-		// Task table
+		// Task table - no title, just show the table directly
 		console.log(
 			ui.createTaskTable(tasks, {
 				showSubtasks: withSubtasks,
@@ -308,16 +303,14 @@ export class ListTasksCommand extends Command {

 		// Display recommended next task section immediately after table
 		if (nextTask) {
-			const description = getTaskDescription(nextTask);
+			// Find the full task object to get description
+			const fullTask = tasks.find((t) => String(t.id) === String(nextTask.id));
+			const description = fullTask ? getTaskDescription(fullTask) : undefined;

 			displayRecommendedNextTask({
-				id: nextTask.id,
-				title: nextTask.title,
-				priority: nextTask.priority,
-				status: nextTask.status,
-				dependencies: nextTask.dependencies,
-				description,
-				complexity: nextTask.complexity as number | undefined
+				...nextTask,
+				status: 'pending', // Next task is typically pending
+				description
 			});
 		} else {
 			displayRecommendedNextTask(undefined);
@@ -474,7 +467,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);
--- a/apps/cli/src/commands/set-status.command.ts
+++ b/apps/cli/src/commands/set-status.command.ts
@@ -258,6 +258,9 @@ export class SetStatusCommand extends Command {
 				)
 			);
 		}
+
+		// Show storage info
+		console.log(chalk.gray(`\nUsing ${result.storageType} storage`));
 	}

 	/**
@@ -287,7 +290,18 @@ export class SetStatusCommand 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 setStatusCommand = new SetStatusCommand();
+		program.addCommand(setStatusCommand);
+		return setStatusCommand;
+	}
+
+	/**
+	 * Alternative registration that returns the command for chaining
+	 * Can also configure the command name if needed
 	 */
 	static register(program: Command, name?: string): SetStatusCommand {
 		const setStatusCommand = new SetStatusCommand(name);
--- a/apps/cli/src/commands/show.command.ts
+++ b/apps/cli/src/commands/show.command.ts
@@ -322,7 +322,18 @@ export class ShowCommand 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 showCommand = new ShowCommand();
+		program.addCommand(showCommand);
+		return showCommand;
+	}
+
+	/**
+	 * Alternative registration that returns the command for chaining
+	 * Can also configure the command name if needed
 	 */
 	static register(program: Command, name?: string): ShowCommand {
 		const showCommand = new ShowCommand(name);
--- a/apps/cli/src/commands/start.command.ts
+++ b/apps/cli/src/commands/start.command.ts
@@ -493,7 +493,16 @@ export class StartCommand extends Command {
 	}

 	/**
-	 * Register this command on an existing program
+	 * Static method to register this command on an existing program
+	 */
+	static registerOn(program: Command): Command {
+		const startCommand = new StartCommand();
+		program.addCommand(startCommand);
+		return startCommand;
+	}
+
+	/**
+	 * Alternative registration that returns the command for chaining
 	 */
 	static register(program: Command, name?: string): StartCommand {
 		const startCommand = new StartCommand(name);
--- a/apps/cli/src/index.ts
+++ b/apps/cli/src/index.ts
@@ -10,15 +10,6 @@ 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';
@@ -27,8 +18,7 @@ export * as ui from './utils/ui.js';
 export {
 	checkForUpdate,
 	performAutoUpdate,
-	displayUpgradeNotification,
-	compareVersions
+	displayUpgradeNotification
 } from './utils/auto-update.js';

 // Re-export commonly used types from tm-core
--- a/apps/cli/src/ui/components/dashboard.component.ts
+++ b/apps/cli/src/ui/components/dashboard.component.ts
@@ -6,7 +6,6 @@
 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
@@ -480,7 +479,7 @@ export function displayDependencyDashboard(
 				? chalk.cyan(nextTask.dependencies.join(', '))
 				: chalk.gray('None')
 		}\n` +
-		`Complexity: ${nextTask?.complexity !== undefined ? getComplexityWithColor(nextTask.complexity) : chalk.gray('N/A')}`;
+		`Complexity: ${nextTask?.complexity || chalk.gray('N/A')}`;

 	return content;
 }
--- a/apps/cli/src/ui/components/next-task.component.ts
+++ b/apps/cli/src/ui/components/next-task.component.ts
@@ -6,7 +6,6 @@
 import chalk from 'chalk';
 import boxen from 'boxen';
 import type { Task } from '@tm/core/types';
-import { getComplexityWithColor } from '../../utils/ui.js';

 /**
 * Next task display options
@@ -18,7 +17,6 @@ export interface NextTaskDisplayOptions {
 	status?: string;
 	dependencies?: (string | number)[];
 	description?: string;
-	complexity?: number;
 }

 /**
@@ -84,11 +82,6 @@ export function displayRecommendedNextTask(
 			: chalk.cyan(task.dependencies.join(', '));
 	content.push(`Dependencies: ${depsDisplay}`);

-	// Complexity with color and label
-	if (typeof task.complexity === 'number') {
-		content.push(`Complexity: ${getComplexityWithColor(task.complexity)}`);
-	}
-
 	// Description if available
 	if (task.description) {
 		content.push('');
--- a/apps/cli/src/ui/components/task-detail.component.ts
+++ b/apps/cli/src/ui/components/task-detail.component.ts
@@ -9,11 +9,7 @@ import Table from 'cli-table3';
 import { marked, MarkedExtension } from 'marked';
 import { markedTerminal } from 'marked-terminal';
 import type { Task } from '@tm/core/types';
-import {
-	getStatusWithColor,
-	getPriorityWithColor,
-	getComplexityWithColor
-} from '../../utils/ui.js';
+import { getStatusWithColor, getPriorityWithColor } from '../../utils/ui.js';

 // Configure marked to use terminal renderer with subtle colors
 marked.use(
@@ -112,9 +108,7 @@ export function displayTaskProperties(task: Task): void {
 		getStatusWithColor(task.status),
 		getPriorityWithColor(task.priority),
 		deps,
-		typeof task.complexity === 'number'
-			? getComplexityWithColor(task.complexity)
-			: chalk.gray('N/A'),
+		'N/A',
 		task.description || ''
 	].join('\n');

@@ -192,7 +186,8 @@ export function displaySubtasks(
 		status: any;
 		description?: string;
 		dependencies?: string[];
-	}>
+	}>,
+	parentId: string | number
 ): void {
 	const terminalWidth = process.stdout.columns * 0.95 || 100;
 	// Display subtasks header
@@ -227,7 +222,7 @@ export function displaySubtasks(
 	});

 	subtasks.forEach((subtask) => {
-		const subtaskId = String(subtask.id);
+		const subtaskId = `${parentId}.${subtask.id}`;

 		// Format dependencies
 		const deps =
@@ -328,7 +323,7 @@ export function displayTaskDetails(
 			console.log(chalk.gray(`  No subtasks with status '${statusFilter}'`));
 		} else if (filteredSubtasks.length > 0) {
 			console.log(); // Empty line for spacing
-			displaySubtasks(filteredSubtasks);
+			displaySubtasks(filteredSubtasks, task.id);
 		}
 	}

--- a/apps/cli/src/utils/auto-update.ts
+++ b/apps/cli/src/utils/auto-update.ts
@@ -7,27 +7,24 @@ import https from 'https';
 import chalk from 'chalk';
 import ora from 'ora';
 import boxen from 'boxen';
+import packageJson from '../../../../package.json' with { type: 'json' };

 export interface UpdateInfo {
 	currentVersion: string;
 	latestVersion: string;
 	needsUpdate: boolean;
-	highlights?: string[];
 }

 /**
- * Get current version from build-time injected environment variable
+ * Get current version from package.json
 */
 function getCurrentVersion(): string {
-	// Version is injected at build time via TM_PUBLIC_VERSION
-	const version = process.env.TM_PUBLIC_VERSION;
-	if (version && version !== 'unknown') {
-		return version;
+	try {
+		return packageJson.version;
+	} catch (error) {
+		console.warn('Could not read package.json for version info');
+		return '0.0.0';
 	}
-
-	// Fallback for development or if injection failed
-	console.warn('Could not read version from TM_PUBLIC_VERSION, using fallback');
-	return '0.0.0';
 }

 /**
@@ -36,7 +33,7 @@ function getCurrentVersion(): string {
 * @param v2 - Second version
 * @returns -1 if v1 < v2, 0 if v1 = v2, 1 if v1 > v2
 */
-export function compareVersions(v1: string, v2: string): number {
+function compareVersions(v1: string, v2: string): number {
 	const toParts = (v: string) => {
 		const [core, pre = ''] = v.split('-', 2);
 		const nums = core.split('.').map((n) => Number.parseInt(n, 10) || 0);
@@ -60,116 +57,6 @@ export function compareVersions(v1: string, v2: string): number {
 	return a.pre < b.pre ? -1 : 1; // basic prerelease tie-break
 }

-/**
- * Fetch CHANGELOG.md from GitHub and extract highlights for a specific version
- */
-async function fetchChangelogHighlights(version: string): Promise<string[]> {
-	return new Promise((resolve) => {
-		const options = {
-			hostname: 'raw.githubusercontent.com',
-			path: '/eyaltoledano/claude-task-master/main/CHANGELOG.md',
-			method: 'GET',
-			headers: {
-				'User-Agent': `task-master-ai/${version}`
-			}
-		};
-
-		const req = https.request(options, (res) => {
-			let data = '';
-
-			res.on('data', (chunk) => {
-				data += chunk;
-			});
-
-			res.on('end', () => {
-				try {
-					if (res.statusCode !== 200) {
-						resolve([]);
-						return;
-					}
-
-					const highlights = parseChangelogHighlights(data, version);
-					resolve(highlights);
-				} catch (error) {
-					resolve([]);
-				}
-			});
-		});
-
-		req.on('error', () => {
-			resolve([]);
-		});
-
-		req.setTimeout(3000, () => {
-			req.destroy();
-			resolve([]);
-		});
-
-		req.end();
-	});
-}
-
-/**
- * Parse changelog markdown to extract Minor Changes for a specific version
- * @internal - Exported for testing purposes only
- */
-export function parseChangelogHighlights(
-	changelog: string,
-	version: string
-): string[] {
-	try {
-		// Validate version format (basic semver pattern) to prevent ReDoS
-		if (!/^\d+\.\d+\.\d+(-[a-zA-Z0-9.-]+)?$/.test(version)) {
-			return [];
-		}
-
-		// Find the version section
-		const versionRegex = new RegExp(
-			`## ${version.replace(/\./g, '\\.')}\\s*\\n`,
-			'i'
-		);
-		const versionMatch = changelog.match(versionRegex);
-
-		if (!versionMatch) {
-			return [];
-		}
-
-		// Extract content from this version to the next version heading
-		const startIdx = versionMatch.index! + versionMatch[0].length;
-		const nextVersionIdx = changelog.indexOf('\n## ', startIdx);
-		const versionContent =
-			nextVersionIdx > 0
-				? changelog.slice(startIdx, nextVersionIdx)
-				: changelog.slice(startIdx);
-
-		// Find Minor Changes section
-		const minorChangesMatch = versionContent.match(
-			/### Minor Changes\s*\n([\s\S]*?)(?=\n###|\n##|$)/i
-		);
-
-		if (!minorChangesMatch) {
-			return [];
-		}
-
-		const minorChangesContent = minorChangesMatch[1];
-		const highlights: string[] = [];
-
-		// Extract all bullet points (lines starting with -)
-		// Format: - [#PR](...) Thanks [@author]! - Description
-		const bulletRegex = /^-\s+\[#\d+\][^\n]*?!\s+-\s+(.+?)$/gm;
-		let match;
-
-		while ((match = bulletRegex.exec(minorChangesContent)) !== null) {
-			const desc = match[1].trim();
-			highlights.push(desc);
-		}
-
-		return highlights;
-	} catch (error) {
-		return [];
-	}
-}
-
 /**
 * Check for newer version of task-master-ai
 */
@@ -196,7 +83,7 @@ export async function checkForUpdate(
 				data += chunk;
 			});

-			res.on('end', async () => {
+			res.on('end', () => {
 				try {
 					if (res.statusCode !== 200)
 						throw new Error(`npm registry status ${res.statusCode}`);
@@ -206,17 +93,10 @@ export async function checkForUpdate(
 					const needsUpdate =
 						compareVersions(currentVersion, latestVersion) < 0;

-					// Fetch highlights if update is needed
-					let highlights: string[] | undefined;
-					if (needsUpdate) {
-						highlights = await fetchChangelogHighlights(latestVersion);
-					}
-
 					resolve({
 						currentVersion,
 						latestVersion,
-						needsUpdate,
-						highlights
+						needsUpdate
 					});
 				} catch (error) {
 					resolve({
@@ -254,29 +134,18 @@ export async function checkForUpdate(
 */
 export function displayUpgradeNotification(
 	currentVersion: string,
-	latestVersion: string,
-	highlights?: string[]
+	latestVersion: string
 ) {
-	let content = `${chalk.blue.bold('Update Available!')} ${chalk.dim(currentVersion)} → ${chalk.green(latestVersion)}`;
-
-	if (highlights && highlights.length > 0) {
-		content += '\n\n' + chalk.bold("What's New:");
-		for (const highlight of highlights) {
-			content += '\n' + chalk.cyan('• ') + highlight;
+	const message = boxen(
+		`${chalk.blue.bold('Update Available!')} ${chalk.dim(currentVersion)} → ${chalk.green(latestVersion)}\n\n` +
+			`Auto-updating to the latest version with new features and bug fixes...`,
+		{
+			padding: 1,
+			margin: { top: 1, bottom: 1 },
+			borderColor: 'yellow',
+			borderStyle: 'round'
 		}
-		content += '\n\n' + 'Auto-updating to the latest version...';
-	} else {
-		content +=
-			'\n\n' +
-			'Auto-updating to the latest version with new features and bug fixes...';
-	}
-
-	const message = boxen(content, {
-		padding: 1,
-		margin: { top: 1, bottom: 1 },
-		borderColor: 'yellow',
-		borderStyle: 'round'
-	});
+	);

 	console.log(message);
 }
@@ -287,18 +156,10 @@ export function displayUpgradeNotification(
 export async function performAutoUpdate(
 	latestVersion: string
 ): Promise<boolean> {
-	if (
-		process.env.TASKMASTER_SKIP_AUTO_UPDATE === '1' ||
-		process.env.CI ||
-		process.env.NODE_ENV === 'test'
-	) {
-		const reason =
-			process.env.TASKMASTER_SKIP_AUTO_UPDATE === '1'
-				? 'TASKMASTER_SKIP_AUTO_UPDATE=1'
-				: process.env.CI
-					? 'CI environment'
-					: 'NODE_ENV=test';
-		console.log(chalk.dim(`Skipping auto-update (${reason})`));
+	if (process.env.TASKMASTER_SKIP_AUTO_UPDATE === '1' || process.env.CI) {
+		console.log(
+			chalk.dim('Skipping auto-update (TASKMASTER_SKIP_AUTO_UPDATE/CI).')
+		);
 		return false;
 	}
 	const spinner = ora({
--- a/apps/cli/src/utils/ui.ts
+++ b/apps/cli/src/utils/ui.ts
@@ -84,23 +84,7 @@ export function getPriorityWithColor(priority: TaskPriority): string {
 }

 /**
- * Get complexity color and label based on score thresholds
- */
-function getComplexityLevel(score: number): {
-	color: (text: string) => string;
-	label: string;
-} {
-	if (score >= 7) {
-		return { color: chalk.hex('#CC0000'), label: 'High' };
-	} else if (score >= 4) {
-		return { color: chalk.hex('#FF8800'), label: 'Medium' };
-	} else {
-		return { color: chalk.green, label: 'Low' };
-	}
-}
-
-/**
- * Get colored complexity display with dot indicator (simple format)
+ * Get colored complexity display
 */
 export function getComplexityWithColor(complexity: number | string): string {
 	const score =
@@ -110,20 +94,13 @@ export function getComplexityWithColor(complexity: number | string): string {
 		return chalk.gray('N/A');
 	}

-	const { color } = getComplexityLevel(score);
-	return color(`● ${score}`);
-}
-
-/**
- * Get colored complexity display with /10 format (for dashboards)
- */
-export function getComplexityWithScore(complexity: number | undefined): string {
-	if (typeof complexity !== 'number') {
-		return chalk.gray('N/A');
+	if (score >= 8) {
+		return chalk.red.bold(`${score} (High)`);
+	} else if (score >= 5) {
+		return chalk.yellow(`${score} (Medium)`);
+	} else {
+		return chalk.green(`${score} (Low)`);
 	}
-
-	const { color, label } = getComplexityLevel(complexity);
-	return color(`${complexity}/10 (${label})`);
 }

 /**
@@ -286,12 +263,12 @@ export function createTaskTable(
 	// Adjust column widths to better match the original layout
 	const baseColWidths = showComplexity
 		? [
-				Math.floor(terminalWidth * 0.1),
+				Math.floor(terminalWidth * 0.06),
 				Math.floor(terminalWidth * 0.4),
 				Math.floor(terminalWidth * 0.15),
-				Math.floor(terminalWidth * 0.1),
+				Math.floor(terminalWidth * 0.12),
 				Math.floor(terminalWidth * 0.2),
-				Math.floor(terminalWidth * 0.1)
+				Math.floor(terminalWidth * 0.12)
 			] // ID, Title, Status, Priority, Dependencies, Complexity
 		: [
 				Math.floor(terminalWidth * 0.08),
@@ -346,12 +323,8 @@ export function createTaskTable(
 		}

 		if (showComplexity) {
-			// Show complexity score from report if available
-			if (typeof task.complexity === 'number') {
-				row.push(getComplexityWithColor(task.complexity));
-			} else {
-				row.push(chalk.gray('N/A'));
-			}
+			// Show N/A if no complexity score
+			row.push(chalk.gray('N/A'));
 		}

 		table.push(row);
@@ -377,11 +350,7 @@ export function createTaskTable(
 				}

 				if (showComplexity) {
-					const complexityDisplay =
-						typeof subtask.complexity === 'number'
-							? getComplexityWithColor(subtask.complexity)
-							: '--';
-					subRow.push(chalk.gray(complexityDisplay));
+					subRow.push(chalk.gray('--'));
 				}

 				table.push(subRow);
--- a/apps/docs/CHANGELOG.md
+++ b/apps/docs/CHANGELOG.md
@@ -1,9 +1,5 @@
 # docs

-## 0.0.5
-
-## 0.0.4
-
 ## 0.0.3

 ## 0.0.2
--- a/apps/docs/README.md
+++ b/apps/docs/README.md
@@ -1,24 +1,22 @@
 # Task Master Documentation

-Welcome to the Task Master documentation. This documentation site provides comprehensive guides for getting started with Task Master.
+Welcome to the Task Master documentation. Use the links below to navigate to the information you need:

 ## Getting Started

- [Quick Start Guide](/getting-started/quick-start) - Complete setup and first-time usage guide
- [Requirements](/getting-started/quick-start/requirements) - What you need to get started
- [Installation](/getting-started/quick-start/installation) - How to install Task Master
+- [Configuration Guide](archive/configuration.md) - Set up environment variables and customize Task Master
+- [Tutorial](archive/ctutorial.md) - Step-by-step guide to getting started with Task Master

-## Core Capabilities
+## Reference

- [MCP Tools](/capabilities/mcp) - Model Control Protocol integration
- [CLI Commands](/capabilities/cli-root-commands) - Command line interface reference
- [Task Structure](/capabilities/task-structure) - Understanding tasks and subtasks
+- [Command Reference](archive/ccommand-reference.md) - Complete list of all available commands
+- [Task Structure](archive/ctask-structure.md) - Understanding the task format and features

-## Best Practices
+## Examples & Licensing

- [Advanced Configuration](/best-practices/configuration-advanced) - Detailed configuration options
- [Advanced Tasks](/best-practices/advanced-tasks) - Working with complex task structures
+- [Example Interactions](archive/cexamples.md) - Common Cursor AI interaction examples
+- [Licensing Information](archive/clicensing.md) - Detailed information about the license

 ## Need More Help?

-If you can't find what you're looking for in these docs, please check the root README.md or visit our [GitHub repository](https://github.com/eyaltoledano/claude-task-master).
+If you can't find what you're looking for in these docs, please check the [main README](../README.md) or visit our [GitHub repository](https://github.com/eyaltoledano/claude-task-master).
--- a/apps/docs/archive/ai-development-workflow.mdx
+++ b/apps/docs/archive/ai-development-workflow.mdx
@@ -118,7 +118,7 @@ description: "Learn how Task Master and Cursor AI work together to streamline yo
    task-master expand --all
    ```

-    For research-backed subtask generation using Perplexity AI:
+    For research-backed subtask generation using configured research model:

    ```
    Please break down task 5 using research-backed generation.
--- a/apps/docs/archive/command-reference.mdx
+++ b/apps/docs/archive/command-reference.mdx
@@ -61,7 +61,7 @@ description: "A comprehensive reference of all available Task Master commands"
    # Update a single task by ID with new information
    task-master update-task --id=<id> --prompt="<prompt>"

-    # Use research-backed updates with Perplexity AI
+    # Use research-backed updates with configured research model
    task-master update-task --id=<id> --prompt="<prompt>" --research
    ```
  </Accordion>
@@ -74,7 +74,7 @@ description: "A comprehensive reference of all available Task Master commands"
    # Example: Add details about API rate limiting to subtask 2 of task 5
    task-master update-subtask --id=5.2 --prompt="Add rate limiting of 100 requests per minute"

-    # Use research-backed updates with Perplexity AI
+    # Use research-backed updates with configured research model
    task-master update-subtask --id=<parentId.subtaskId> --prompt="<prompt>" --research
    ```

@@ -155,7 +155,7 @@ description: "A comprehensive reference of all available Task Master commands"
    # Use an alternative tasks file
    task-master analyze-complexity --file=custom-tasks.json

-    # Use Perplexity AI for research-backed complexity analysis
+    # Use configured research model for research-backed complexity analysis
    task-master analyze-complexity --research
    ```
  </Accordion>
--- a/apps/docs/capabilities/rpg-method.mdx
+++ b/apps/docs/capabilities/rpg-method.mdx
@@ -1,326 +0,0 @@
---
-title: RPG Method for PRD Creation
-sidebarTitle: "RPG Method"
---
-
-# Repository Planning Graph (RPG) Method
-
-The RPG (Repository Planning Graph) method is an advanced approach to creating Product Requirements Documents that generate highly-structured, dependency-aware task graphs. It's based on Microsoft Research's methodology for scalable codebase generation.
-
-## When to Use RPG
-
-Use the RPG template (`example_prd_rpg.txt`) for:
-
- **Complex multi-module systems** with intricate dependencies
- **Large-scale codebases** being built from scratch
- **Projects requiring explicit architecture** and clear module boundaries
- **Teams needing dependency visibility** for parallel development
-
-For simpler features or smaller projects, the standard `example_prd.txt` template may be more appropriate.
-
---
-
-## Core Principles
-
-### 1. Dual-Semantics
-
-Separate **functional** thinking (WHAT) from **structural** thinking (HOW):
-
-```
-Functional: "Data Validation capability with schema checking and rule enforcement"
-                    ↓
-Structural: "src/validation/ with schema-validator.js and rule-validator.js"
-```
-
-This separation prevents mixing concerns and creates clearer module boundaries.
-
-### 2. Explicit Dependencies
-
-Never assume dependencies - always state them explicitly:
-
-```
-Good:
-  Module: data-ingestion
-  Depends on: [schema-validator, config-manager]
-
-Bad:
-  Module: data-ingestion
-  (Assumes schema-validator exists somewhere)
-```
-
-Explicit dependencies enable:
- Topological ordering of implementation
- Parallel development of independent modules
- Clear build/test order
- Early detection of circular dependencies
-
-### 3. Topological Order
-
-Build foundation layers before higher layers:
-
-```
-Phase 0 (Foundation): error-handling, base-types, config
-                ↓
-Phase 1 (Data): validation, ingestion (depend on Phase 0)
-                ↓
-Phase 2 (Core): algorithms, pipelines (depend on Phase 1)
-                ↓
-Phase 3 (API): routes, handlers (depend on Phase 2)
-```
-
-Task Master automatically orders tasks based on this dependency chain.
-
-### 4. Progressive Refinement
-
-Start broad, refine iteratively:
-
-1. High-level capabilities → Main tasks
-2. Features per capability → Subtasks
-3. Implementation details → Expanded subtasks
-
---
-
-## Template Structure
-
-The RPG template guides you through 7 key sections:
-
-### 1. Overview
- Problem statement
- Target users
- Success metrics
-
-### 2. Functional Decomposition (WHAT)
- High-level capability domains
- Features per capability
- Inputs/outputs/behavior for each feature
-
-**Example:**
-```
-Capability: Data Management
-  Feature: Schema validation
-    Description: Validate JSON against defined schemas
-    Inputs: JSON object, schema definition
-    Outputs: Validation result + error details
-    Behavior: Iterate fields, check types, enforce constraints
-```
-
-### 3. Structural Decomposition (HOW)
- Repository folder structure
- Module-to-capability mapping
- File organization
- Public interfaces/exports
-
-**Example:**
-```
-Capability: Data Management
-  → Maps to: src/data/
-    ├── schema-validator.js    (Schema validation feature)
-    ├── rule-validator.js      (Rule validation feature)
-    └── index.js               (Exports)
-```
-
-### 4. Dependency Graph (CRITICAL)
- Foundation layer (no dependencies)
- Each subsequent layer's dependencies
- Explicit "depends on" declarations
-
-**Example:**
-```
-Foundation Layer (Phase 0):
-  - error-handling: No dependencies
-  - base-types: No dependencies
-
-Data Layer (Phase 1):
-  - schema-validator: Depends on [base-types, error-handling]
-  - data-ingestion: Depends on [schema-validator]
-```
-
-### 5. Implementation Roadmap
- Phases with entry/exit criteria
- Tasks grouped by phase
- Clear deliverables per phase
-
-### 6. Test Strategy
- Test pyramid ratios
- Coverage requirements
- Critical test scenarios per module
- Guidelines for test generation
-
-### 7. Architecture & Risks
- Technical architecture
- Data models
- Technology decisions
- Risk mitigation strategies
-
---
-
-## Using RPG with Task Master
-
-### Step 1: Create PRD with RPG Template
-
-Use a code-context-aware tool to fill out the template:
-
-```bash
-# In Claude Code, Cursor, or similar
-"Create a PRD using @.taskmaster/templates/example_prd_rpg.txt for [your project]"
-```
-
-**Why code context matters:** The AI needs to understand your existing codebase to make informed decisions about:
- Module boundaries
- Dependency relationships
- Integration points
- Naming conventions
-
-**Recommended tools:**
- Claude Code (claude-code CLI)
- Cursor/Windsurf
- Gemini CLI (large contexts)
- Codex/Grok CLI
-
-### Step 2: Parse PRD into Tasks
-
-```bash
-task-master parse-prd .taskmaster/docs/your-prd.txt --research
-```
-
-Task Master will:
-1. Extract capabilities → Main tasks
-2. Extract features → Subtasks
-3. Parse dependencies → Task dependencies
-4. Order by phases → Task priorities
-
-**Result:** A dependency-aware task graph ready for topological execution.
-
-### Step 3: Analyze Complexity
-
-```bash
-task-master analyze-complexity --research
-```
-
-Review the complexity report to identify tasks that need expansion.
-
-### Step 4: Expand Tasks
-
-```bash
-task-master expand --all --research
-```
-
-Break down complex tasks into manageable subtasks while preserving dependency chains.
-
---
-
-## RPG Benefits
-
-### For Solo Developers
- Clear roadmap for implementing complex features
- Prevents architectural mistakes early
- Explicit dependency tracking avoids integration issues
- Enables resuming work after interruptions
-
-### For Teams
- Parallel development of independent modules
- Clear contracts between modules (explicit dependencies)
- Reduced merge conflicts (proper module boundaries)
- Onboarding aid (architectural overview in PRD)
-
-### For AI Agents
- Structured context for code generation
- Clear scope boundaries per task
- Dependency awareness prevents incomplete implementations
- Test strategy guidance for TDD workflows
-
---
-
-## RPG vs Standard Template
-
-| Aspect | Standard Template | RPG Template |
-|--------|------------------|--------------|
-| **Best for** | Simple features | Complex systems |
-| **Dependency handling** | Implicit | Explicit graph |
-| **Structure guidance** | Minimal | Step-by-step |
-| **Examples** | Few | Inline good/bad examples |
-| **Module boundaries** | Vague | Precise mapping |
-| **Task ordering** | Manual | Automatic (topological) |
-| **Learning curve** | Low | Medium |
-| **Resulting task quality** | Good | Excellent |
-
---
-
-## Tips for Best Results
-
-### 1. Spend Time on Dependencies
-The dependency graph section is the most valuable. List all dependencies explicitly, even if they seem obvious.
-
-### 2. Keep Features Atomic
-Each feature should be independently testable. If a feature description is vague ("handle data"), break it into specific features.
-
-### 3. Progressive Refinement
-Don't try to get everything perfect on the first pass:
-1. Fill out high-level sections
-2. Review and refine
-3. Add detail where needed
-4. Let `task-master expand` break down complex tasks further
-
-### 4. Use Research Mode
-```bash
-task-master parse-prd --research
-```
-The `--research` flag leverages AI to enhance task generation with domain knowledge.
-
-### 5. Validate Early
-```bash
-task-master validate-dependencies
-```
-Check for circular dependencies or orphaned modules before starting implementation.
-
---
-
-## Common Pitfalls
-
-### ❌ Mixing Functional and Structural
-```
-Bad: "Capability: validation.js"
-Good: "Capability: Data Validation" → maps to "src/validation/"
-```
-
-### ❌ Vague Module Boundaries
-```
-Bad: "Module: utils"
-Good: "Module: string-utilities" with clear exports
-```
-
-### ❌ Implicit Dependencies
-```
-Bad: "Module: API handlers (needs validation)"
-Good: "Module: API handlers, Depends on: [validation, error-handling]"
-```
-
-### ❌ Skipping Test Strategy
-Without test strategy, the AI won't know what to test during implementation.
-
---
-
-## Example Workflow
-
-1. **Discuss idea with AI**: Explain your project concept
-2. **Reference RPG template**: Show AI the `example_prd_rpg.txt`
-3. **Co-create PRD**: Work through each section with AI guidance
-4. **Save to docs**: Place in `.taskmaster/docs/your-project.txt`
-5. **Parse PRD**: `task-master parse-prd .taskmaster/docs/your-project.txt --research`
-6. **Analyze**: `task-master analyze-complexity --research`
-7. **Expand**: `task-master expand --all --research`
-8. **Start work**: `task-master next`
-
---
-
-## Further Reading
-
- [PRD Creation and Parsing Guide](/getting-started/quick-start/prd-quick)
- [Task Structure Documentation](/capabilities/task-structure)
- [Microsoft Research RPG Paper](https://arxiv.org/abs/2410.21376) (Original methodology)
-
---
-
-<Tip>
-The RPG template includes inline `<instruction>` and `<example>` blocks that teach the method as you use it. Read these sections carefully - they provide valuable guidance at each decision point.
-</Tip>
--- a/apps/docs/docs.json
+++ b/apps/docs/docs.json
@@ -32,7 +32,6 @@
 									"getting-started/quick-start/execute-quick"
 								]
 							},
-							"getting-started/api-keys",
 							"getting-started/faq",
 							"getting-started/contribute"
 						]
--- a/apps/docs/getting-started/api-keys.mdx
+++ b/apps/docs/getting-started/api-keys.mdx
@@ -1,267 +0,0 @@
-# API Keys Configuration
-
-Task Master supports multiple AI providers through environment variables. This page lists all available API keys and their configuration requirements.
-
-## Required API Keys
-
-> **Note**: At least one required API key must be configured for Task Master to function.
->
-> "Required: Yes" below means "required to use that specific provider," not "required globally." You only need at least one provider configured.
-
-### ANTHROPIC_API_KEY (Recommended)
- **Provider**: Anthropic Claude models
- **Format**: `sk-ant-api03-...`
- **Required**: ✅ **Yes**
- **Models**: Claude 3.5 Sonnet, Claude 3 Haiku, Claude 3 Opus
- **Get Key**: [Anthropic Console](https://console.anthropic.com/)
-
-```bash
-ANTHROPIC_API_KEY="sk-ant-api03-your-key-here"
-```
-
-### PERPLEXITY_API_KEY (Highly Recommended for Research)
- **Provider**: Perplexity AI (Research features)
- **Format**: `pplx-...`
- **Required**: ✅ **Yes**
- **Purpose**: Enables research-backed task expansions and updates
- **Models**: Perplexity Sonar models
- **Get Key**: [Perplexity API](https://www.perplexity.ai/settings/api)
-
-```bash
-PERPLEXITY_API_KEY="pplx-your-key-here"
-```
-
-### OPENAI_API_KEY
- **Provider**: OpenAI GPT models
- **Format**: `sk-proj-...` or `sk-...`
- **Required**: ✅ **Yes**
- **Models**: GPT-4, GPT-4 Turbo, GPT-3.5 Turbo, O1 models
- **Get Key**: [OpenAI Platform](https://platform.openai.com/api-keys)
-
-```bash
-OPENAI_API_KEY="sk-proj-your-key-here"
-```
-
-### GOOGLE_API_KEY
- **Provider**: Google Gemini models
- **Format**: Various formats
- **Required**: ✅ **Yes**
- **Models**: Gemini Pro, Gemini Flash, Gemini Ultra
- **Get Key**: [Google AI Studio](https://aistudio.google.com/app/apikey)
- **Alternative**: Use `GOOGLE_APPLICATION_CREDENTIALS` for service account (Google Vertex)
-
-```bash
-GOOGLE_API_KEY="your-google-api-key-here"
-```
-
-### GROQ_API_KEY
- **Provider**: Groq (High-performance inference)
- **Required**: ✅ **Yes**
- **Models**: Llama models, Mixtral models (via Groq)
- **Get Key**: [Groq Console](https://console.groq.com/keys)
-
-```bash
-GROQ_API_KEY="your-groq-key-here"
-```
-
-### OPENROUTER_API_KEY
- **Provider**: OpenRouter (Multiple model access)
- **Required**: ✅ **Yes**
- **Models**: Access to various models through single API
- **Get Key**: [OpenRouter](https://openrouter.ai/keys)
-
-```bash
-OPENROUTER_API_KEY="your-openrouter-key-here"
-```
-
-### AZURE_OPENAI_API_KEY
- **Provider**: Azure OpenAI Service
- **Required**: ✅ **Yes**
- **Requirements**: Also requires `AZURE_OPENAI_ENDPOINT` configuration
- **Models**: GPT models via Azure
- **Get Key**: [Azure Portal](https://portal.azure.com/)
-
-```bash
-AZURE_OPENAI_API_KEY="your-azure-key-here"
-```
-
-### XAI_API_KEY
- **Provider**: xAI (Grok) models
- **Required**: ✅ **Yes**
- **Models**: Grok models
- **Get Key**: [xAI Console](https://console.x.ai/)
-
-```bash
-XAI_API_KEY="your-xai-key-here"
-```
-
-## Optional API Keys
-
-> **Note**: These API keys are optional - providers will work without them or use alternative authentication methods.
-
-### AWS_ACCESS_KEY_ID (Bedrock)
- **Provider**: AWS Bedrock
- **Required**: ❌ **No** (uses AWS credential chain)
- **Models**: Claude models via AWS Bedrock
- **Authentication**: Uses AWS credential chain (profiles, IAM roles, etc.)
- **Get Key**: [AWS Console](https://console.aws.amazon.com/iam/)
-
-```bash
-# Optional - AWS credential chain is preferred
-AWS_ACCESS_KEY_ID="your-aws-access-key"
-AWS_SECRET_ACCESS_KEY="your-aws-secret-key"
-```
-
-### CLAUDE_CODE_API_KEY
- **Provider**: Claude Code CLI
- **Required**: ❌ **No** (uses OAuth tokens)
- **Purpose**: Integration with local Claude Code CLI
- **Authentication**: Uses OAuth tokens, no API key needed
-
-```bash
-# Not typically needed
-CLAUDE_CODE_API_KEY="not-usually-required"
-```
-
-### GEMINI_API_KEY
- **Provider**: Gemini CLI
- **Required**: ❌ **No** (uses OAuth authentication)
- **Purpose**: Integration with Gemini CLI
- **Authentication**: Primarily uses OAuth via CLI, API key is optional
-
-```bash
-# Optional - OAuth via CLI is preferred
-GEMINI_API_KEY="your-gemini-key-here"
-```
-
-### GROK_CLI_API_KEY
- **Provider**: Grok CLI
- **Required**: ❌ **No** (can use CLI config)
- **Purpose**: Integration with Grok CLI
- **Authentication**: Can use Grok CLI's own config file
-
-```bash
-# Optional - CLI config is preferred
-GROK_CLI_API_KEY="your-grok-cli-key"
-```
-
-### OLLAMA_API_KEY
- **Provider**: Ollama (Local/Remote)
- **Required**: ❌ **No** (local installation doesn't need key)
- **Purpose**: For remote Ollama servers that require authentication
- **Requirements**: Only needed for remote servers with authentication
- **Note**: Not needed for local Ollama installations
-
-```bash
-# Only needed for remote Ollama servers
-OLLAMA_API_KEY="your-ollama-api-key-here"
-```
-
-### GITHUB_API_KEY
- **Provider**: GitHub (Import/Export features)
- **Format**: `ghp_...` or `github_pat_...`
- **Required**: ❌ **No** (for GitHub features only)
- **Purpose**: GitHub import/export features
- **Get Key**: [GitHub Settings](https://github.com/settings/tokens)
-
-```bash
-GITHUB_API_KEY="ghp-your-github-key-here"
-```
-
-## Configuration Methods
-
-### Method 1: Environment File (.env)
-Create a `.env` file in your project root:
-
-```bash
-# Copy from .env.example
-cp .env.example .env
-
-# Edit with your keys
-vim .env
-```
-
-### Method 2: System Environment Variables
-```bash
-export ANTHROPIC_API_KEY="your-key-here"
-export PERPLEXITY_API_KEY="your-key-here"
-# ... other keys
-```
-
-### Method 3: MCP Server Configuration
-For Claude Code integration, configure keys in `.mcp.json`:
-
-```json
-{
-  "mcpServers": {
-    "task-master-ai": {
-      "command": "npx",
-      "args": ["-y", "task-master-ai"],
-      "env": {
-        "ANTHROPIC_API_KEY": "your-key-here",
-        "PERPLEXITY_API_KEY": "your-key-here",
-        "OPENAI_API_KEY": "your-key-here"
-      }
-    }
-  }
-}
-```
-
-## Key Requirements
-
-### Minimum Requirements
- **At least one** AI provider key is required
- **ANTHROPIC_API_KEY** is recommended as the primary provider
- **PERPLEXITY_API_KEY** is highly recommended for research features
-
-### Provider-Specific Requirements
- **Azure OpenAI**: Requires both `AZURE_OPENAI_API_KEY` and `AZURE_OPENAI_ENDPOINT` configuration
- **Google Vertex**: Requires `VERTEX_PROJECT_ID` and `VERTEX_LOCATION` environment variables
- **AWS Bedrock**: Uses AWS credential chain (profiles, IAM roles, etc.) instead of API keys
- **Ollama**: Only needs API key for remote servers with authentication
- **CLI Providers**: Gemini CLI, Grok CLI, and Claude Code use OAuth/CLI config instead of API keys
-
-## Model Configuration
-
-After setting up API keys, configure which models to use:
-
-```bash
-# Interactive model setup
-task-master models --setup
-
-# Set specific models
-task-master models --set-main claude-3-5-sonnet-20241022
-task-master models --set-research perplexity-llama-3.1-sonar-large-128k-online
-task-master models --set-fallback gpt-4o-mini
-```
-
-## Security Best Practices
-
-1. **Never commit API keys** to version control
-2. **Use .env files** and add them to `.gitignore`
-3. **Rotate keys regularly** especially if compromised
-4. **Use minimal permissions** for service accounts
-5. **Monitor usage** to detect unauthorized access
-
-## Troubleshooting
-
-### Key Validation
-```bash
-# Check if keys are properly configured
-task-master models
-
-# Test specific provider
-task-master add-task --prompt="test task" --model=claude-3-5-sonnet-20241022
-```
-
-### Common Issues
- **Invalid key format**: Check the expected format for each provider
- **Insufficient permissions**: Ensure keys have necessary API access
- **Rate limits**: Some providers have usage limits
- **Regional restrictions**: Some models may not be available in all regions
-
-### Getting Help
-If you encounter issues with API key configuration:
- Check the [FAQ](/getting-started/faq) for common solutions
- Join our [Discord community](https://discord.gg/fWJkU7rf) for support
- Report issues on [GitHub](https://github.com/eyaltoledano/claude-task-master/issues)
--- a/apps/docs/getting-started/quick-start/configuration-quick.mdx
+++ b/apps/docs/getting-started/quick-start/configuration-quick.mdx
@@ -108,5 +108,5 @@ You don’t need to configure everything up front. Most settings can be left as
 </Accordion>

 <Note>
-For advanced configuration options and detailed customization, see our [Advanced Configuration Guide](/best-practices/configuration-advanced) page.
+For advanced configuration options and detailed customization, see our [Advanced Configuration Guide](/docs/best-practices/configuration-advanced) page.
 </Note>
--- a/apps/docs/getting-started/quick-start/execute-quick.mdx
+++ b/apps/docs/getting-started/quick-start/execute-quick.mdx
@@ -56,4 +56,4 @@ If you ran into problems and had to debug errors you can create new rules as you

 By now you have all you need to get started executing code faster and smarter with Task Master.

-If you have any questions please check out [Frequently Asked Questions](/getting-started/faq)
+If you have any questions please check out [Frequently Asked Questions](/docs/getting-started/faq)
--- a/Show More
+++ b/Show More