chore: apply requested changes

Move git utilities from scripts/modules/utils/git-utils.js to packages/tm-core/src/utils/git-utils.ts for better type safety and reusability.

## Changes

**New File**: `packages/tm-core/src/utils/git-utils.ts`
- Converted from JavaScript to TypeScript with full type annotations
- Added `GitHubRepoInfo` interface for type safety
- Includes all essential git functions needed for Phase 1:
  - `isGitRepository`, `isGitRepositorySync`
  - `getCurrentBranch`, `getCurrentBranchSync`
  - `getLocalBranches`, `getRemoteBranches`
  - `isGhCliAvailable`, `getGitHubRepoInfo`
  - `getDefaultBranch`, `isOnDefaultBranch`
  - `sanitizeBranchNameForTag`, `isValidBranchForTag`

**Updated Files**:
- `preflight-checker.service.ts`: Now imports from local git-utils
- `packages/tm-core/src/utils/index.ts`: Exports git utilities

## Rationale

Phase 1 will need git operations for:
- Creating feature branches (WorkflowOrchestrator)
- Checking git status before execution
- Validating clean working tree
- Branch naming validation

Having these utilities in tm-core provides:
- Type safety (no more `require()` hacks)
- Better testability
- Cleaner imports
- Reusability across services

## Verification

✅ All tests pass (1298 passed, 121 test suites)
✅ Typecheck passes (5/5 successful)
✅ Build successful

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

.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.

.changeset/brave-lions-sing.md

@@ -0,0 +1,11 @@
+---
+"task-master-ai": minor
+---
+
+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

.changeset/chore-fix-docs.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Improve `analyze-complexity` cli docs and `--research` flag documentation

.changeset/cursor-slash-commands.md

@@ -0,0 +1,7 @@
+---
+"task-master-ai": minor
+---
+
+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.

.changeset/curvy-weeks-flow.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Change parent task back to "pending" when all subtasks are in "pending" state

.changeset/easy-spiders-wave.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Do a quick fix on build

.changeset/fix-mcp-connection-errors.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+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.

.changeset/fix-mcp-default-tasks-path.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Fix MCP server error when file parameter not provided - now properly constructs default tasks.json path instead of failing with 'tasksJsonPath is required' error.

.changeset/flat-cities-say.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": minor
+---
+
+Added api keys page on docs website: docs.task-master.dev/getting-started/api-keys

.changeset/forty-tables-invite.md

@@ -0,0 +1,10 @@
+---
+"task-master-ai": minor
+---
+
+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

.changeset/gentle-cats-dance.md

@@ -0,0 +1,30 @@
+---
+"task-master-ai": minor
+---
+
+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.

.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.

.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.

.changeset/petite-ideas-grab.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+Fix Claude Code settings validation for pathToClaudeCodeExecutable

.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.

.changeset/pre.json

@@ -0,0 +1,26 @@
+{
+  "mode": "exit",
+  "tag": "rc",
+  "initialVersions": {
+    "task-master-ai": "0.27.3",
+    "docs": "0.0.4",
+    "extension": "0.25.4"
+  },
+  "changesets": [
+    "brave-lions-sing",
+    "chore-fix-docs",
+    "cursor-slash-commands",
+    "curvy-weeks-flow",
+    "easy-spiders-wave",
+    "fix-mcp-connection-errors",
+    "fix-mcp-default-tasks-path",
+    "flat-cities-say",
+    "forty-tables-invite",
+    "gentle-cats-dance",
+    "mcp-timeout-configuration",
+    "petite-ideas-grab",
+    "silly-pandas-find",
+    "sweet-maps-rule",
+    "whole-pigs-say"
+  ]
+}

.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`

.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.

.changeset/sweet-maps-rule.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": minor
+---
+
+Upgrade grok-cli ai provider to ai sdk v5

.changeset/whole-pigs-say.md

@@ -0,0 +1,8 @@
+---
+"task-master-ai": patch
+---
+
+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)

.coderabbit.yaml

@@ -1,10 +1,3 @@
 reviews:
   profile: assertive
   poem: false
-  auto_review:
-    base_branches:
-      - rc
-      - beta
-      - alpha
-      - production
-      - next

.taskmaster/config.json

@@ -1,8 +1,8 @@
 {
 	"models": {
 		"main": {
-			"provider": "anthropic",
-			"modelId": "claude-sonnet-4-20250514",
+			"provider": "claude-code",
+			"modelId": "sonnet",
 			"maxTokens": 64000,
 			"temperature": 0.2
 		},
@@ -35,6 +35,7 @@
 		"defaultTag": "master"
 	},
 	"claudeCode": {},
+	"codexCli": {},
 	"grokCli": {
 		"timeout": 120000,
 		"workingDirectory": null,

.taskmaster/docs/autonomous-tdd-git-workflow.md

@@ -0,0 +1,912 @@
+## Summary
+
+- Put the existing git and test workflows on rails: a repeatable, automated process that can run autonomously, with guardrails and a compact TUI for visibility.
+
+- Flow: for a selected task, create a branch named with the tag + task id → generate tests for the first subtask (red) using the Surgical Test Generator → implement code (green) → verify tests → commit → repeat per subtask → final verify → push → open PR against the default branch.
+
+- Build on existing rules: .cursor/rules/git_workflow.mdc, .cursor/rules/test_workflow.mdc, .claude/agents/surgical-test-generator.md, and existing CLI/core services.
+
+## Goals
+
+- Deterministic, resumable automation to execute the TDD loop per subtask with minimal human intervention.
+
+- Strong guardrails: never commit to the default branch; only commit when tests pass; enforce status transitions; persist logs/state for debuggability.
+
+- Visibility: a compact terminal UI (like lazygit) to pick tag, view tasks, and start work; right-side pane opens an executor terminal (via tmux) for agent coding.
+
+- Extensible: framework-agnostic test generation via the Surgical Test Generator; detect and use the repo’s test command for execution with coverage thresholds.
+
+## Non‑Goals (initial)
+
+- Full multi-language runner parity beyond detection and executing the project’s test command.
+
+- Complex GUI; start with CLI/TUI + tmux pane. IDE/extension can hook into the same state later.
+
+- Rich executor selection UX (codex/gemini/claude) — we’ll prompt per run; defaults can come later.
+
+## Success Criteria
+
+- One command can autonomously complete a task's subtasks via TDD and open a PR when done.
+
+- All commits made on a branch that includes the tag and task id (see Branch Naming); no commits to the default branch directly.
+
+- Every subtask iteration: failing tests added first (red), then code added to pass them (green), commit only after green.
+
+- End-to-end logs + artifacts stored in .taskmaster/reports/runs/<timestamp-or-id>/.
+
+## Success Metrics (Phase 1)
+
+- **Adoption**: 80% of tasks in a pilot repo completed via `tm autopilot`
+- **Safety**: 0 commits to default branch; 100% of commits have green tests
+- **Efficiency**: Average time from task start to PR < 30min for simple subtasks
+- **Reliability**: < 5% of runs require manual intervention (timeout/conflicts)
+
+## User Stories
+
+- As a developer, I can run tm autopilot <taskId> and watch a structured, safe workflow execute.
+
+- As a reviewer, I can inspect commits per subtask, and a PR summarizing the work when the task completes.
+
+- As an operator, I can see current step, active subtask, tests status, and logs in a compact CLI view and read a final run report.
+
+## Example Workflow Traces
+
+### Happy Path: Complete a 3-subtask feature
+
+```bash
+# Developer starts
+$ tm autopilot 42
+→ Checks preflight: ✓ clean tree, ✓ npm test detected
+→ Creates branch: analytics/task-42-user-metrics
+→ Subtask 42.1: "Add metrics schema"
+  RED: generates test_metrics_schema.test.js → 3 failures
+  GREEN: implements schema.js → all pass
+  COMMIT: "feat(metrics): add metrics schema (task 42.1)"
+→ Subtask 42.2: "Add collection endpoint"
+  RED: generates test_metrics_endpoint.test.js → 5 failures
+  GREEN: implements api/metrics.js → all pass
+  COMMIT: "feat(metrics): add collection endpoint (task 42.2)"
+→ Subtask 42.3: "Add dashboard widget"
+  RED: generates test_metrics_widget.test.js → 4 failures
+  GREEN: implements components/MetricsWidget.jsx → all pass
+  COMMIT: "feat(metrics): add dashboard widget (task 42.3)"
+→ Final: all 3 subtasks complete
+  ✓ Run full test suite → all pass
+  ✓ Coverage check → 85% (meets 80% threshold)
+  PUSH: confirms with user → pushed to origin
+  PR: opens #123 "Task #42 [analytics]: User metrics tracking"
+
+✓ Task 42 complete. PR: https://github.com/org/repo/pull/123
+  Run report: .taskmaster/reports/runs/2025-01-15-142033/
+```
+
+### Error Recovery: Failing tests timeout
+
+```bash
+$ tm autopilot 42
+→ Subtask 42.2 GREEN phase: attempt 1 fails (2 tests still red)
+→ Subtask 42.2 GREEN phase: attempt 2 fails (1 test still red)
+→ Subtask 42.2 GREEN phase: attempt 3 fails (1 test still red)
+
+⚠️  Paused: Could not achieve green state after 3 attempts
+📋 State saved to: .taskmaster/reports/runs/2025-01-15-142033/
+    Last error: "POST /api/metrics returns 500 instead of 201"
+
+Next steps:
+  - Review diff: git diff HEAD
+  - Inspect logs: cat .taskmaster/reports/runs/2025-01-15-142033/log.jsonl
+  - Check test output: cat .taskmaster/reports/runs/2025-01-15-142033/test-results/subtask-42.2-green-attempt3.json
+  - Resume after manual fix: tm autopilot --resume
+
+# Developer manually fixes the issue, then:
+$ tm autopilot --resume
+→ Resuming subtask 42.2 GREEN phase
+  GREEN: all tests pass
+  COMMIT: "feat(metrics): add collection endpoint (task 42.2)"
+→ Continuing to subtask 42.3...
+```
+
+### Dry Run: Preview before execution
+
+```bash
+$ tm autopilot 42 --dry-run
+Autopilot Plan for Task #42 [analytics]: User metrics tracking
+─────────────────────────────────────────────────────────────
+Preflight:
+  ✓ Working tree is clean
+  ✓ Test command detected: npm test
+  ✓ Tools available: git, gh, node, npm
+  ✓ Current branch: main (will create new branch)
+
+Branch & Tag:
+  → Create branch: analytics/task-42-user-metrics
+  → Set active tag: analytics
+
+Subtasks (3 pending):
+  1. 42.1: Add metrics schema
+     - RED: generate tests in src/__tests__/schema.test.js
+     - GREEN: implement src/schema.js
+     - COMMIT: "feat(metrics): add metrics schema (task 42.1)"
+
+  2. 42.2: Add collection endpoint [depends on 42.1]
+     - RED: generate tests in src/api/__tests__/metrics.test.js
+     - GREEN: implement src/api/metrics.js
+     - COMMIT: "feat(metrics): add collection endpoint (task 42.2)"
+
+  3. 42.3: Add dashboard widget [depends on 42.2]
+     - RED: generate tests in src/components/__tests__/MetricsWidget.test.jsx
+     - GREEN: implement src/components/MetricsWidget.jsx
+     - COMMIT: "feat(metrics): add dashboard widget (task 42.3)"
+
+Finalization:
+  → Run full test suite with coverage
+  → Push branch to origin (will confirm)
+  → Create PR targeting main
+
+Run without --dry-run to execute.
+```
+
+## High‑Level Workflow
+
+1) Pre‑flight
+
+   - Verify clean working tree or confirm staging/commit policy (configurable).
+
+   - Detect repo type and the project’s test command (e.g., npm test, pnpm test, pytest, go test).
+
+   - Validate tools: git, gh (optional for PR), node/npm, and (if used) claude CLI.
+
+   - Load TaskMaster state and selected task; if no subtasks exist, automatically run “expand” before working.
+
+2) Branch & Tag Setup
+
+   - Checkout default branch and update (optional), then create a branch using Branch Naming (below).
+
+   - Map branch ↔ tag via existing tag management; explicitly set active tag to the branch’s tag.
+
+3) Subtask Loop (for each pending/in-progress subtask in dependency order)
+
+   - Select next eligible subtask using tm-core TaskService getNextTask() and subtask eligibility logic.
+
+   - Red: generate or update failing tests for the subtask
+
+     - Use the Surgical Test Generator system prompt .claude/agents/surgical-test-generator.md) to produce high-signal tests following project conventions.
+
+     - Run tests to confirm red; record results. If not red (already passing), skip to next subtask or escalate.
+
+   - Green: implement code to pass tests
+
+     - Use executor to implement changes (initial: claude CLI prompt with focused context).
+
+     - Re-run tests until green or timeout/backoff policy triggers.
+
+   - Commit: when green
+
+     - Commit tests + code with conventional commit message. Optionally update subtask status to done.
+
+     - Persist run step metadata/logs.
+
+4) Finalization
+
+   - Run full test suite and coverage (if configured); optionally lint/format.
+
+   - Commit any final adjustments.
+
+   - Push branch (ask user to confirm); create PR (via gh pr create) targeting the default branch. Title format: Task #<id> [<tag>]: <title>.
+
+5) Post‑Run
+
+   - Update task status if desired (e.g., review).
+
+   - Persist run report (JSON + markdown summary) to .taskmaster/reports/runs/<run-id>/.
+
+## Guardrails
+
+- Never commit to the default branch.
+
+- Commit only if all tests (targeted and suite) pass; allow override flags.
+
+- Enforce 80% coverage thresholds (lines/branches/functions/statements) by default; configurable.
+
+- Timebox/model ops and retries; if not green within N attempts, pause with actionable state for resume.
+
+- Always log actions, commands, and outcomes; include dry-run mode.
+
+- Ask before branch creation, pushing, and opening a PR unless --no-confirm is set.
+
+## Integration Points (Current Repo)
+
+- CLI: apps/cli provides command structure and UI components.
+
+  - New command: tm autopilot (alias: task-master autopilot).
+
+  - Reuse UI components under apps/cli/src/ui/components/ for headers/task details/next-task.
+
+- Core services: packages/tm-core
+
+  - TaskService for selection, status, tags.
+
+  - TaskExecutionService for prompt formatting and executor prep.
+
+  - Executors: claude executor and ExecutorFactory to run external tools.
+
+  - Proposed new: WorkflowOrchestrator to drive the autonomous loop and emit progress events.
+
+- Tag/Git utilities: scripts/modules/utils/git-utils.js and scripts/modules/task-manager/tag-management.js for branch→tag mapping and explicit tag switching.
+
+- Rules: .cursor/rules/git_workflow.mdc and .cursor/rules/test_workflow.mdc to steer behavior and ensure consistency.
+
+- Test generation prompt: .claude/agents/surgical-test-generator.md.
+
+## Proposed Components
+
+- Orchestrator (tm-core): WorkflowOrchestrator (new)
+
+  - State machine driving phases: Preflight → Branch/Tag → SubtaskIter (Red/Green/Commit) → Finalize → PR.
+
+  - Exposes an evented API (progress events) that the CLI can render.
+
+  - Stores run state artifacts.
+
+- Test Runner Adapter
+
+  - Detects and runs tests via the project’s test command (e.g., npm test), with targeted runs where feasible.
+
+  - API: runTargeted(files/pattern), runAll(), report summary (failures, duration, coverage), enforce 80% threshold by default.
+
+- Git/PR Adapter
+
+  - Encapsulates git ops: branch create/checkout, add/commit, push.
+
+  - Optional gh integration to open PR; fallback to instructions if gh unavailable.
+
+  - Confirmation gates for branch creation and pushes.
+
+- Prompt/Exec Adapter
+
+  - Uses existing executor service to call the selected coding assistant (initially claude) with tight prompts: task/subtask context, surgical tests first, then minimal code to green.
+
+- Run State + Reporting
+
+  - JSONL log of steps, timestamps, commands, test results.
+
+  - Markdown summary for PR description and post-run artifact.
+
+## CLI UX (MVP)
+
+- Command: tm autopilot [taskId]
+
+  - Flags: --dry-run, --no-push, --no-pr, --no-confirm, --force, --max-attempts <n>, --runner <auto|custom>, --commit-scope <scope>
+
+  - Output: compact header (project, tag, branch), current phase, subtask line, last test summary, next actions.
+
+- Resume: If interrupted, tm autopilot --resume picks up from last checkpoint in run state.
+
+### TUI with tmux (Linear Execution)
+
+- Left pane: Tag selector, task list (status/priority), start/expand shortcuts; "Start" triggers the next task or a selected task.
+
+- Right pane: Executor terminal (tmux split) that runs the coding agent (claude-code/codex). Autopilot can hand over to the right pane during green.
+
+- MCP integration: use MCP tools for task queries/updates and for shell/test invocations where available.
+
+## TUI Layout (tmux-based)
+
+### Pane Structure
+
+```
+┌─────────────────────────────────────┬──────────────────────────────────┐
+│ Task Navigator (left)               │ Executor Terminal (right)        │
+│                                     │                                  │
+│ Project: my-app                     │ $ tm autopilot --executor-mode   │
+│ Branch: analytics/task-42           │ > Running subtask 42.2 GREEN...  │
+│ Tag: analytics                      │ > Implementing endpoint...       │
+│                                     │ > Tests: 3 passed, 0 failed      │
+│ Tasks:                              │ > Ready to commit                │
+│ → 42 [in-progress] User metrics     │                                  │
+│   → 42.1 [done] Schema              │ [Live output from Claude Code]   │
+│   → 42.2 [active] Endpoint ◀        │                                  │
+│   → 42.3 [pending] Dashboard        │                                  │
+│                                     │                                  │
+│ [s] start  [p] pause  [q] quit      │                                  │
+└─────────────────────────────────────┴──────────────────────────────────┘
+```
+
+### Implementation Notes
+
+- **Left pane**: `apps/cli/src/ui/tui/navigator.ts` (new, uses `blessed` or `ink`)
+- **Right pane**: spawned via `tmux split-window -h` running `tm autopilot --executor-mode`
+- **Communication**: shared state file `.taskmaster/state/current-run.json` + file watching or event stream
+- **Keybindings**:
+  - `s` - Start selected task
+  - `p` - Pause/resume current run
+  - `q` - Quit (with confirmation if run active)
+  - `↑/↓` - Navigate task list
+  - `Enter` - Expand/collapse subtasks
+
+## Prompt Composition (Detailed)
+
+### System Prompt Assembly
+
+Prompts are composed in three layers:
+
+1. **Base rules** (loaded in order from `.cursor/rules/` and `.claude/agents/`):
+   - `git_workflow.mdc` → git commit conventions, branch policy, PR guidelines
+   - `test_workflow.mdc` → TDD loop requirements, coverage thresholds, test structure
+   - `surgical-test-generator.md` → test generation methodology, project-specific test patterns
+
+2. **Task context injection**:
+   ```
+   You are implementing:
+   Task #42 [analytics]: User metrics tracking
+   Subtask 42.2: Add collection endpoint
+
+   Description:
+   Implement POST /api/metrics endpoint to collect user metrics events
+
+   Acceptance criteria:
+   - POST /api/metrics accepts { userId, eventType, timestamp }
+   - Validates input schema (reject missing/invalid fields)
+   - Persists to database
+   - Returns 201 on success with created record
+   - Returns 400 on validation errors
+
+   Dependencies:
+   - Subtask 42.1 (metrics schema) is complete
+
+   Current phase: RED (generate failing tests)
+   Test command: npm test
+   Test file convention: src/**/*.test.js (vitest framework detected)
+   Branch: analytics/task-42-user-metrics
+   Project language: JavaScript (Node.js)
+   ```
+
+3. **Phase-specific instructions**:
+   - **RED phase**: "Generate minimal failing tests for this subtask. Do NOT implement any production code. Only create test files. Confirm tests fail with clear error messages indicating missing implementation."
+   - **GREEN phase**: "Implement minimal code to pass the failing tests. Follow existing project patterns in `src/`. Only modify files necessary for this subtask. Keep changes focused and reviewable."
+
+### Example Full Prompt (RED Phase)
+
+```markdown
+<SYSTEM PROMPT>
+[Contents of .cursor/rules/git_workflow.mdc]
+[Contents of .cursor/rules/test_workflow.mdc]
+[Contents of .claude/agents/surgical-test-generator.md]
+
+<TASK CONTEXT>
+You are implementing:
+Task #42.2: Add collection endpoint
+
+Description:
+Implement POST /api/metrics endpoint to collect user metrics events
+
+Acceptance criteria:
+- POST /api/metrics accepts { userId, eventType, timestamp }
+- Validates input schema (reject missing/invalid fields)
+- Persists to database using MetricsSchema from subtask 42.1
+- Returns 201 on success with created record
+- Returns 400 on validation errors with details
+
+Dependencies: Subtask 42.1 (metrics schema) is complete
+
+<INSTRUCTION>
+Generate failing tests for this subtask. Follow project conventions:
+- Test file: src/api/__tests__/metrics.test.js
+- Framework: vitest (detected from package.json)
+- Test cases to cover:
+  * POST /api/metrics with valid payload → should return 201 (will fail: endpoint not implemented)
+  * POST /api/metrics with missing userId → should return 400 (will fail: validation not implemented)
+  * POST /api/metrics with invalid timestamp → should return 400 (will fail: validation not implemented)
+  * POST /api/metrics should persist to database → should save record (will fail: persistence not implemented)
+
+Do NOT implement the endpoint code yet. Only create test file(s).
+Confirm tests fail with messages like "Cannot POST /api/metrics" or "endpoint not defined".
+
+Output format:
+1. File path to create: src/api/__tests__/metrics.test.js
+2. Complete test code
+3. Command to run: npm test src/api/__tests__/metrics.test.js
+```
+
+### Example Full Prompt (GREEN Phase)
+
+```markdown
+<SYSTEM PROMPT>
+[Contents of .cursor/rules/git_workflow.mdc]
+[Contents of .cursor/rules/test_workflow.mdc]
+
+<TASK CONTEXT>
+Task #42.2: Add collection endpoint
+[same context as RED phase]
+
+<CURRENT STATE>
+Tests created in RED phase:
+- src/api/__tests__/metrics.test.js
+- 5 tests written, all failing as expected
+
+Test output:
+```
+FAIL src/api/__tests__/metrics.test.js
+  POST /api/metrics
+    ✗ should return 201 with valid payload (endpoint not found)
+    ✗ should return 400 with missing userId (endpoint not found)
+    ✗ should return 400 with invalid timestamp (endpoint not found)
+    ✗ should persist to database (endpoint not found)
+```
+
+<INSTRUCTION>
+Implement minimal code to make all tests pass.
+
+Guidelines:
+- Create/modify file: src/api/metrics.js
+- Use existing patterns from src/api/ (e.g., src/api/users.js for reference)
+- Import MetricsSchema from subtask 42.1 (src/models/schema.js)
+- Implement validation, persistence, and response handling
+- Follow project error handling conventions
+- Keep implementation focused on this subtask only
+
+After implementation:
+1. Run tests: npm test src/api/__tests__/metrics.test.js
+2. Confirm all 5 tests pass
+3. Report results
+
+Output format:
+1. File(s) created/modified
+2. Implementation code
+3. Test command and results
+```
+
+### Prompt Loading Configuration
+
+See `.taskmaster/config.json` → `prompts` section for paths and load order.
+
+## Configuration Schema
+
+### .taskmaster/config.json
+
+```json
+{
+  "autopilot": {
+    "enabled": true,
+    "requireCleanWorkingTree": true,
+    "commitTemplate": "{type}({scope}): {msg}",
+    "defaultCommitType": "feat",
+    "maxGreenAttempts": 3,
+    "testTimeout": 300000
+  },
+  "test": {
+    "runner": "auto",
+    "coverageThresholds": {
+      "lines": 80,
+      "branches": 80,
+      "functions": 80,
+      "statements": 80
+    },
+    "targetedRunPattern": "**/*.test.js"
+  },
+  "git": {
+    "branchPattern": "{tag}/task-{id}-{slug}",
+    "pr": {
+      "enabled": true,
+      "base": "default",
+      "bodyTemplate": ".taskmaster/templates/pr-body.md"
+    }
+  },
+  "prompts": {
+    "rulesPath": ".cursor/rules",
+    "testGeneratorPath": ".claude/agents/surgical-test-generator.md",
+    "loadOrder": ["git_workflow.mdc", "test_workflow.mdc"]
+  }
+}
+```
+
+### Configuration Fields
+
+#### autopilot
+- `enabled` (boolean): Enable/disable autopilot functionality
+- `requireCleanWorkingTree` (boolean): Require clean git state before starting
+- `commitTemplate` (string): Template for commit messages (tokens: `{type}`, `{scope}`, `{msg}`)
+- `defaultCommitType` (string): Default commit type (feat, fix, chore, etc.)
+- `maxGreenAttempts` (number): Maximum retry attempts to achieve green tests (default: 3)
+- `testTimeout` (number): Timeout in milliseconds per test run (default: 300000 = 5min)
+
+#### test
+- `runner` (string): Test runner detection mode (`"auto"` or explicit command like `"npm test"`)
+- `coverageThresholds` (object): Minimum coverage percentages required
+  - `lines`, `branches`, `functions`, `statements` (number): Threshold percentages (0-100)
+- `targetedRunPattern` (string): Glob pattern for targeted subtask test runs
+
+#### git
+- `branchPattern` (string): Branch naming pattern (tokens: `{tag}`, `{id}`, `{slug}`)
+- `pr.enabled` (boolean): Enable automatic PR creation
+- `pr.base` (string): Target branch for PRs (`"default"` uses repo default, or specify like `"main"`)
+- `pr.bodyTemplate` (string): Path to PR body template file (optional)
+
+#### prompts
+- `rulesPath` (string): Directory containing rule files (e.g., `.cursor/rules`)
+- `testGeneratorPath` (string): Path to test generator prompt file
+- `loadOrder` (array): Order to load rule files from `rulesPath`
+
+### Environment Variables
+
+```bash
+# Required for executor
+ANTHROPIC_API_KEY=sk-ant-...          # Claude API key
+
+# Optional: for PR creation
+GITHUB_TOKEN=ghp_...                  # GitHub personal access token
+
+# Optional: for other executors (future)
+OPENAI_API_KEY=sk-...
+GOOGLE_API_KEY=...
+```
+
+## Run Artifacts & Observability
+
+### Per-Run Artifact Structure
+
+Each autopilot run creates a timestamped directory with complete traceability:
+
+```
+.taskmaster/reports/runs/2025-01-15-142033/
+├── manifest.json          # run metadata (task id, start/end time, status)
+├── log.jsonl              # timestamped event stream
+├── commits.txt            # list of commit SHAs made during run
+├── test-results/
+│   ├── subtask-42.1-red.json
+│   ├── subtask-42.1-green.json
+│   ├── subtask-42.2-red.json
+│   ├── subtask-42.2-green-attempt1.json
+│   ├── subtask-42.2-green-attempt2.json
+│   ├── subtask-42.2-green-attempt3.json
+│   └── final-suite.json
+└── pr.md                  # generated PR body
+```
+
+### manifest.json Format
+
+```json
+{
+  "runId": "2025-01-15-142033",
+  "taskId": "42",
+  "tag": "analytics",
+  "branch": "analytics/task-42-user-metrics",
+  "startTime": "2025-01-15T14:20:33Z",
+  "endTime": "2025-01-15T14:45:12Z",
+  "status": "completed",
+  "subtasksCompleted": ["42.1", "42.2", "42.3"],
+  "subtasksFailed": [],
+  "totalCommits": 3,
+  "prUrl": "https://github.com/org/repo/pull/123",
+  "finalCoverage": {
+    "lines": 85.3,
+    "branches": 82.1,
+    "functions": 88.9,
+    "statements": 85.0
+  }
+}
+```
+
+### log.jsonl Format
+
+Event stream in JSON Lines format for easy parsing and debugging:
+
+```jsonl
+{"ts":"2025-01-15T14:20:33Z","phase":"preflight","status":"ok","details":{"testCmd":"npm test","gitClean":true}}
+{"ts":"2025-01-15T14:20:45Z","phase":"branch","status":"ok","branch":"analytics/task-42-user-metrics"}
+{"ts":"2025-01-15T14:21:00Z","phase":"red","subtask":"42.1","status":"ok","tests":{"failed":3,"passed":0}}
+{"ts":"2025-01-15T14:22:15Z","phase":"green","subtask":"42.1","status":"ok","tests":{"passed":3,"failed":0},"attempts":2}
+{"ts":"2025-01-15T14:22:20Z","phase":"commit","subtask":"42.1","status":"ok","sha":"a1b2c3d","message":"feat(metrics): add metrics schema (task 42.1)"}
+{"ts":"2025-01-15T14:23:00Z","phase":"red","subtask":"42.2","status":"ok","tests":{"failed":5,"passed":0}}
+{"ts":"2025-01-15T14:25:30Z","phase":"green","subtask":"42.2","status":"error","tests":{"passed":3,"failed":2},"attempts":3,"error":"Max attempts reached"}
+{"ts":"2025-01-15T14:25:35Z","phase":"pause","reason":"max_attempts","nextAction":"manual_review"}
+```
+
+### Test Results Format
+
+Each test run stores detailed results:
+
+```json
+{
+  "subtask": "42.2",
+  "phase": "green",
+  "attempt": 3,
+  "timestamp": "2025-01-15T14:25:30Z",
+  "command": "npm test src/api/__tests__/metrics.test.js",
+  "exitCode": 1,
+  "duration": 2340,
+  "summary": {
+    "total": 5,
+    "passed": 3,
+    "failed": 2,
+    "skipped": 0
+  },
+  "failures": [
+    {
+      "test": "POST /api/metrics should return 201 with valid payload",
+      "error": "Expected status 201, got 500",
+      "stack": "..."
+    }
+  ],
+  "coverage": {
+    "lines": 78.5,
+    "branches": 75.0,
+    "functions": 80.0,
+    "statements": 78.5
+  }
+}
+```
+
+## Execution Model
+
+### Orchestration vs Direct Execution
+
+The autopilot system uses an **orchestration model** rather than direct code execution:
+
+**Orchestrator Role** (tm-core WorkflowOrchestrator):
+- Maintains state machine tracking current phase (RED/GREEN/COMMIT) per subtask
+- Validates preconditions (tests pass, git state clean, etc.)
+- Returns "work units" describing what needs to be done next
+- Records completion and advances to next phase
+- Persists state for resumability
+
+**Executor Role** (Claude Code/AI session via MCP):
+- Queries orchestrator for next work unit
+- Executes the work (generates tests, writes code, runs tests, makes commits)
+- Reports results back to orchestrator
+- Handles file operations and tool invocations
+
+**Why This Approach?**
+- Leverages existing AI capabilities (Claude Code) rather than duplicating them
+- MCP protocol provides clean separation between state management and execution
+- Allows human oversight and intervention at each phase
+- Simpler to implement: orchestrator is pure state logic, no code generation needed
+- Enables multiple executor types (Claude Code, other AI tools, human developers)
+
+**Example Flow**:
+```typescript
+// Claude Code (via MCP) queries orchestrator
+const workUnit = await orchestrator.getNextWorkUnit('42');
+// => {
+//      phase: 'RED',
+//      subtask: '42.1',
+//      action: 'Generate failing tests for metrics schema',
+//      context: { title, description, dependencies, testFile: 'src/__tests__/schema.test.js' }
+//    }
+
+// Claude Code executes the work (writes test file, runs tests)
+// Then reports back
+await orchestrator.completeWorkUnit('42', '42.1', 'RED', {
+  success: true,
+  testsCreated: ['src/__tests__/schema.test.js'],
+  testsFailed: 3
+});
+
+// Query again for next phase
+const nextWorkUnit = await orchestrator.getNextWorkUnit('42');
+// => { phase: 'GREEN', subtask: '42.1', action: 'Implement code to pass tests', ... }
+```
+
+## Design Decisions
+
+### Why commit per subtask instead of per task?
+
+**Decision**: Commit after each subtask's green state, not after the entire task.
+
+**Rationale**:
+- Atomic commits make code review easier (reviewers can see logical progression)
+- Easier to revert a single subtask if it causes issues downstream
+- Matches the TDD loop's natural checkpoint and cognitive boundary
+- Provides resumability points if the run is interrupted
+
+**Trade-off**: More commits per task (can use squash-merge in PRs if desired)
+
+### Why not support parallel subtask execution?
+
+**Decision**: Sequential subtask execution in Phase 1; parallel execution deferred to Phase 3.
+
+**Rationale**:
+- Subtasks often have implicit dependencies (e.g., schema before endpoint, endpoint before UI)
+- Simpler orchestrator state machine (less complexity = faster to ship)
+- Parallel execution requires explicit dependency DAG and conflict resolution
+- Can be added in Phase 3 once core workflow is proven stable
+
+**Trade-off**: Slower for truly independent subtasks (mitigated by keeping subtasks small and focused)
+
+### Why require 80% coverage by default?
+
+**Decision**: Enforce 80% coverage threshold (lines/branches/functions/statements) before allowing commits.
+
+**Rationale**:
+- Industry standard baseline for production code quality
+- Forces test generation to be comprehensive, not superficial
+- Configurable per project via `.taskmaster/config.json` if too strict
+- Prevents "green tests" that only test happy paths
+
+**Trade-off**: May require more test generation iterations; can be lowered per project
+
+### Why use tmux instead of a rich GUI?
+
+**Decision**: MVP uses tmux split panes for TUI, not Electron/web-based GUI.
+
+**Rationale**:
+- Tmux is universally available on dev machines; no installation burden
+- Terminal-first workflows match developer mental model (no context switching)
+- Simpler to implement and maintain; can add GUI later via extensions
+- State stored in files allows IDE/extension integration without coupling
+
+**Trade-off**: Less visual polish than GUI; requires tmux familiarity
+
+### Why not support multiple executors (codex/gemini/claude) in Phase 1?
+
+**Decision**: Start with Claude executor only; add others in Phase 2+.
+
+**Rationale**:
+- Reduces scope and complexity for initial delivery
+- Claude Code already integrated with existing executor service
+- Executor abstraction already exists; adding more is straightforward later
+- Different executors may need different prompt strategies (requires experimentation)
+
+**Trade-off**: Users locked to Claude initially; can work around with manual executor selection
+
+## Risks and Mitigations
+
+- Model hallucination/large diffs: restrict prompt scope; enforce minimal changes; show diff previews (optional) before commit.
+
+- Flaky tests: allow retries, isolate targeted runs for speed, then full suite before commit.
+
+- Environment variability: detect runners/tools; provide fallbacks and actionable errors.
+
+- PR creation fails: still push and print manual commands; persist PR body to reuse.
+
+## Open Questions
+
+1) Slugging rules for branch names; any length limits or normalization beyond {slug} token sanitize?
+
+2) PR body standard sections beyond run report (e.g., checklist, coverage table)?
+
+3) Default executor prompt fine-tuning once codex/gemini integration is available.
+
+4) Where to store persistent TUI state (pane layout, last selection) in .taskmaster/state.json?
+
+## Branch Naming
+
+- Include both the tag and the task id in the branch name to make lineage explicit.
+
+- Default pattern: <tag>/task-<id>[-slug] (e.g., master/task-12, tag-analytics/task-4-user-auth).
+
+- Configurable via .taskmaster/config.json: git.branchPattern supports tokens {tag}, {id}, {slug}.
+
+## PR Base Branch
+
+- Use the repository’s default branch (detected via git) unless overridden.
+
+- Title format: Task #<id> [<tag>]: <title>.
+
+## RPG Mapping (Repository Planning Graph)
+
+Functional nodes (capabilities):
+
+- Autopilot Orchestration → drives TDD loop and lifecycle
+
+- Test Generation (Surgical) → produces failing tests from subtask context
+
+- Test Execution + Coverage → runs suite, enforces thresholds
+
+- Git/Branch/PR Management → safe operations and PR creation
+
+- TUI/Terminal Integration → interactive control and visibility via tmux
+
+- MCP Integration → structured task/status/context operations
+
+Structural nodes (code organization):
+
+- packages/tm-core:
+
+  - services/workflow-orchestrator.ts (new)
+
+  - services/test-runner-adapter.ts (new)
+
+  - services/git-adapter.ts (new)
+
+  - existing: task-service.ts, task-execution-service.ts, executors/*
+
+- apps/cli:
+
+  - src/commands/autopilot.command.ts (new)
+
+  - src/ui/tui/ (new tmux/TUI helpers)
+
+- scripts/modules:
+
+  - reuse utils/git-utils.js, task-manager/tag-management.js
+
+- .claude/agents/:
+
+  - surgical-test-generator.md
+
+Edges (data/control flow):
+
+- Autopilot → Test Generation → Test Execution → Git Commit → loop
+
+- Autopilot → Git Adapter (branch, tag, PR)
+
+- Autopilot → TUI (event stream) → tmux pane control
+
+- Autopilot → MCP tools for task/status updates
+
+- Test Execution → Coverage gate → Autopilot decision
+
+Topological traversal (implementation order):
+
+1) Git/Test adapters (foundations)
+
+2) Orchestrator skeleton + events
+
+3) CLI autopilot command and dry-run
+
+4) Surgical test-gen integration and execution gate
+
+5) PR creation, run reports, resumability
+
+## Phased Roadmap
+
+- Phase 0: Spike
+
+  - Implement CLI skeleton tm autopilot with dry-run showing planned steps from a real task + subtasks.
+
+  - Detect test runner (package.json) and git state; render a preflight report.
+
+- Phase 1: Core Rails (State Machine & Orchestration)
+
+  - Implement WorkflowOrchestrator in tm-core as a **state machine** that tracks TDD phases per subtask.
+
+  - Orchestrator **guides** the current AI session (Claude Code/MCP client) rather than executing code itself.
+
+  - Add Git/Test adapters for status checks and validation (not direct execution).
+
+  - WorkflowOrchestrator API:
+    - `getNextWorkUnit(taskId)` → returns next phase to execute (RED/GREEN/COMMIT) with context
+    - `completeWorkUnit(taskId, subtaskId, phase, result)` → records completion and advances state
+    - `getRunState(taskId)` → returns current progress and resumability data
+
+  - MCP integration: expose work unit endpoints so Claude Code can query "what to do next" and report back.
+
+  - Branch/tag mapping via existing tag-management APIs.
+
+  - Run report persisted under .taskmaster/reports/runs/ with state checkpoints for resumability.
+
+- Phase 2: PR + Resumability
+
+  - Add gh PR creation with well-formed body using the run report.
+
+  - Introduce resumable checkpoints and --resume flag.
+
+  - Add coverage enforcement and optional lint/format step.
+
+- Phase 3: Extensibility + Guardrails
+
+  - Add support for basic pytest/go test adapters.
+
+  - Add safeguards: diff preview mode, manual confirm gates, aggressive minimal-change prompts.
+
+  - Optional: small TUI panel and extension panel leveraging the same run state file.
+
+## References (Repo)
+
+- Test Workflow: .cursor/rules/test_workflow.mdc
+
+- Git Workflow: .cursor/rules/git_workflow.mdc
+
+- CLI: apps/cli/src/commands/start.command.ts, apps/cli/src/ui/components/*.ts
+
+- Core Services: packages/tm-core/src/services/task-service.ts, task-execution-service.ts
+
+- Executors: packages/tm-core/src/executors/*
+
+- Git Utilities: scripts/modules/utils/git-utils.js
+
+- Tag Management: scripts/modules/task-manager/tag-management.js
+
+ - Surgical Test Generator: .claude/agents/surgical-test-generator.md
+

.taskmaster/docs/tdd-workflow-phase-0-spike.md

@@ -0,0 +1,130 @@
+# Phase 0: Spike - Autonomous TDD Workflow ✅ COMPLETE
+
+## Objective
+Validate feasibility and build foundational understanding before full implementation.
+
+## Status
+**COMPLETED** - All deliverables implemented and validated.
+
+See `apps/cli/src/commands/autopilot.command.ts` for implementation.
+
+## Scope
+- Implement CLI skeleton `tm autopilot` with dry-run mode
+- Show planned steps from a real task with subtasks
+- Detect test runner from package.json
+- Detect git state and render preflight report
+
+## Deliverables
+
+### 1. CLI Command Skeleton
+- Create `apps/cli/src/commands/autopilot.command.ts`
+- Support `tm autopilot <taskId>` command
+- Implement `--dry-run` flag
+- Basic help text and usage information
+
+### 2. Preflight Detection System
+- Detect test runner from package.json (npm test, pnpm test, etc.)
+- Check git working tree state (clean/dirty)
+- Validate required tools are available (git, gh, node/npm)
+- Detect default branch
+
+### 3. Dry-Run Execution Plan Display
+Display planned execution for a task including:
+- Preflight checks status
+- Branch name that would be created
+- Tag that would be set
+- List of subtasks in execution order
+- For each subtask:
+  - RED phase: test file that would be created
+  - GREEN phase: implementation files that would be modified
+  - COMMIT: commit message that would be used
+- Finalization steps: test suite run, coverage check, push, PR creation
+
+### 4. Task Loading & Validation
+- Load task from TaskMaster state
+- Validate task exists and has subtasks
+- If no subtasks, show message about needing to expand first
+- Show dependency order for subtasks
+
+## Example Output
+
+```bash
+$ tm autopilot 42 --dry-run
+
+Autopilot Plan for Task #42 [analytics]: User metrics tracking
+─────────────────────────────────────────────────────────────
+
+Preflight Checks:
+  ✓ Working tree is clean
+  ✓ Test command detected: npm test
+  ✓ Tools available: git, gh, node, npm
+  ✓ Current branch: main (will create new branch)
+  ✓ Task has 3 subtasks ready to execute
+
+Branch & Tag:
+  → Will create branch: analytics/task-42-user-metrics
+  → Will set active tag: analytics
+
+Execution Plan (3 subtasks):
+
+  1. Subtask 42.1: Add metrics schema
+     RED:    Generate tests → src/__tests__/schema.test.js
+     GREEN:  Implement code → src/schema.js
+     COMMIT: "feat(metrics): add metrics schema (task 42.1)"
+
+  2. Subtask 42.2: Add collection endpoint [depends on 42.1]
+     RED:    Generate tests → src/api/__tests__/metrics.test.js
+     GREEN:  Implement code → src/api/metrics.js
+     COMMIT: "feat(metrics): add collection endpoint (task 42.2)"
+
+  3. Subtask 42.3: Add dashboard widget [depends on 42.2]
+     RED:    Generate tests → src/components/__tests__/MetricsWidget.test.jsx
+     GREEN:  Implement code → src/components/MetricsWidget.jsx
+     COMMIT: "feat(metrics): add dashboard widget (task 42.3)"
+
+Finalization:
+  → Run full test suite with coverage (threshold: 80%)
+  → Push branch to origin (will confirm)
+  → Create PR targeting main
+
+Estimated commits: 3
+Estimated duration: ~20-30 minutes (depends on implementation complexity)
+
+Run without --dry-run to execute.
+```
+
+## Success Criteria
+- Dry-run output is clear and matches expected workflow
+- Preflight detection works correctly on the project repo
+- Task loading integrates with existing TaskMaster state
+- No actual git operations or file modifications occur in dry-run mode
+
+## Out of Scope
+- Actual test generation
+- Actual code implementation
+- Git operations (branch creation, commits, push)
+- PR creation
+- Test execution
+
+## Implementation Notes
+- Reuse existing `TaskService` from `packages/tm-core`
+- Use existing git utilities from `scripts/modules/utils/git-utils.js`
+- Load task/subtask data from `.taskmaster/tasks/tasks.json`
+- Detect test command via package.json → scripts.test field
+
+## Dependencies
+- Existing TaskMaster CLI structure
+- Existing task storage format
+- Git utilities
+
+## Estimated Effort
+2-3 days
+
+## Validation
+Test dry-run mode with:
+- Task with 1 subtask
+- Task with multiple subtasks
+- Task with dependencies between subtasks
+- Task without subtasks (should show warning)
+- Dirty git working tree (should warn)
+- Missing tools (should error with helpful message)

.taskmaster/docs/tdd-workflow-phase-1-orchestrator.md

@@ -0,0 +1,369 @@
+# Phase 1: Core Rails - State Machine & Orchestration
+
+## Objective
+Build the WorkflowOrchestrator as a state machine that guides AI sessions through TDD workflow, rather than directly executing code.
+
+## Architecture Overview
+
+### Execution Model
+The orchestrator acts as a **state manager and guide**, not a code executor:
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                    Claude Code (MCP Client)                  │
+│  - Queries "what to do next"                                │
+│  - Executes work (writes tests, code, runs commands)        │
+│  - Reports completion                                        │
+└────────────────┬────────────────────────────────────────────┘
+                 │ MCP Protocol
+                 ▼
+┌─────────────────────────────────────────────────────────────┐
+│              WorkflowOrchestrator (tm-core)                  │
+│  - Maintains state machine (RED → GREEN → COMMIT)           │
+│  - Returns work units with context                          │
+│  - Validates preconditions                                  │
+│  - Records progress                                         │
+│  - Persists state for resumability                          │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### Why This Approach?
+1. **Separation of Concerns**: State management separate from code execution
+2. **Leverage Existing Tools**: Uses Claude Code's capabilities instead of reimplementing
+3. **Human-in-the-Loop**: Easy to inspect state and intervene at any phase
+4. **Simpler Implementation**: Orchestrator is pure logic, no AI model integration needed
+5. **Flexible Executors**: Any tool (Claude Code, human, other AI) can execute work units
+
+## Core Components
+
+### 1. WorkflowOrchestrator Service
+**Location**: `packages/tm-core/src/services/workflow-orchestrator.service.ts`
+
+**Responsibilities**:
+- Track current phase (RED/GREEN/COMMIT) per subtask
+- Generate work units with context for each phase
+- Validate phase completion criteria
+- Advance state machine on successful completion
+- Handle errors and retry logic
+- Persist run state for resumability
+
+**API**:
+```typescript
+interface WorkflowOrchestrator {
+  // Start a new autopilot run
+  startRun(taskId: string, options?: RunOptions): Promise<RunContext>;
+
+  // Get next work unit to execute
+  getNextWorkUnit(runId: string): Promise<WorkUnit | null>;
+
+  // Report work unit completion
+  completeWorkUnit(
+    runId: string,
+    workUnitId: string,
+    result: WorkUnitResult
+  ): Promise<void>;
+
+  // Get current run state
+  getRunState(runId: string): Promise<RunState>;
+
+  // Pause/resume
+  pauseRun(runId: string): Promise<void>;
+  resumeRun(runId: string): Promise<void>;
+}
+
+interface WorkUnit {
+  id: string;                    // Unique work unit ID
+  phase: 'RED' | 'GREEN' | 'COMMIT';
+  subtaskId: string;             // e.g., "42.1"
+  action: string;                // Human-readable description
+  context: WorkUnitContext;      // All info needed to execute
+  preconditions: Precondition[]; // Checks before execution
+}
+
+interface WorkUnitContext {
+  taskId: string;
+  taskTitle: string;
+  subtaskTitle: string;
+  subtaskDescription: string;
+  dependencies: string[];        // Completed subtask IDs
+  testCommand: string;           // e.g., "npm test"
+
+  // Phase-specific context
+  redPhase?: {
+    testFile: string;            // Where to create test
+    testFramework: string;       // e.g., "vitest"
+    acceptanceCriteria: string[];
+  };
+
+  greenPhase?: {
+    testFile: string;            // Test to make pass
+    implementationHints: string[];
+    expectedFiles: string[];     // Files likely to modify
+  };
+
+  commitPhase?: {
+    commitMessage: string;       // Pre-generated message
+    filesToCommit: string[];     // Files modified in RED+GREEN
+  };
+}
+
+interface WorkUnitResult {
+  success: boolean;
+  phase: 'RED' | 'GREEN' | 'COMMIT';
+
+  // RED phase results
+  testsCreated?: string[];
+  testsFailed?: number;
+
+  // GREEN phase results
+  testsPassed?: number;
+  filesModified?: string[];
+  attempts?: number;
+
+  // COMMIT phase results
+  commitSha?: string;
+
+  // Common
+  error?: string;
+  logs?: string;
+}
+
+interface RunState {
+  runId: string;
+  taskId: string;
+  status: 'running' | 'paused' | 'completed' | 'failed';
+  currentPhase: 'RED' | 'GREEN' | 'COMMIT';
+  currentSubtask: string;
+  completedSubtasks: string[];
+  failedSubtasks: string[];
+  startTime: Date;
+  lastUpdateTime: Date;
+
+  // Resumability
+  checkpoint: {
+    subtaskId: string;
+    phase: 'RED' | 'GREEN' | 'COMMIT';
+    attemptNumber: number;
+  };
+}
+```
+
+### 2. State Machine Logic
+
+**Phase Transitions**:
+```
+START → RED(subtask 1) → GREEN(subtask 1) → COMMIT(subtask 1)
+                                               ↓
+                        RED(subtask 2) ← ─ ─ ─ ┘
+                             ↓
+                        GREEN(subtask 2)
+                             ↓
+                        COMMIT(subtask 2)
+                             ↓
+                           (repeat for remaining subtasks)
+                             ↓
+                        FINALIZE → END
+```
+
+**Phase Rules**:
+- **RED**: Can only transition to GREEN if tests created and failing
+- **GREEN**: Can only transition to COMMIT if tests passing (attempt < maxAttempts)
+- **COMMIT**: Can only transition to next RED if commit successful
+- **FINALIZE**: Can only start if all subtasks completed
+
+**Preconditions**:
+- RED: No uncommitted changes (or staged from previous GREEN that failed)
+- GREEN: RED phase complete, tests exist and are failing
+- COMMIT: GREEN phase complete, all tests passing, coverage meets threshold
+
+### 3. MCP Integration
+
+**New MCP Tools** (expose WorkflowOrchestrator via MCP):
+```typescript
+// Start an autopilot run
+mcp__task_master_ai__autopilot_start(taskId: string, dryRun?: boolean)
+
+// Get next work unit
+mcp__task_master_ai__autopilot_next_work_unit(runId: string)
+
+// Complete current work unit
+mcp__task_master_ai__autopilot_complete_work_unit(
+  runId: string,
+  workUnitId: string,
+  result: WorkUnitResult
+)
+
+// Get run state
+mcp__task_master_ai__autopilot_get_state(runId: string)
+
+// Pause/resume
+mcp__task_master_ai__autopilot_pause(runId: string)
+mcp__task_master_ai__autopilot_resume(runId: string)
+```
+
+### 4. Git/Test Adapters
+
+**GitAdapter** (`packages/tm-core/src/services/git-adapter.service.ts`):
+- Check working tree status
+- Validate branch state
+- Read git config (user, remote, default branch)
+- **Does NOT execute** git commands (that's executor's job)
+
+**TestAdapter** (`packages/tm-core/src/services/test-adapter.service.ts`):
+- Detect test framework from package.json
+- Parse test output (failures, passes, coverage)
+- Validate coverage thresholds
+- **Does NOT run** tests (that's executor's job)
+
+### 5. Run State Persistence
+
+**Storage Location**: `.taskmaster/reports/runs/<runId>/`
+
+**Files**:
+- `state.json` - Current run state (for resumability)
+- `log.jsonl` - Event stream (timestamped work unit completions)
+- `manifest.json` - Run metadata
+- `work-units.json` - All work units generated for this run
+
+**Example `state.json`**:
+```json
+{
+  "runId": "2025-01-15-142033",
+  "taskId": "42",
+  "status": "paused",
+  "currentPhase": "GREEN",
+  "currentSubtask": "42.2",
+  "completedSubtasks": ["42.1"],
+  "failedSubtasks": [],
+  "checkpoint": {
+    "subtaskId": "42.2",
+    "phase": "GREEN",
+    "attemptNumber": 2
+  },
+  "startTime": "2025-01-15T14:20:33Z",
+  "lastUpdateTime": "2025-01-15T14:35:12Z"
+}
+```
+
+## Implementation Plan
+
+### Step 1: WorkflowOrchestrator Skeleton
+- [ ] Create `workflow-orchestrator.service.ts` with interfaces
+- [ ] Implement state machine logic (phase transitions)
+- [ ] Add run state persistence (state.json, log.jsonl)
+- [ ] Write unit tests for state machine
+
+### Step 2: Work Unit Generation
+- [ ] Implement `getNextWorkUnit()` with context assembly
+- [ ] Generate RED phase work units (test file paths, criteria)
+- [ ] Generate GREEN phase work units (implementation hints)
+- [ ] Generate COMMIT phase work units (commit messages)
+
+### Step 3: Git/Test Adapters
+- [ ] Create GitAdapter for status checks only
+- [ ] Create TestAdapter for output parsing only
+- [ ] Add precondition validation using adapters
+- [ ] Write adapter unit tests
+
+### Step 4: MCP Integration
+- [ ] Add MCP tool definitions in `packages/mcp-server/src/tools/`
+- [ ] Wire up WorkflowOrchestrator to MCP tools
+- [ ] Test MCP tools via Claude Code
+- [ ] Document MCP workflow in CLAUDE.md
+
+### Step 5: CLI Integration
+- [ ] Update `autopilot.command.ts` to call WorkflowOrchestrator
+- [ ] Add `--interactive` mode that shows work units and waits for completion
+- [ ] Add `--resume` flag to continue paused runs
+- [ ] Test end-to-end flow
+
+### Step 6: Integration Testing
+- [ ] Create test task with 2-3 subtasks
+- [ ] Run autopilot start → get work unit → complete → repeat
+- [ ] Verify state persistence and resumability
+- [ ] Test failure scenarios (test failures, git issues)
+
+## Success Criteria
+- [ ] WorkflowOrchestrator can generate work units for all phases
+- [ ] MCP tools allow Claude Code to query and complete work units
+- [ ] State persists correctly between work unit completions
+- [ ] Run can be paused and resumed from checkpoint
+- [ ] Adapters validate preconditions without executing commands
+- [ ] End-to-end: Claude Code can complete a simple task via work units
+
+## Out of Scope (Phase 1)
+- Actual git operations (branch creation, commits) - executor handles this
+- Actual test execution - executor handles this
+- PR creation - deferred to Phase 2
+- TUI interface - deferred to Phase 3
+- Coverage enforcement - deferred to Phase 2
+
+## Example Usage Flow
+
+```bash
+# Terminal 1: Claude Code session
+$ claude
+
+# In Claude Code (via MCP):
+> Start autopilot for task 42
+[Calls mcp__task_master_ai__autopilot_start(42)]
+→ Run started: run-2025-01-15-142033
+
+> Get next work unit
+[Calls mcp__task_master_ai__autopilot_next_work_unit(run-2025-01-15-142033)]
+→ Work unit: RED phase for subtask 42.1
+→ Action: Generate failing tests for metrics schema
+→ Test file: src/__tests__/schema.test.js
+→ Framework: vitest
+
+> [Claude Code creates test file, runs tests]
+
+> Complete work unit
+[Calls mcp__task_master_ai__autopilot_complete_work_unit(
+  run-2025-01-15-142033,
+  workUnit-42.1-RED,
+  { success: true, testsCreated: ['src/__tests__/schema.test.js'], testsFailed: 3 }
+)]
+→ Work unit completed. State saved.
+
+> Get next work unit
+[Calls mcp__task_master_ai__autopilot_next_work_unit(run-2025-01-15-142033)]
+→ Work unit: GREEN phase for subtask 42.1
+→ Action: Implement code to pass failing tests
+→ Test file: src/__tests__/schema.test.js
+→ Expected implementation: src/schema.js
+
+> [Claude Code implements schema.js, runs tests, confirms all pass]
+
+> Complete work unit
+[...]
+→ Work unit completed. Ready for COMMIT.
+
+> Get next work unit
+[...]
+→ Work unit: COMMIT phase for subtask 42.1
+→ Commit message: "feat(metrics): add metrics schema (task 42.1)"
+→ Files to commit: src/__tests__/schema.test.js, src/schema.js
+
+> [Claude Code stages files and commits]
+
+> Complete work unit
+[...]
+→ Subtask 42.1 complete! Moving to 42.2...
+```
+
+## Dependencies
+- Existing TaskService (task loading, status updates)
+- Existing PreflightChecker (environment validation)
+- Existing TaskLoaderService (dependency ordering)
+- MCP server infrastructure
+
+## Estimated Effort
+7-10 days
+
+## Next Phase
+Phase 2 will add:
+- PR creation via gh CLI
+- Coverage enforcement
+- Enhanced error recovery
+- Full resumability testing

.taskmaster/docs/tdd-workflow-phase-2-pr-resumability.md

@@ -0,0 +1,433 @@
+# Phase 2: PR + Resumability - Autonomous TDD Workflow
+
+## Objective
+Add PR creation with GitHub CLI integration, resumable checkpoints for interrupted runs, and enhanced guardrails with coverage enforcement.
+
+## Scope
+- GitHub PR creation via `gh` CLI
+- Well-formed PR body using run report
+- Resumable checkpoints and `--resume` flag
+- Coverage enforcement before finalization
+- Optional lint/format step
+- Enhanced error recovery
+
+## Deliverables
+
+### 1. PR Creation Integration
+
+**PRAdapter** (`packages/tm-core/src/services/pr-adapter.ts`):
+```typescript
+class PRAdapter {
+  async isGHAvailable(): Promise<boolean>
+  async createPR(options: PROptions): Promise<PRResult>
+  async getPRTemplate(runReport: RunReport): Promise<string>
+
+  // Fallback for missing gh CLI
+  async getManualPRInstructions(options: PROptions): Promise<string>
+}
+
+interface PROptions {
+  branch: string
+  base: string
+  title: string
+  body: string
+  draft?: boolean
+}
+
+interface PRResult {
+  url: string
+  number: number
+}
+```
+
+**PR Title Format:**
+```
+Task #<id> [<tag>]: <title>
+```
+
+Example: `Task #42 [analytics]: User metrics tracking`
+
+**PR Body Template:**
+
+Located at `.taskmaster/templates/pr-body.md`:
+
+```markdown
+## Summary
+
+Implements Task #42 from TaskMaster autonomous workflow.
+
+**Branch:** {branch}
+**Tag:** {tag}
+**Subtasks completed:** {subtaskCount}
+
+{taskDescription}
+
+## Subtasks
+
+{subtasksList}
+
+## Test Coverage
+
+| Metric | Coverage |
+|--------|----------|
+| Lines | {lines}% |
+| Branches | {branches}% |
+| Functions | {functions}% |
+| Statements | {statements}% |
+
+**All subtasks passed with {totalTests} tests.**
+
+## Commits
+
+{commitsList}
+
+## Run Report
+
+Full execution report: `.taskmaster/reports/runs/{runId}/`
+
+---
+
+🤖 Generated with [Task Master](https://github.com/cline/task-master) autonomous TDD workflow
+```
+
+**Token replacement:**
+- `{branch}` → branch name
+- `{tag}` → active tag
+- `{subtaskCount}` → number of completed subtasks
+- `{taskDescription}` → task description from TaskMaster
+- `{subtasksList}` → markdown list of subtask titles
+- `{lines}`, `{branches}`, `{functions}`, `{statements}` → coverage percentages
+- `{totalTests}` → total test count
+- `{commitsList}` → markdown list of commit SHAs and messages
+- `{runId}` → run ID timestamp
+
+### 2. GitHub CLI Integration
+
+**Detection:**
+```bash
+which gh
+```
+
+If not found, show fallback instructions:
+```bash
+✓ Branch pushed: analytics/task-42-user-metrics
+✗ gh CLI not found - cannot create PR automatically
+
+To create PR manually:
+  gh pr create \
+    --base main \
+    --head analytics/task-42-user-metrics \
+    --title "Task #42 [analytics]: User metrics tracking" \
+    --body-file .taskmaster/reports/runs/2025-01-15-142033/pr.md
+
+Or visit:
+  https://github.com/org/repo/compare/main...analytics/task-42-user-metrics
+```
+
+**Confirmation gate:**
+```bash
+Ready to create PR:
+  Title: Task #42 [analytics]: User metrics tracking
+  Base: main
+  Head: analytics/task-42-user-metrics
+
+Create PR? [Y/n]
+```
+
+Unless `--no-confirm` flag is set.
+
+### 3. Resumable Workflow
+
+**State Checkpoint** (`state.json`):
+```json
+{
+  "runId": "2025-01-15-142033",
+  "taskId": "42",
+  "phase": "subtask-loop",
+  "currentSubtask": "42.2",
+  "currentPhase": "green",
+  "attempts": 2,
+  "completedSubtasks": ["42.1"],
+  "commits": ["a1b2c3d"],
+  "branch": "analytics/task-42-user-metrics",
+  "tag": "analytics",
+  "canResume": true,
+  "pausedAt": "2025-01-15T14:25:35Z",
+  "pausedReason": "max_attempts_reached",
+  "nextAction": "manual_review_required"
+}
+```
+
+**Resume Command:**
+```bash
+$ tm autopilot --resume
+
+Resuming run: 2025-01-15-142033
+  Task: #42 [analytics] User metrics tracking
+  Branch: analytics/task-42-user-metrics
+  Last subtask: 42.2 (GREEN phase, attempt 2/3 failed)
+  Paused: 5 minutes ago
+
+Reason: Could not achieve green state after 3 attempts
+Last error: POST /api/metrics returns 500 instead of 201
+
+Resume from subtask 42.2 GREEN phase? [Y/n]
+```
+
+**Resume logic:**
+1. Load state from `.taskmaster/reports/runs/<runId>/state.json`
+2. Verify branch still exists and is checked out
+3. Verify no uncommitted changes (unless `--force`)
+4. Continue from last checkpoint phase
+5. Update state file as execution progresses
+
+**Multiple interrupted runs:**
+```bash
+$ tm autopilot --resume
+
+Found 2 resumable runs:
+  1. 2025-01-15-142033 - Task #42 (paused 5 min ago at subtask 42.2 GREEN)
+  2. 2025-01-14-103022 - Task #38 (paused 2 hours ago at subtask 38.3 RED)
+
+Select run to resume [1-2]:
+```
+
+### 4. Coverage Enforcement
+
+**Coverage Check Phase** (before finalization):
+```typescript
+async function enforceCoverage(runId: string): Promise<void> {
+  const testResults = await testRunner.runAll()
+  const coverage = await testRunner.getCoverage()
+
+  const thresholds = config.test.coverageThresholds
+  const failures = []
+
+  if (coverage.lines < thresholds.lines) {
+    failures.push(`Lines: ${coverage.lines}% < ${thresholds.lines}%`)
+  }
+  // ... check branches, functions, statements
+
+  if (failures.length > 0) {
+    throw new CoverageError(
+      `Coverage thresholds not met:\n${failures.join('\n')}`
+    )
+  }
+
+  // Store coverage in run report
+  await storeRunArtifact(runId, 'coverage.json', coverage)
+}
+```
+
+**Handling coverage failures:**
+```bash
+⚠️  Coverage check failed:
+  Lines: 78.5% < 80%
+  Branches: 75.0% < 80%
+
+Options:
+  1. Add more tests and resume
+  2. Lower thresholds in .taskmaster/config.json
+  3. Skip coverage check: tm autopilot --resume --skip-coverage
+
+Run paused. Fix coverage and resume with:
+  tm autopilot --resume
+```
+
+### 5. Optional Lint/Format Step
+
+**Configuration:**
+```json
+{
+  "autopilot": {
+    "finalization": {
+      "lint": {
+        "enabled": true,
+        "command": "npm run lint",
+        "fix": true,
+        "failOnError": false
+      },
+      "format": {
+        "enabled": true,
+        "command": "npm run format",
+        "commitChanges": true
+      }
+    }
+  }
+}
+```
+
+**Execution:**
+```bash
+Finalization Steps:
+
+  ✓ All tests passing (12 tests, 0 failures)
+  ✓ Coverage thresholds met (85% lines, 82% branches)
+
+  LINT Running linter... ⏳
+  LINT ✓ No lint errors
+
+  FORMAT Running formatter... ⏳
+  FORMAT ✓ Formatted 3 files
+  FORMAT ✓ Committed formatting changes: "chore: auto-format code"
+
+  PUSH Pushing to origin... ⏳
+  PUSH ✓ Pushed analytics/task-42-user-metrics
+
+  PR Creating pull request... ⏳
+  PR ✓ Created PR #123
+      https://github.com/org/repo/pull/123
+```
+
+### 6. Enhanced Error Recovery
+
+**Pause Points:**
+- Max GREEN attempts reached (current)
+- Coverage check failed (new)
+- Lint errors (if `failOnError: true`)
+- Git push failed (new)
+- PR creation failed (new)
+
+**Each pause saves:**
+- Full state checkpoint
+- Last command output
+- Suggested next actions
+- Resume instructions
+
+**Automatic recovery attempts:**
+- Git push: retry up to 3 times with backoff
+- PR creation: fall back to manual instructions
+- Lint: auto-fix if enabled, otherwise pause
+
+### 7. Finalization Phase Enhancement
+
+**Updated workflow:**
+1. Run full test suite
+2. Check coverage thresholds → pause if failed
+3. Run lint (if enabled) → pause if failed and `failOnError: true`
+4. Run format (if enabled) → auto-commit changes
+5. Confirm push (unless `--no-confirm`)
+6. Push branch → retry on failure
+7. Generate PR body from template
+8. Create PR via gh → fall back to manual instructions
+9. Update task status to 'review' (configurable)
+10. Save final run report
+
+**Final output:**
+```bash
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+✅ Task #42 [analytics]: User metrics tracking - COMPLETE
+
+  Branch: analytics/task-42-user-metrics
+  Subtasks completed: 3/3
+  Commits: 3
+  Total tests: 12 (12 passed, 0 failed)
+  Coverage: 85% lines, 82% branches, 88% functions, 85% statements
+
+  PR #123: https://github.com/org/repo/pull/123
+
+  Run report: .taskmaster/reports/runs/2025-01-15-142033/
+
+Next steps:
+  - Review PR and request changes if needed
+  - Merge when ready
+  - Task status updated to 'review'
+
+Completed in 24 minutes
+```
+
+## CLI Updates
+
+**New flags:**
+- `--resume` → Resume from last checkpoint
+- `--skip-coverage` → Skip coverage checks
+- `--skip-lint` → Skip lint step
+- `--skip-format` → Skip format step
+- `--skip-pr` → Push branch but don't create PR
+- `--draft-pr` → Create draft PR instead of ready-for-review
+
+## Configuration Updates
+
+**Add to `.taskmaster/config.json`:**
+```json
+{
+  "autopilot": {
+    "finalization": {
+      "lint": {
+        "enabled": false,
+        "command": "npm run lint",
+        "fix": true,
+        "failOnError": false
+      },
+      "format": {
+        "enabled": false,
+        "command": "npm run format",
+        "commitChanges": true
+      },
+      "updateTaskStatus": "review"
+    }
+  },
+  "git": {
+    "pr": {
+      "enabled": true,
+      "base": "default",
+      "bodyTemplate": ".taskmaster/templates/pr-body.md",
+      "draft": false
+    },
+    "pushRetries": 3,
+    "pushRetryDelay": 5000
+  }
+}
+```
+
+## Success Criteria
+- Can create PR automatically with well-formed body
+- Can resume interrupted runs from any checkpoint
+- Coverage checks prevent low-quality code from being merged
+- Clear error messages and recovery paths for all failure modes
+- Run reports include full PR context for review
+
+## Out of Scope (defer to Phase 3)
+- Multiple test framework support (pytest, go test)
+- Diff preview before commits
+- TUI panel implementation
+- Extension/IDE integration
+
+## Testing Strategy
+- Mock `gh` CLI for PR creation tests
+- Test resume from each possible pause point
+- Test coverage failure scenarios
+- Test lint/format integration with mock commands
+- End-to-end test with PR creation on test repo
+
+## Dependencies
+- Phase 1 completed (core workflow)
+- GitHub CLI (`gh`) installed (optional, fallback provided)
+- Test framework supports coverage output
+
+## Estimated Effort
+1-2 weeks
+
+## Risks & Mitigations
+- **Risk:** GitHub CLI auth issues
+  - **Mitigation:** Clear auth setup docs, fallback to manual instructions
+
+- **Risk:** PR body template doesn't match all project needs
+  - **Mitigation:** Make template customizable via config path
+
+- **Risk:** Resume state gets corrupted
+  - **Mitigation:** Validate state on load, provide --force-reset option
+
+- **Risk:** Coverage calculation differs between runs
+  - **Mitigation:** Store coverage with each test run for comparison
+
+## Validation
+Test with:
+- Successful PR creation end-to-end
+- Resume from GREEN attempt failure
+- Resume from coverage failure
+- Resume from lint failure
+- Missing `gh` CLI (fallback to manual)
+- Lint/format integration enabled
+- Multiple interrupted runs (selection UI)

.taskmaster/docs/tdd-workflow-phase-3-extensibility-guardrails.md

@@ -0,0 +1,534 @@
+# Phase 3: Extensibility + Guardrails - Autonomous TDD Workflow
+
+## Objective
+Add multi-language/framework support, enhanced safety guardrails, TUI interface, and extensibility for IDE/editor integration.
+
+## Scope
+- Multi-language test runner support (pytest, go test, etc.)
+- Enhanced safety: diff preview, confirmation gates, minimal-change prompts
+- Optional TUI panel with tmux integration
+- State-based extension API for IDE integration
+- Parallel subtask execution (experimental)
+
+## Deliverables
+
+### 1. Multi-Language Test Runner Support
+
+**Extend TestRunnerAdapter:**
+```typescript
+class TestRunnerAdapter {
+  // Existing methods...
+
+  async detectLanguage(): Promise<Language>
+  async detectFramework(language: Language): Promise<Framework>
+  async getFrameworkAdapter(framework: Framework): Promise<FrameworkAdapter>
+}
+
+enum Language {
+  JavaScript = 'javascript',
+  TypeScript = 'typescript',
+  Python = 'python',
+  Go = 'go',
+  Rust = 'rust'
+}
+
+enum Framework {
+  Vitest = 'vitest',
+  Jest = 'jest',
+  Pytest = 'pytest',
+  GoTest = 'gotest',
+  CargoTest = 'cargotest'
+}
+
+interface FrameworkAdapter {
+  runTargeted(pattern: string): Promise<TestResults>
+  runAll(): Promise<TestResults>
+  parseCoverage(output: string): Promise<CoverageReport>
+  getTestFilePattern(): string
+  getTestFileExtension(): string
+}
+```
+
+**Framework-specific adapters:**
+
+**PytestAdapter** (`packages/tm-core/src/services/test-adapters/pytest-adapter.ts`):
+```typescript
+class PytestAdapter implements FrameworkAdapter {
+  async runTargeted(pattern: string): Promise<TestResults> {
+    const output = await exec(`pytest ${pattern} --json-report`)
+    return this.parseResults(output)
+  }
+
+  async runAll(): Promise<TestResults> {
+    const output = await exec('pytest --cov --json-report')
+    return this.parseResults(output)
+  }
+
+  parseCoverage(output: string): Promise<CoverageReport> {
+    // Parse pytest-cov XML output
+  }
+
+  getTestFilePattern(): string {
+    return '**/test_*.py'
+  }
+
+  getTestFileExtension(): string {
+    return '.py'
+  }
+}
+```
+
+**GoTestAdapter** (`packages/tm-core/src/services/test-adapters/gotest-adapter.ts`):
+```typescript
+class GoTestAdapter implements FrameworkAdapter {
+  async runTargeted(pattern: string): Promise<TestResults> {
+    const output = await exec(`go test ${pattern} -json`)
+    return this.parseResults(output)
+  }
+
+  async runAll(): Promise<TestResults> {
+    const output = await exec('go test ./... -coverprofile=coverage.out -json')
+    return this.parseResults(output)
+  }
+
+  parseCoverage(output: string): Promise<CoverageReport> {
+    // Parse go test coverage output
+  }
+
+  getTestFilePattern(): string {
+    return '**/*_test.go'
+  }
+
+  getTestFileExtension(): string {
+    return '_test.go'
+  }
+}
+```
+
+**Detection Logic:**
+```typescript
+async function detectFramework(): Promise<Framework> {
+  // Check for package.json
+  if (await exists('package.json')) {
+    const pkg = await readJSON('package.json')
+    if (pkg.devDependencies?.vitest) return Framework.Vitest
+    if (pkg.devDependencies?.jest) return Framework.Jest
+  }
+
+  // Check for Python files
+  if (await exists('pytest.ini') || await exists('setup.py')) {
+    return Framework.Pytest
+  }
+
+  // Check for Go files
+  if (await exists('go.mod')) {
+    return Framework.GoTest
+  }
+
+  // Check for Rust files
+  if (await exists('Cargo.toml')) {
+    return Framework.CargoTest
+  }
+
+  throw new Error('Could not detect test framework')
+}
+```
+
+### 2. Enhanced Safety Guardrails
+
+**Diff Preview Mode:**
+```bash
+$ tm autopilot 42 --preview-diffs
+
+[2/3] Subtask 42.2: Add collection endpoint
+
+  RED   ✓ Tests created: src/api/__tests__/metrics.test.js
+
+  GREEN Implementing code...
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Proposed changes (src/api/metrics.js):
+
+  + import { MetricsSchema } from '../models/schema.js'
+  +
+  + export async function createMetric(data) {
+  +   const validated = MetricsSchema.parse(data)
+  +   const result = await db.metrics.create(validated)
+  +   return result
+  + }
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Apply these changes? [Y/n/e(dit)/s(kip)]
+  Y - Apply and continue
+  n - Reject and retry GREEN phase
+  e - Open in editor for manual changes
+  s - Skip this subtask
+```
+
+**Minimal Change Enforcement:**
+
+Add to system prompt:
+```markdown
+CRITICAL: Make MINIMAL changes to pass the failing tests.
+- Only modify files directly related to the subtask
+- Do not refactor existing code unless absolutely necessary
+- Do not add features beyond the acceptance criteria
+- Keep changes under 50 lines per file when possible
+- Prefer composition over modification
+```
+
+**Change Size Warnings:**
+```bash
+⚠️  Large change detected:
+  Files modified: 5
+  Lines changed: +234, -12
+
+This subtask was expected to be small (~50 lines).
+Consider:
+  - Breaking into smaller subtasks
+  - Reviewing acceptance criteria
+  - Checking for unintended changes
+
+Continue anyway? [y/N]
+```
+
+### 3. TUI Interface with tmux
+
+**Layout:**
+```
+┌──────────────────────────────────┬─────────────────────────────────┐
+│ Task Navigator (left)            │ Executor Terminal (right)       │
+│                                  │                                 │
+│ Project: my-app                  │ $ tm autopilot --executor-mode  │
+│ Branch: analytics/task-42        │ > Running subtask 42.2 GREEN... │
+│ Tag: analytics                   │ > Implementing endpoint...      │
+│                                  │ > Tests: 3 passed, 0 failed     │
+│ Tasks:                           │ > Ready to commit               │
+│ → 42 [in-progress] User metrics  │                                 │
+│   → 42.1 [done] Schema           │ [Live output from executor]     │
+│   → 42.2 [active] Endpoint ◀     │                                 │
+│   → 42.3 [pending] Dashboard     │                                 │
+│                                  │                                 │
+│ [s] start  [p] pause  [q] quit   │                                 │
+└──────────────────────────────────┴─────────────────────────────────┘
+```
+
+**Implementation:**
+
+**TUI Navigator** (`apps/cli/src/ui/tui/navigator.ts`):
+```typescript
+import blessed from 'blessed'
+
+class AutopilotTUI {
+  private screen: blessed.Widgets.Screen
+  private taskList: blessed.Widgets.ListElement
+  private statusBox: blessed.Widgets.BoxElement
+  private executorPane: string  // tmux pane ID
+
+  async start(taskId?: string) {
+    // Create blessed screen
+    this.screen = blessed.screen()
+
+    // Create task list widget
+    this.taskList = blessed.list({
+      label: 'Tasks',
+      keys: true,
+      vi: true,
+      style: { selected: { bg: 'blue' } }
+    })
+
+    // Spawn tmux pane for executor
+    this.executorPane = await this.spawnExecutorPane()
+
+    // Watch state file for updates
+    this.watchStateFile()
+
+    // Handle keybindings
+    this.setupKeybindings()
+  }
+
+  private async spawnExecutorPane(): Promise<string> {
+    const paneId = await exec('tmux split-window -h -P -F "#{pane_id}"')
+    await exec(`tmux send-keys -t ${paneId} "tm autopilot --executor-mode" Enter`)
+    return paneId.trim()
+  }
+
+  private watchStateFile() {
+    watch('.taskmaster/state/current-run.json', (event, filename) => {
+      this.updateDisplay()
+    })
+  }
+
+  private setupKeybindings() {
+    this.screen.key(['s'], () => this.startTask())
+    this.screen.key(['p'], () => this.pauseTask())
+    this.screen.key(['q'], () => this.quit())
+    this.screen.key(['up', 'down'], () => this.navigateTasks())
+  }
+}
+```
+
+**Executor Mode:**
+```bash
+$ tm autopilot 42 --executor-mode
+
+# Runs in executor pane, writes state to shared file
+# Left pane reads state file and updates display
+```
+
+**State File** (`.taskmaster/state/current-run.json`):
+```json
+{
+  "runId": "2025-01-15-142033",
+  "taskId": "42",
+  "status": "running",
+  "currentPhase": "green",
+  "currentSubtask": "42.2",
+  "lastOutput": "Implementing endpoint...",
+  "testsStatus": {
+    "passed": 3,
+    "failed": 0
+  }
+}
+```
+
+### 4. Extension API for IDE Integration
+
+**State-based API:**
+
+Expose run state via JSON files that IDEs can read:
+- `.taskmaster/state/current-run.json` - live run state
+- `.taskmaster/reports/runs/<runId>/manifest.json` - run metadata
+- `.taskmaster/reports/runs/<runId>/log.jsonl` - event stream
+
+**WebSocket API (optional):**
+```typescript
+// packages/tm-core/src/services/autopilot-server.ts
+class AutopilotServer {
+  private wss: WebSocketServer
+
+  start(port: number = 7890) {
+    this.wss = new WebSocketServer({ port })
+
+    this.wss.on('connection', (ws) => {
+      // Send current state
+      ws.send(JSON.stringify(this.getCurrentState()))
+
+      // Stream events
+      this.orchestrator.on('*', (event) => {
+        ws.send(JSON.stringify(event))
+      })
+    })
+  }
+}
+```
+
+**Usage from IDE extension:**
+```typescript
+// VS Code extension example
+const ws = new WebSocket('ws://localhost:7890')
+
+ws.on('message', (data) => {
+  const event = JSON.parse(data)
+
+  if (event.type === 'subtask:complete') {
+    vscode.window.showInformationMessage(
+      `Subtask ${event.subtaskId} completed`
+    )
+  }
+})
+```
+
+### 5. Parallel Subtask Execution (Experimental)
+
+**Dependency Analysis:**
+```typescript
+class SubtaskScheduler {
+  async buildDependencyGraph(subtasks: Subtask[]): Promise<DAG> {
+    const graph = new DAG()
+
+    for (const subtask of subtasks) {
+      graph.addNode(subtask.id)
+
+      for (const depId of subtask.dependencies) {
+        graph.addEdge(depId, subtask.id)
+      }
+    }
+
+    return graph
+  }
+
+  async getParallelBatches(graph: DAG): Promise<Subtask[][]> {
+    const batches: Subtask[][] = []
+    const completed = new Set<string>()
+
+    while (completed.size < graph.size()) {
+      const ready = graph.nodes.filter(node =>
+        !completed.has(node.id) &&
+        node.dependencies.every(dep => completed.has(dep))
+      )
+
+      batches.push(ready)
+      ready.forEach(node => completed.add(node.id))
+    }
+
+    return batches
+  }
+}
+```
+
+**Parallel Execution:**
+```bash
+$ tm autopilot 42 --parallel
+
+[Batch 1] Running 2 subtasks in parallel:
+  → 42.1: Add metrics schema
+  → 42.4: Add API documentation
+
+  42.1 RED   ✓ Tests created
+  42.4 RED   ✓ Tests created
+
+  42.1 GREEN ✓ Implementation complete
+  42.4 GREEN ✓ Implementation complete
+
+  42.1 COMMIT ✓ Committed: a1b2c3d
+  42.4 COMMIT ✓ Committed: e5f6g7h
+
+[Batch 2] Running 2 subtasks in parallel (depend on 42.1):
+  → 42.2: Add collection endpoint
+  → 42.3: Add dashboard widget
+  ...
+```
+
+**Conflict Detection:**
+```typescript
+async function detectConflicts(subtasks: Subtask[]): Promise<Conflict[]> {
+  const conflicts: Conflict[] = []
+
+  for (let i = 0; i < subtasks.length; i++) {
+    for (let j = i + 1; j < subtasks.length; j++) {
+      const filesA = await predictAffectedFiles(subtasks[i])
+      const filesB = await predictAffectedFiles(subtasks[j])
+
+      const overlap = filesA.filter(f => filesB.includes(f))
+
+      if (overlap.length > 0) {
+        conflicts.push({
+          subtasks: [subtasks[i].id, subtasks[j].id],
+          files: overlap
+        })
+      }
+    }
+  }
+
+  return conflicts
+}
+```
+
+### 6. Advanced Configuration
+
+**Add to `.taskmaster/config.json`:**
+```json
+{
+  "autopilot": {
+    "safety": {
+      "previewDiffs": false,
+      "maxChangeLinesPerFile": 100,
+      "warnOnLargeChanges": true,
+      "requireConfirmOnLargeChanges": true
+    },
+    "parallel": {
+      "enabled": false,
+      "maxConcurrent": 3,
+      "detectConflicts": true
+    },
+    "tui": {
+      "enabled": false,
+      "tmuxSession": "taskmaster-autopilot"
+    },
+    "api": {
+      "enabled": false,
+      "port": 7890,
+      "allowRemote": false
+    }
+  },
+  "test": {
+    "frameworks": {
+      "python": {
+        "runner": "pytest",
+        "coverageCommand": "pytest --cov",
+        "testPattern": "**/test_*.py"
+      },
+      "go": {
+        "runner": "go test",
+        "coverageCommand": "go test ./... -coverprofile=coverage.out",
+        "testPattern": "**/*_test.go"
+      }
+    }
+  }
+}
+```
+
+## CLI Updates
+
+**New commands:**
+```bash
+tm autopilot <taskId> --tui              # Launch TUI interface
+tm autopilot <taskId> --parallel         # Enable parallel execution
+tm autopilot <taskId> --preview-diffs    # Show diffs before applying
+tm autopilot <taskId> --executor-mode    # Run as executor pane
+tm autopilot-server start                # Start WebSocket API
+```
+
+## Success Criteria
+- Supports Python projects with pytest
+- Supports Go projects with go test
+- Diff preview prevents unwanted changes
+- TUI provides better visibility for long-running tasks
+- IDE extensions can integrate via state files or WebSocket
+- Parallel execution reduces total time for independent subtasks
+
+## Out of Scope
+- Full Electron/web GUI
+- AI executor selection UI (defer to Phase 4)
+- Multi-repository support
+- Remote execution on cloud runners
+
+## Testing Strategy
+- Test with Python project (pytest)
+- Test with Go project (go test)
+- Test diff preview UI with mock changes
+- Test parallel execution with independent subtasks
+- Test conflict detection with overlapping file changes
+- Test TUI with mock tmux environment
+
+## Dependencies
+- Phase 2 completed (PR + resumability)
+- tmux installed (for TUI)
+- blessed or ink library (for TUI rendering)
+
+## Estimated Effort
+3-4 weeks
+
+## Risks & Mitigations
+- **Risk:** Parallel execution causes git conflicts
+  - **Mitigation:** Conservative conflict detection, sequential fallback
+
+- **Risk:** TUI adds complexity and maintenance burden
+  - **Mitigation:** Keep TUI optional, state-based design allows alternatives
+
+- **Risk:** Framework adapters hard to maintain across versions
+  - **Mitigation:** Abstract common parsing logic, document adapter interface
+
+- **Risk:** Diff preview slows down workflow
+  - **Mitigation:** Make optional, use --preview-diffs flag only when needed
+
+## Validation
+Test with:
+- Python project with pytest and pytest-cov
+- Go project with go test
+- Large changes requiring confirmation
+- Parallel execution with 3+ independent subtasks
+- TUI with task selection and live status updates
+- VS Code extension reading state files

.taskmaster/reports/task-complexity-report_autonomous-tdd-git-workflow.json

@@ -0,0 +1,197 @@
+{
+	"meta": {
+		"generatedAt": "2025-10-07T09:46:06.248Z",
+		"tasksAnalyzed": 23,
+		"totalTasks": 23,
+		"analysisCount": 23,
+		"thresholdScore": 5,
+		"projectName": "Taskmaster",
+		"usedResearch": false
+	},
+	"complexityAnalysis": [
+		{
+			"taskId": 31,
+			"taskTitle": "Create WorkflowOrchestrator service foundation",
+			"complexityScore": 7,
+			"recommendedSubtasks": 5,
+			"expansionPrompt": "Break down the WorkflowOrchestrator foundation into its core architectural components: phase management system, event emitter infrastructure, state management interfaces, service integration, and lifecycle control methods. Each subtask should focus on a specific architectural concern with clear interfaces and testable units.",
+			"reasoning": "This is a foundational service requiring state machine implementation, event-driven architecture, and integration with existing services. The complexity is high due to the need for robust phase management, error handling, and service orchestration patterns."
+		},
+		{
+			"taskId": 32,
+			"taskTitle": "Implement GitAdapter for repository operations",
+			"complexityScore": 6,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Decompose the GitAdapter implementation into: TypeScript wrapper creation around existing git-utils.js, core git operation methods with comprehensive error handling, branch naming pattern system with token replacement, and confirmation gates for destructive operations. Focus on type safety and existing code integration.",
+			"reasoning": "Moderate-high complexity due to TypeScript integration over existing JavaScript utilities, branch pattern implementation, and safety mechanisms. The existing git-utils.js provides a solid foundation, reducing complexity."
+		},
+		{
+			"taskId": 33,
+			"taskTitle": "Create TestRunnerAdapter for framework detection and execution",
+			"complexityScore": 8,
+			"recommendedSubtasks": 6,
+			"expansionPrompt": "Break down TestRunnerAdapter into framework detection logic, test execution engine with process management, Jest-specific result parsing, Vitest-specific result parsing, unified result interfaces, and final integration. Each framework parser should be separate to handle their unique output formats.",
+			"reasoning": "High complexity due to multiple framework support (Jest, Vitest), child process management, result parsing from different formats, coverage reporting, and timeout handling. Each framework has unique output formats requiring specialized parsers."
+		},
+		{
+			"taskId": 34,
+			"taskTitle": "Implement autopilot CLI command structure",
+			"complexityScore": 5,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Structure the autopilot command into: basic command setup with Commander.js integration, comprehensive flag handling and validation system, preflight check validation with environment validation, and WorkflowOrchestrator integration with dry-run execution planning. Follow existing CLI patterns from the codebase.",
+			"reasoning": "Moderate complexity involving CLI structure, flag handling, and integration with WorkflowOrchestrator. The existing CLI patterns and Commander.js usage in the codebase provide good guidance, reducing implementation complexity."
+		},
+		{
+			"taskId": 35,
+			"taskTitle": "Integrate surgical test generator with WorkflowOrchestrator",
+			"complexityScore": 6,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Decompose the test generation integration into: TaskExecutionService enhancement for test generation mode, TestGenerationService creation using executor framework, prompt composition system for rule integration, and framework-specific test pattern support. Leverage existing executor patterns from the codebase.",
+			"reasoning": "Moderate-high complexity due to integration with existing services, prompt composition system, and framework-specific test generation. The existing executor framework and TaskExecutionService provide good integration points."
+		},
+		{
+			"taskId": 36,
+			"taskTitle": "Implement subtask TDD loop execution",
+			"complexityScore": 9,
+			"recommendedSubtasks": 7,
+			"expansionPrompt": "Break down the TDD loop into: SubtaskExecutor class architecture, RED phase test generation, GREEN phase code generation, COMMIT phase with conventional commits, retry mechanism for GREEN phase, timeout and backoff policies, and TaskService integration. Each phase should be independently testable.",
+			"reasoning": "Very high complexity due to implementing the complete TDD red-green-commit cycle with AI integration, retry logic, timeout handling, and git operations. This is the core autonomous workflow requiring robust error handling and state management."
+		},
+		{
+			"taskId": 37,
+			"taskTitle": "Add configuration schema for autopilot settings",
+			"complexityScore": 4,
+			"recommendedSubtasks": 3,
+			"expansionPrompt": "Expand configuration support into: extending configuration interfaces with autopilot settings, updating ConfigManager validation logic, and implementing default configuration values. Build on existing configuration patterns and maintain backward compatibility.",
+			"reasoning": "Low-moderate complexity involving schema extension and validation logic. The existing configuration system provides clear patterns to follow, making this primarily an extension task rather than new architecture."
+		},
+		{
+			"taskId": 38,
+			"taskTitle": "Implement run state persistence and logging",
+			"complexityScore": 6,
+			"recommendedSubtasks": 5,
+			"expansionPrompt": "Structure run state management into: RunStateManager service class creation, run directory structure and manifest creation, JSONL event logging system, test result and commit tracking storage, and state checkpointing with resume functionality. Focus on data integrity and structured logging.",
+			"reasoning": "Moderate-high complexity due to file system operations, structured logging, state serialization, and resume functionality. Requires careful design of data formats and error handling for persistence operations."
+		},
+		{
+			"taskId": 39,
+			"taskTitle": "Add GitHub PR creation with run reports",
+			"complexityScore": 5,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Decompose PR creation into: PRAdapter service foundation with interfaces, GitHub CLI integration and command execution, PR body generation from run data and test results, and custom PR template system with configuration support. Leverage existing git-utils.js patterns for CLI integration.",
+			"reasoning": "Moderate complexity involving GitHub CLI integration, report generation, and template systems. The existing git-utils.js provides patterns for CLI tool integration, reducing implementation complexity."
+		},
+		{
+			"taskId": 40,
+			"taskTitle": "Implement task dependency resolution for subtask ordering",
+			"complexityScore": 6,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Break down dependency resolution into: dependency resolution algorithm with cycle detection, topological sorting for subtask ordering, task eligibility checking system, and TaskService integration. Implement graph algorithms for dependency management with proper error handling.",
+			"reasoning": "Moderate-high complexity due to graph algorithm implementation, cycle detection, and integration with existing task management. Requires careful design of dependency resolution logic and edge case handling."
+		},
+		{
+			"taskId": 41,
+			"taskTitle": "Create resume functionality for interrupted runs",
+			"complexityScore": 7,
+			"recommendedSubtasks": 5,
+			"expansionPrompt": "Structure resume functionality into: checkpoint creation in RunStateManager, state restoration logic with validation, state validation for safe resume operations, CLI flag implementation for resume command, and partial phase resume functionality. Focus on data integrity and workflow consistency.",
+			"reasoning": "High complexity due to state serialization/deserialization, workflow restoration, validation logic, and CLI integration. Requires robust error handling and state consistency checks for reliable resume operations."
+		},
+		{
+			"taskId": 42,
+			"taskTitle": "Add coverage threshold enforcement",
+			"complexityScore": 5,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Decompose coverage enforcement into: coverage report parsing from Jest/Vitest, configurable threshold validation logic, coverage gates integration in workflow phases, and detailed coverage failure reporting system. Build on existing TestRunnerAdapter patterns.",
+			"reasoning": "Moderate complexity involving coverage report parsing, validation logic, and workflow integration. The existing TestRunnerAdapter provides good foundation for extending coverage capabilities."
+		},
+		{
+			"taskId": 43,
+			"taskTitle": "Implement tmux-based TUI navigator",
+			"complexityScore": 8,
+			"recommendedSubtasks": 6,
+			"expansionPrompt": "Break down TUI implementation into: framework selection and basic structure setup, left pane interface layout with status indicators, tmux integration and terminal coordination, navigation system with keybindings, real-time status updates system, and comprehensive event handling with UX polish. Each component should be independently testable.",
+			"reasoning": "High complexity due to terminal UI framework integration, tmux session management, real-time updates, keyboard event handling, and terminal interface design. Requires expertise in terminal UI libraries and tmux integration."
+		},
+		{
+			"taskId": 44,
+			"taskTitle": "Add prompt composition system for context-aware test generation",
+			"complexityScore": 6,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Structure prompt composition into: PromptComposer service foundation, template processing engine with token replacement, rule loading system with precedence handling, and context injection with phase-specific prompt generation. Focus on flexible template system and rule management.",
+			"reasoning": "Moderate-high complexity due to template processing, rule precedence systems, and context injection logic. Requires careful design of template syntax and rule loading mechanisms."
+		},
+		{
+			"taskId": 45,
+			"taskTitle": "Implement tag-branch mapping and automatic tag switching",
+			"complexityScore": 5,
+			"recommendedSubtasks": 3,
+			"expansionPrompt": "Decompose tag-branch mapping into: GitAdapter enhancement with branch-to-tag extraction logic, automatic tag switching workflow integration, and branch-to-tag mapping persistence with validation. Build on existing git-utils.js and tag management functionality.",
+			"reasoning": "Moderate complexity involving pattern matching, tag management integration, and workflow automation. The existing git-utils.js and tag management systems provide good foundation for implementation."
+		},
+		{
+			"taskId": 46,
+			"taskTitle": "Add comprehensive error handling and recovery",
+			"complexityScore": 7,
+			"recommendedSubtasks": 5,
+			"expansionPrompt": "Structure error handling into: error classification system with specific error types, recovery suggestion engine with actionable recommendations, error context management and preservation, force flag implementation with selective bypass, and logging/reporting system integration. Focus on actionable error messages and automated recovery where possible.",
+			"reasoning": "High complexity due to comprehensive error taxonomy, recovery automation, context preservation, and integration across all workflow components. Requires deep understanding of failure modes and recovery strategies."
+		},
+		{
+			"taskId": 47,
+			"taskTitle": "Implement conventional commit message generation",
+			"complexityScore": 4,
+			"recommendedSubtasks": 3,
+			"expansionPrompt": "Break down commit message generation into: template system creation with variable substitution, commit type auto-detection based on task content and file changes, and validation with GitAdapter integration. Follow conventional commit standards and integrate with existing git operations.",
+			"reasoning": "Low-moderate complexity involving template processing, pattern matching for commit type detection, and validation logic. Well-defined conventional commit standards provide clear implementation guidance."
+		},
+		{
+			"taskId": 48,
+			"taskTitle": "Add multi-framework test execution support",
+			"complexityScore": 7,
+			"recommendedSubtasks": 5,
+			"expansionPrompt": "Expand test framework support into: framework detection system for multiple languages, common adapter interface design, Python pytest adapter implementation, Go and Rust adapter implementations, and integration with existing TestRunnerAdapter. Each language adapter should follow the unified interface pattern.",
+			"reasoning": "High complexity due to multi-language support, framework detection across different ecosystems, and adapter pattern implementation. Each language has unique testing conventions and output formats."
+		},
+		{
+			"taskId": 49,
+			"taskTitle": "Implement workflow event streaming for real-time monitoring",
+			"complexityScore": 6,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Structure event streaming into: WorkflowOrchestrator EventEmitter enhancement, structured event format with metadata, event persistence to run logs, and optional WebSocket streaming for external monitoring. Focus on event consistency and real-time delivery.",
+			"reasoning": "Moderate-high complexity due to event-driven architecture, structured event formats, persistence integration, and WebSocket implementation. Requires careful design of event schemas and delivery mechanisms."
+		},
+		{
+			"taskId": 50,
+			"taskTitle": "Add intelligent test targeting for faster feedback",
+			"complexityScore": 7,
+			"recommendedSubtasks": 5,
+			"expansionPrompt": "Decompose test targeting into: file change detection system, test dependency analysis engine, framework-specific targeting adapters, test impact calculation algorithm, and fallback integration with TestRunnerAdapter. Focus on accuracy and performance optimization.",
+			"reasoning": "High complexity due to dependency analysis, impact calculation algorithms, framework-specific targeting, and integration with existing test execution. Requires sophisticated analysis of code relationships and test dependencies."
+		},
+		{
+			"taskId": 51,
+			"taskTitle": "Implement dry-run visualization with execution timeline",
+			"complexityScore": 6,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Structure dry-run visualization into: timeline calculation engine with duration estimates, estimation algorithms based on task complexity, ASCII art progress visualization with formatting, and resource validation with preflight checks. Focus on accurate planning and clear visual presentation.",
+			"reasoning": "Moderate-high complexity due to timeline calculation, estimation algorithms, ASCII visualization, and resource validation. Requires understanding of workflow timing and visual formatting for terminal output."
+		},
+		{
+			"taskId": 52,
+			"taskTitle": "Add autopilot workflow integration tests",
+			"complexityScore": 8,
+			"recommendedSubtasks": 6,
+			"expansionPrompt": "Structure integration testing into: isolated test environment infrastructure, mock integrations and service stubs, end-to-end workflow test scenarios, performance benchmarking and resource monitoring, test isolation and parallelization strategies, and comprehensive result validation and reporting. Focus on realistic test scenarios and reliable automation.",
+			"reasoning": "High complexity due to end-to-end testing requirements, mock service integration, performance testing, isolation mechanisms, and comprehensive validation. Requires sophisticated test infrastructure and scenario design."
+		},
+		{
+			"taskId": 53,
+			"taskTitle": "Finalize autopilot documentation and examples",
+			"complexityScore": 3,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Structure documentation into: comprehensive autopilot documentation covering setup and usage, example PRD files and templates for different project types, troubleshooting guide for common issues and solutions, and demo materials with workflow visualization. Focus on clarity and practical examples.",
+			"reasoning": "Low complexity involving documentation writing, example creation, and demo material production. The main challenge is ensuring accuracy and completeness rather than technical implementation."
+		}
+	]
+}

.taskmaster/reports/task-complexity-report_tdd-workflow-phase-0.json

@@ -0,0 +1,93 @@
+{
+	"meta": {
+		"generatedAt": "2025-10-07T14:16:40.283Z",
+		"tasksAnalyzed": 10,
+		"totalTasks": 10,
+		"analysisCount": 10,
+		"thresholdScore": 5,
+		"projectName": "Taskmaster",
+		"usedResearch": false
+	},
+	"complexityAnalysis": [
+		{
+			"taskId": 1,
+			"taskTitle": "Create autopilot command CLI skeleton",
+			"complexityScore": 4,
+			"recommendedSubtasks": 3,
+			"expansionPrompt": "Break down the autopilot command creation into: 1) Create AutopilotCommand class extending Commander.Command with proper argument parsing and options, 2) Implement command structure with help text and validation following existing patterns, 3) Add basic registration method and placeholder action handler",
+			"reasoning": "Medium complexity due to following established patterns in the codebase. The command-registry.ts and start.command.ts provide clear templates for implementation. Main complexity is argument parsing and option validation."
+		},
+		{
+			"taskId": 2,
+			"taskTitle": "Implement preflight detection system",
+			"complexityScore": 7,
+			"recommendedSubtasks": 5,
+			"expansionPrompt": "Create PreflightChecker with these subtasks: 1) Package.json test script detection and validation, 2) Git working tree status checking using system commands, 3) Tool availability validation (git, gh, node/npm), 4) Default branch detection via git commands, 5) Structured result reporting with success/failure indicators and error messages",
+			"reasoning": "High complexity due to system integration requirements. Needs to interact with multiple external tools (git, npm, gh), parse various file formats, and handle different system configurations. Error handling for missing tools adds complexity."
+		},
+		{
+			"taskId": 3,
+			"taskTitle": "Implement task loading and validation",
+			"complexityScore": 5,
+			"recommendedSubtasks": 3,
+			"expansionPrompt": "Implement task loading: 1) Use existing TaskService from @tm/core to load tasks by ID with proper error handling, 2) Validate task structure including subtask existence and dependency validation, 3) Provide user-friendly error messages for missing tasks or need to expand subtasks first",
+			"reasoning": "Medium-high complexity. While leveraging existing TaskService reduces implementation effort, the validation logic for subtasks and dependencies requires careful handling of edge cases. Task structure validation adds complexity."
+		},
+		{
+			"taskId": 4,
+			"taskTitle": "Create execution plan display logic",
+			"complexityScore": 6,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Build ExecutionPlanDisplay: 1) Create display formatter using boxen and chalk for consistent CLI styling, 2) Format preflight check results with color-coded status indicators, 3) Display subtask execution order with RED/GREEN/COMMIT phase visualization, 4) Show branch/tag info and finalization steps with duration estimates",
+			"reasoning": "Moderate-high complexity due to complex formatting requirements and dependency on multiple other components. The display needs to coordinate information from preflight, task validation, and execution planning. CLI styling consistency adds complexity."
+		},
+		{
+			"taskId": 5,
+			"taskTitle": "Implement branch and tag planning",
+			"complexityScore": 3,
+			"recommendedSubtasks": 2,
+			"expansionPrompt": "Create BranchPlanner: 1) Implement branch name generation using pattern <tag>/task-<id>-<slug> with kebab-case conversion and special character handling, 2) Add TaskMaster config integration to determine active tag and handle existing branch conflicts",
+			"reasoning": "Low-medium complexity. String manipulation and naming convention implementation is straightforward. The main complexity is handling edge cases with special characters and existing branch conflicts."
+		},
+		{
+			"taskId": 6,
+			"taskTitle": "Create subtask execution order calculation",
+			"complexityScore": 8,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Implement dependency resolution: 1) Build dependency graph from subtask data with proper parsing, 2) Implement topological sort algorithm for execution order, 3) Add circular dependency detection with clear error reporting, 4) Create parallel execution grouping for independent subtasks",
+			"reasoning": "High complexity due to graph algorithms and dependency resolution. Topological sorting, circular dependency detection, and parallel grouping require algorithmic sophistication. Edge cases in dependency chains add significant complexity."
+		},
+		{
+			"taskId": 7,
+			"taskTitle": "Implement TDD phase planning for subtasks",
+			"complexityScore": 6,
+			"recommendedSubtasks": 4,
+			"expansionPrompt": "Create TDDPhasePlanner: 1) Implement test file path detection for common project structures (src/, tests/, __tests__), 2) Parse implementation files from subtask details and descriptions, 3) Generate conventional commit messages for RED/GREEN/COMMIT phases, 4) Add implementation complexity estimation based on subtask content",
+			"reasoning": "Moderate-high complexity due to project structure detection and file path inference. Conventional commit message generation and complexity estimation require understanding of different project layouts and parsing subtask content effectively."
+		},
+		{
+			"taskId": 8,
+			"taskTitle": "Add finalization steps planning",
+			"complexityScore": 4,
+			"recommendedSubtasks": 3,
+			"expansionPrompt": "Create FinalizationPlanner: 1) Implement test suite execution planning with coverage threshold detection from package.json, 2) Add git operations planning (branch push, PR creation) using existing git patterns, 3) Create duration estimation algorithm based on subtask count and complexity metrics",
+			"reasoning": "Medium complexity. Building on existing git utilities and test command detection reduces complexity. Main challenges are coverage threshold parsing and duration estimation algorithms."
+		},
+		{
+			"taskId": 9,
+			"taskTitle": "Integrate command with existing CLI infrastructure",
+			"complexityScore": 3,
+			"recommendedSubtasks": 2,
+			"expansionPrompt": "Complete CLI integration: 1) Add AutopilotCommand to command-registry.ts following existing patterns and update command metadata, 2) Test command registration and help system integration with proper cleanup and error handling",
+			"reasoning": "Low-medium complexity. The command-registry.ts provides a clear pattern to follow. Main work is registration and ensuring proper integration with existing CLI infrastructure. Well-established patterns reduce complexity."
+		},
+		{
+			"taskId": 10,
+			"taskTitle": "Add comprehensive error handling and edge cases",
+			"complexityScore": 7,
+			"recommendedSubtasks": 5,
+			"expansionPrompt": "Implement error handling: 1) Add missing task and invalid task structure error handling with helpful messages, 2) Handle git state errors (dirty working tree, missing tools), 3) Add dependency validation errors (circular, invalid references), 4) Implement missing tool detection with installation guidance, 5) Create user-friendly error messages following existing CLI patterns",
+			"reasoning": "High complexity due to comprehensive error scenarios. Each component (preflight, task loading, dependency resolution) has multiple failure modes that need proper handling. Providing helpful error messages and recovery suggestions adds complexity."
+		}
+	]
+}

.taskmaster/state.json

@@ -1,6 +1,6 @@
 {
 	"currentTag": "master",
-	"lastSwitched": "2025-09-12T22:25:27.535Z",
+	"lastSwitched": "2025-10-07T17:17:58.049Z",
 	"branchTagMapping": {
 		"v017-adds": "v017-adds",
 		"next": "next"

.taskmaster/templates/example_prd_rpg.txt

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

CHANGELOG.md

@@ -1,84 +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

apps/cli/CHANGELOG.md

@@ -4,13 +4,6 @@
 
 ### Patch Changes
 
-- Updated dependencies []:
-  - @tm/core@null
-
-## null
-
-### Patch Changes
-
 - Updated dependencies []:
   - @tm/core@null
 

apps/cli/package.json

@@ -48,6 +48,5 @@
 		"*": {
 			"*": ["src/*"]
 		}
-	},
-	"version": ""
+	}
 }

apps/cli/src/command-registry.ts

@@ -13,6 +13,7 @@ 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';
+import { AutopilotCommand } from './commands/autopilot.command.js';
 
 /**
  * Command metadata for registration
@@ -63,6 +64,12 @@ export class CommandRegistry {
 			commandClass: ExportCommand as any,
 			category: 'task'
 		},
+		{
+			name: 'autopilot',
+			description: 'Execute a task autonomously using TDD workflow',
+			commandClass: AutopilotCommand as any,
+			category: 'development'
+		},
 
 		// Authentication & Context Commands
 		{

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

@@ -0,0 +1,515 @@
+/**
+ * @fileoverview AutopilotCommand using Commander's native class pattern
+ * Extends Commander.Command for better integration with the framework
+ * This is a thin presentation layer over @tm/core's autopilot functionality
+ */
+
+import { Command } from 'commander';
+import chalk from 'chalk';
+import boxen from 'boxen';
+import ora, { type Ora } from 'ora';
+import {
+	createTaskMasterCore,
+	type TaskMasterCore,
+	type Task,
+	type Subtask
+} from '@tm/core';
+import * as ui from '../utils/ui.js';
+
+/**
+ * CLI-specific options interface for the autopilot command
+ */
+export interface AutopilotCommandOptions {
+	format?: 'text' | 'json';
+	project?: string;
+	dryRun?: boolean;
+}
+
+/**
+ * Preflight check result for a single check
+ */
+export interface PreflightCheckResult {
+	success: boolean;
+	message?: string;
+}
+
+/**
+ * Overall preflight check results
+ */
+export interface PreflightResult {
+	success: boolean;
+	testCommand: PreflightCheckResult;
+	gitWorkingTree: PreflightCheckResult;
+	requiredTools: PreflightCheckResult;
+	defaultBranch: PreflightCheckResult;
+}
+
+/**
+ * CLI-specific result type from autopilot command
+ */
+export interface AutopilotCommandResult {
+	success: boolean;
+	taskId: string;
+	task?: Task;
+	error?: string;
+	message?: string;
+}
+
+/**
+ * AutopilotCommand extending Commander's Command class
+ * This is a thin presentation layer over @tm/core's autopilot functionality
+ */
+export class AutopilotCommand extends Command {
+	private tmCore?: TaskMasterCore;
+	private lastResult?: AutopilotCommandResult;
+
+	constructor(name?: string) {
+		super(name || 'autopilot');
+
+		// Configure the command
+		this.description(
+			'Execute a task autonomously using TDD workflow with git integration'
+		)
+			.argument('<taskId>', 'Task ID to execute autonomously')
+			.option('-f, --format <format>', 'Output format (text, json)', 'text')
+			.option('-p, --project <path>', 'Project root directory', process.cwd())
+			.option(
+				'--dry-run',
+				'Show what would be executed without performing actions'
+			)
+			.action(async (taskId: string, options: AutopilotCommandOptions) => {
+				await this.executeCommand(taskId, options);
+			});
+	}
+
+	/**
+	 * Execute the autopilot command
+	 */
+	private async executeCommand(
+		taskId: string,
+		options: AutopilotCommandOptions
+	): Promise<void> {
+		let spinner: Ora | null = null;
+
+		try {
+			// Validate options
+			if (!this.validateOptions(options)) {
+				process.exit(1);
+			}
+
+			// Validate task ID format
+			if (!this.validateTaskId(taskId)) {
+				ui.displayError(`Invalid task ID format: ${taskId}`);
+				process.exit(1);
+			}
+
+			// Initialize tm-core with spinner
+			spinner = ora('Initializing Task Master...').start();
+			await this.initializeCore(options.project || process.cwd());
+			spinner.succeed('Task Master initialized');
+
+			// Load and validate task existence
+			spinner = ora(`Loading task ${taskId}...`).start();
+			const task = await this.loadTask(taskId);
+
+			if (!task) {
+				spinner.fail(`Task ${taskId} not found`);
+				ui.displayError(`Task with ID ${taskId} does not exist`);
+				process.exit(1);
+			}
+
+			spinner.succeed(`Task ${taskId} loaded`);
+
+			// Display task information
+			this.displayTaskInfo(task, options.dryRun || false);
+
+			// Execute autopilot logic (placeholder for now)
+			const result = await this.performAutopilot(taskId, task, options);
+
+			// Store result for programmatic access
+			this.setLastResult(result);
+
+			// Display results
+			this.displayResults(result, options);
+		} catch (error: unknown) {
+			if (spinner) {
+				spinner.fail('Operation failed');
+			}
+			this.handleError(error);
+			process.exit(1);
+		}
+	}
+
+	/**
+	 * Validate command options
+	 */
+	private validateOptions(options: AutopilotCommandOptions): boolean {
+		// Validate format
+		if (options.format && !['text', 'json'].includes(options.format)) {
+			console.error(chalk.red(`Invalid format: ${options.format}`));
+			console.error(chalk.gray(`Valid formats: text, json`));
+			return false;
+		}
+
+		return true;
+	}
+
+	/**
+	 * Validate task ID format
+	 */
+	private validateTaskId(taskId: string): boolean {
+		// Task ID should be a number or number.number format (e.g., "1" or "1.2")
+		const taskIdPattern = /^\d+(\.\d+)*$/;
+		return taskIdPattern.test(taskId);
+	}
+
+	/**
+	 * Initialize TaskMasterCore
+	 */
+	private async initializeCore(projectRoot: string): Promise<void> {
+		if (!this.tmCore) {
+			this.tmCore = await createTaskMasterCore({ projectPath: projectRoot });
+		}
+	}
+
+	/**
+	 * Load task from tm-core
+	 */
+	private async loadTask(taskId: string): Promise<Task | null> {
+		if (!this.tmCore) {
+			throw new Error('TaskMasterCore not initialized');
+		}
+
+		try {
+			const { task } = await this.tmCore.getTaskWithSubtask(taskId);
+			return task;
+		} catch (error) {
+			return null;
+		}
+	}
+
+	/**
+	 * Display task information before execution
+	 */
+	private displayTaskInfo(task: Task, isDryRun: boolean): void {
+		const prefix = isDryRun ? '[DRY RUN] ' : '';
+		console.log();
+		console.log(
+			boxen(
+				chalk.cyan.bold(`${prefix}Autopilot Task Execution`) +
+					'\n\n' +
+					chalk.white(`Task ID: ${task.id}`) +
+					'\n' +
+					chalk.white(`Title: ${task.title}`) +
+					'\n' +
+					chalk.white(`Status: ${task.status}`) +
+					(task.description ? '\n\n' + chalk.gray(task.description) : ''),
+				{
+					padding: 1,
+					borderStyle: 'round',
+					borderColor: 'cyan',
+					width: process.stdout.columns ? process.stdout.columns * 0.95 : 100
+				}
+			)
+		);
+		console.log();
+	}
+
+	/**
+	 * Perform autopilot execution using PreflightChecker and TaskLoader
+	 */
+	private async performAutopilot(
+		taskId: string,
+		task: Task,
+		options: AutopilotCommandOptions
+	): Promise<AutopilotCommandResult> {
+		// Run preflight checks
+		const preflightResult = await this.runPreflightChecks(options);
+		if (!preflightResult.success) {
+			return {
+				success: false,
+				taskId,
+				task,
+				error: 'Preflight checks failed',
+				message: 'Please resolve the issues above before running autopilot'
+			};
+		}
+
+		// Validate task structure and get execution order
+		const validationResult = await this.validateTaskStructure(
+			taskId,
+			task,
+			options
+		);
+		if (!validationResult.success) {
+			return validationResult;
+		}
+
+		// Display execution plan
+		this.displayExecutionPlan(
+			validationResult.task!,
+			validationResult.orderedSubtasks!,
+			options
+		);
+
+		return {
+			success: true,
+			taskId,
+			task: validationResult.task,
+			message: options.dryRun
+				? 'Dry run completed successfully'
+				: 'Autopilot execution ready (actual execution not yet implemented)'
+		};
+	}
+
+	/**
+	 * Run preflight checks and display results
+	 */
+	private async runPreflightChecks(
+		options: AutopilotCommandOptions
+	): Promise<PreflightResult> {
+		const { PreflightChecker } = await import('@tm/core');
+
+		console.log();
+		console.log(chalk.cyan.bold('Running preflight checks...'));
+
+		const preflightChecker = new PreflightChecker(
+			options.project || process.cwd()
+		);
+		const result = await preflightChecker.runAllChecks();
+
+		this.displayPreflightResults(result);
+
+		return result;
+	}
+
+	/**
+	 * Validate task structure and get execution order
+	 */
+	private async validateTaskStructure(
+		taskId: string,
+		task: Task,
+		options: AutopilotCommandOptions
+	): Promise<AutopilotCommandResult & { orderedSubtasks?: Subtask[] }> {
+		const { TaskLoaderService } = await import('@tm/core');
+
+		console.log();
+		console.log(chalk.cyan.bold('Validating task structure...'));
+
+		const taskLoader = new TaskLoaderService(options.project || process.cwd());
+		const validationResult = await taskLoader.loadAndValidateTask(taskId);
+
+		if (!validationResult.success) {
+			await taskLoader.cleanup();
+			return {
+				success: false,
+				taskId,
+				task,
+				error: validationResult.errorMessage,
+				message: validationResult.suggestion
+			};
+		}
+
+		const orderedSubtasks = taskLoader.getExecutionOrder(
+			validationResult.task!
+		);
+
+		await taskLoader.cleanup();
+
+		return {
+			success: true,
+			taskId,
+			task: validationResult.task,
+			orderedSubtasks
+		};
+	}
+
+	/**
+	 * Display execution plan with subtasks and TDD workflow
+	 */
+	private displayExecutionPlan(
+		task: Task,
+		orderedSubtasks: Subtask[],
+		options: AutopilotCommandOptions
+	): void {
+		console.log();
+		console.log(chalk.green.bold('✓ All checks passed!'));
+		console.log();
+		console.log(chalk.cyan.bold('Execution Plan:'));
+		console.log(chalk.white(`Task: ${task.title}`));
+		console.log(
+			chalk.gray(
+				`${orderedSubtasks.length} subtasks will be executed in dependency order`
+			)
+		);
+		console.log();
+
+		// Display subtasks
+		orderedSubtasks.forEach((subtask: Subtask, index: number) => {
+			console.log(
+				chalk.yellow(`${index + 1}. ${task.id}.${subtask.id}: ${subtask.title}`)
+			);
+			if (subtask.dependencies && subtask.dependencies.length > 0) {
+				console.log(
+					chalk.gray(`   Dependencies: ${subtask.dependencies.join(', ')}`)
+				);
+			}
+		});
+
+		console.log();
+		console.log(
+			chalk.cyan('Autopilot would execute each subtask using TDD workflow:')
+		);
+		console.log(chalk.gray('  1. RED phase: Write failing test'));
+		console.log(chalk.gray('  2. GREEN phase: Implement code to pass test'));
+		console.log(chalk.gray('  3. COMMIT phase: Commit changes'));
+		console.log();
+
+		if (options.dryRun) {
+			console.log(
+				chalk.yellow('This was a dry run. Use without --dry-run to execute.')
+			);
+		}
+	}
+
+	/**
+	 * Display preflight check results
+	 */
+	private displayPreflightResults(result: PreflightResult): void {
+		const checks = [
+			{ name: 'Test command', result: result.testCommand },
+			{ name: 'Git working tree', result: result.gitWorkingTree },
+			{ name: 'Required tools', result: result.requiredTools },
+			{ name: 'Default branch', result: result.defaultBranch }
+		];
+
+		checks.forEach((check) => {
+			const icon = check.result.success ? chalk.green('✓') : chalk.red('✗');
+			const status = check.result.success
+				? chalk.green('PASS')
+				: chalk.red('FAIL');
+			console.log(`${icon} ${chalk.white(check.name)}: ${status}`);
+			if (check.result.message) {
+				console.log(chalk.gray(`  ${check.result.message}`));
+			}
+		});
+	}
+
+	/**
+	 * Display results based on format
+	 */
+	private displayResults(
+		result: AutopilotCommandResult,
+		options: AutopilotCommandOptions
+	): void {
+		const format = options.format || 'text';
+
+		switch (format) {
+			case 'json':
+				this.displayJson(result);
+				break;
+
+			case 'text':
+			default:
+				this.displayTextResult(result);
+				break;
+		}
+	}
+
+	/**
+	 * Display in JSON format
+	 */
+	private displayJson(result: AutopilotCommandResult): void {
+		console.log(JSON.stringify(result, null, 2));
+	}
+
+	/**
+	 * Display result in text format
+	 */
+	private displayTextResult(result: AutopilotCommandResult): void {
+		if (result.success) {
+			console.log(
+				boxen(
+					chalk.green.bold('✓ Autopilot Command Completed') +
+						'\n\n' +
+						chalk.white(result.message || 'Execution complete'),
+					{
+						padding: 1,
+						borderStyle: 'round',
+						borderColor: 'green',
+						margin: { top: 1 }
+					}
+				)
+			);
+		} else {
+			console.log(
+				boxen(
+					chalk.red.bold('✗ Autopilot Command Failed') +
+						'\n\n' +
+						chalk.white(result.error || 'Unknown error'),
+					{
+						padding: 1,
+						borderStyle: 'round',
+						borderColor: 'red',
+						margin: { top: 1 }
+					}
+				)
+			);
+		}
+	}
+
+	/**
+	 * Handle general errors
+	 */
+	private handleError(error: unknown): void {
+		const errorObj = error as {
+			getSanitizedDetails?: () => { message: string };
+			message?: string;
+			stack?: string;
+		};
+
+		const msg = errorObj?.getSanitizedDetails?.() ?? {
+			message: errorObj?.message ?? String(error)
+		};
+		console.error(chalk.red(`Error: ${msg.message || 'Unexpected error'}`));
+
+		// Show stack trace in development mode or when DEBUG is set
+		const isDevelopment = process.env.NODE_ENV !== 'production';
+		if ((isDevelopment || process.env.DEBUG) && errorObj.stack) {
+			console.error(chalk.gray(errorObj.stack));
+		}
+	}
+
+	/**
+	 * Set the last result for programmatic access
+	 */
+	private setLastResult(result: AutopilotCommandResult): void {
+		this.lastResult = result;
+	}
+
+	/**
+	 * Get the last result (for programmatic usage)
+	 */
+	getLastResult(): AutopilotCommandResult | undefined {
+		return this.lastResult;
+	}
+
+	/**
+	 * Clean up resources
+	 */
+	async cleanup(): Promise<void> {
+		if (this.tmCore) {
+			await this.tmCore.close();
+			this.tmCore = undefined;
+		}
+	}
+
+	/**
+	 * Register this command on an existing program
+	 */
+	static register(program: Command, name?: string): AutopilotCommand {
+		const autopilotCommand = new AutopilotCommand(name);
+		program.addCommand(autopilotCommand);
+		return autopilotCommand;
+	}
+}

apps/cli/src/index.ts

@@ -11,6 +11,7 @@ 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';
+export { AutopilotCommand } from './commands/autopilot.command.js';
 
 // Command Registry
 export {

apps/cli/src/utils/auto-update.ts

@@ -12,7 +12,6 @@ export interface UpdateInfo {
 	currentVersion: string;
 	latestVersion: string;
 	needsUpdate: boolean;
-	highlights?: string[];
 }
 
 /**
@@ -60,116 +59,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 +85,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 +95,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 +136,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;
-		}
-		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, {
+	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'
-	});
+		}
+	);
 
 	console.log(message);
 }

apps/docs/CHANGELOG.md

@@ -1,7 +1,5 @@
 # docs
 
-## 0.0.5
-
 ## 0.0.4
 
 ## 0.0.3

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

@@ -124,8 +124,6 @@ sidebarTitle: "CLI Commands"
     # Research-backed generation for all tasks
     task-master expand --all --research
     ```
-
-    When you run `task-master expand --all` after `task-master analyze-complexity`, the expand operation automatically uses the recommended subtask counts from the complexity analysis instead of applying uniform defaults. This ensures each task is broken down according to its actual complexity level.
   </Accordion>
 
   <Accordion title="Clear Subtasks">

apps/docs/capabilities/mcp.mdx

@@ -40,7 +40,7 @@ The MCP tools can be categorized in the same way as the core functionalities:
 
 -   **`parse_prd`**: Parses a PRD to generate tasks.
 -   **`expand_task`**: Expands a task into subtasks.
--   **`expand_all`**: Expands all eligible tasks, automatically using complexity analysis recommendations when available.
+-   **`expand_all`**: Expands all eligible tasks.
 -   **`analyze_project_complexity`**: Analyzes task complexity.
 -   **`complexity_report`**: Displays the complexity analysis report.
 

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 and determine optimal subtask counts.
-
-### Step 4: Expand Tasks
-
-```bash
-task-master expand --all --research
-```
-
-Break down complex tasks into manageable subtasks while preserving dependency chains. The expand operation automatically uses the complexity analysis recommendations to determine the appropriate number of subtasks for each task based on its complexity level.
-
----
-
-## 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>

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

@@ -32,11 +32,7 @@ The more context you give the model, the better the breakdown and results.
 
 ## Writing a PRD for Task Master
 
-<Note>
-Two example PRD templates are available in `.taskmaster/templates/`:
-- `example_prd.txt` - Simple template for straightforward projects
-- `example_prd_rpg.txt` - Advanced RPG (Repository Planning Graph) template for complex projects with dependencies
-</Note>
+<Note>An example PRD can be found in .taskmaster/templates/example_prd.txt</Note>
 
 
 You can co-write your PRD with an LLM model using the following workflow:
@@ -47,29 +43,6 @@ You can co-write your PRD with an LLM model using the following workflow:
 
 This approach works great in Cursor, or anywhere you use a chat-based LLM.
 
-### Choosing Between Templates
-
-**Use `example_prd.txt` when:**
-- Building straightforward features
-- Working on smaller projects
-- Dependencies are simple and obvious
-
-**Use `example_prd_rpg.txt` when:**
-- Building complex systems with multiple modules
-- Need explicit dependency management
-- Want structured guidance on architecture decisions
-- Planning a large codebase from scratch
-
-The RPG template teaches you to think about:
-1. **Functional decomposition** (WHAT the system does)
-2. **Structural decomposition** (HOW it's organized in code)
-3. **Explicit dependencies** (WHAT depends on WHAT)
-4. **Topological ordering** (build foundation first, then layers)
-
-<Tip>
-For complex projects, using the RPG template with a code-context-aware ai agent produces the best results because the AI can understand your existing codebase structure. [Learn more about the RPG method →](/capabilities/rpg-method)
-</Tip>
-
 ---
 
 ## Where to Save Your PRD

apps/docs/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "docs",
-	"version": "0.0.5",
+	"version": "0.0.4",
 	"private": true,
 	"description": "Task Master documentation powered by Mintlify",
 	"scripts": {

apps/extension/CHANGELOG.md

@@ -1,12 +1,5 @@
 # Change Log
 
-## 0.25.5
-
-### Patch Changes
-
-- Updated dependencies [[`b43b7ce`](https://github.com/eyaltoledano/claude-task-master/commit/b43b7ce201625eee956fb2f8cd332f238bb78c21), [`aaacc3d`](https://github.com/eyaltoledano/claude-task-master/commit/aaacc3dae36247b4de72b2d2697f49e5df6d01e3), [`0079b7d`](https://github.com/eyaltoledano/claude-task-master/commit/0079b7defdad550811f704c470fdd01955d91d4d), [`0b2c696`](https://github.com/eyaltoledano/claude-task-master/commit/0b2c6967c4605c33a100cff16f6ce8ff09ad06f0), [`4f984f8`](https://github.com/eyaltoledano/claude-task-master/commit/4f984f8a6965da9f9c7edd60ddfd6560ac022917), [`7b5a7c4`](https://github.com/eyaltoledano/claude-task-master/commit/7b5a7c4495a68b782f7407fc5d0e0d3ae81f42f5), [`caee040`](https://github.com/eyaltoledano/claude-task-master/commit/caee040907f856d31a660171c9e6d966f23c632e), [`18aa416`](https://github.com/eyaltoledano/claude-task-master/commit/18aa416035f44345bde1c7321490345733a5d042), [`18aa416`](https://github.com/eyaltoledano/claude-task-master/commit/18aa416035f44345bde1c7321490345733a5d042), [`738ec51`](https://github.com/eyaltoledano/claude-task-master/commit/738ec51c049a295a12839b2dfddaf05e23b8fede), [`d67b81d`](https://github.com/eyaltoledano/claude-task-master/commit/d67b81d25ddd927fabb6f5deb368e8993519c541), [`b5fe723`](https://github.com/eyaltoledano/claude-task-master/commit/b5fe723f8ead928e9f2dbde13b833ee70ac3382d), [`2b69936`](https://github.com/eyaltoledano/claude-task-master/commit/2b69936ee7b34346d6de5175af20e077359e2e2a), [`986ac11`](https://github.com/eyaltoledano/claude-task-master/commit/986ac117aee00bcd3e6830a0f76e1ad6d10e0bca), [`20004a3`](https://github.com/eyaltoledano/claude-task-master/commit/20004a39ea848f747e1ff48981bfe176554e4055)]:
-  - task-master-ai@0.28.0
-
 ## 0.25.5-rc.0
 
 ### Patch Changes

apps/extension/package.json

@@ -3,7 +3,7 @@
 	"private": true,
 	"displayName": "TaskMaster",
 	"description": "A visual Kanban board interface for TaskMaster projects in VS Code",
-	"version": "0.25.5",
+	"version": "0.25.5-rc.0",
 	"publisher": "Hamster",
 	"icon": "assets/icon.png",
 	"engines": {

assets/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>

docs/contributor-docs/worktree-setup.md

@@ -0,0 +1,420 @@
+# Git Worktree Setup for Parallel Development
+
+Simple git worktree setup for running multiple AI coding assistants in parallel.
+
+## Why Worktrees?
+
+Instead of Docker complexity, use git worktrees to create isolated working directories:
+
+✅ **Editor Agnostic** - Works with Cursor, Windsurf, VS Code, Claude Code, etc.
+✅ **Simple** - No Docker, no containers, just git
+✅ **Fast** - Instant setup, shared git history
+✅ **Flexible** - Each worktree can be on a different branch
+✅ **Task Master Works** - Full access to `.taskmaster/` in each worktree
+
+## Quick Start
+
+### 1. Create a Worktree
+
+```bash
+# Using current branch as base
+./scripts/create-worktree.sh
+
+# Or specify a branch name
+./scripts/create-worktree.sh feature/my-feature
+```
+
+This creates a worktree in `../claude-task-master-worktrees/<branch-name>/`
+
+### 2. Open in Your Editor
+
+```bash
+# Navigate to the worktree
+cd ../claude-task-master-worktrees/auto-main/  # (or whatever branch)
+
+# Open with your preferred AI editor
+cursor .        # Cursor
+code .          # VS Code
+windsurf .      # Windsurf
+claude          # Claude Code CLI
+```
+
+### 3. Work in Parallel
+
+**Main directory** (where you are now):
+```bash
+# Keep working normally
+git checkout main
+cursor .
+```
+
+**Worktree directory**:
+```bash
+cd ../claude-task-master-worktrees/auto-main/
+# Different files, different branch, same git repo
+claude
+```
+
+## Usage Examples
+
+### Example 1: Let Claude Work Autonomously
+
+```bash
+# Create worktree
+./scripts/create-worktree.sh auto/taskmaster-work
+
+# Navigate there
+cd ../claude-task-master-worktrees/auto-taskmaster-work/
+
+# Start Claude
+claude
+
+# In Claude session
+> Use task-master to get the next task and complete it
+```
+
+**Meanwhile in your main directory:**
+```bash
+# You keep working normally
+cursor .
+# No conflicts!
+```
+
+### Example 2: Multiple AI Assistants in Parallel
+
+```bash
+# Create multiple worktrees
+./scripts/create-worktree.sh cursor/feature-a
+./scripts/create-worktree.sh claude/feature-b
+./scripts/create-worktree.sh windsurf/feature-c
+
+# Terminal 1
+cd ../claude-task-master-worktrees/cursor-feature-a/
+cursor .
+
+# Terminal 2
+cd ../claude-task-master-worktrees/claude-feature-b/
+claude
+
+# Terminal 3
+cd ../claude-task-master-worktrees/windsurf-feature-c/
+windsurf .
+```
+
+### Example 3: Test vs Implementation
+
+```bash
+# Main directory: Write implementation
+cursor .
+
+# Worktree: Have Claude write tests
+cd ../claude-task-master-worktrees/auto-main/
+claude -p "Write tests for the recent changes in the main branch"
+```
+
+## How It Works
+
+### Directory Structure
+
+```
+/Volumes/Workspace/workspace/contrib/task-master/
+├── claude-task-master/              # Main directory (this one)
+│   ├── .git/                        # Shared git repo
+│   ├── .taskmaster/                 # Synced via git
+│   └── your code...
+│
+└── claude-task-master-worktrees/    # Worktrees directory
+    ├── auto-main/                   # Worktree 1
+    │   ├── .git -> (points to main .git)
+    │   ├── .taskmaster/             # Same tasks, synced
+    │   └── your code... (on branch auto/main)
+    │
+    └── feature-x/                   # Worktree 2
+        ├── .git -> (points to main .git)
+        ├── .taskmaster/
+        └── your code... (on branch feature/x)
+```
+
+### Shared Git Repository
+
+All worktrees share the same `.git`:
+- Commits in one worktree are immediately visible in others
+- Branches are shared
+- Git history is shared
+- Only the working files differ
+
+## Task Master in Worktrees
+
+Task Master works perfectly in worktrees:
+
+```bash
+# In any worktree
+task-master list        # Same tasks
+task-master next        # Same task queue
+task-master show 1.2    # Same task data
+
+# Changes are shared (if committed/pushed)
+```
+
+### Recommended Workflow
+
+Use **tags** to separate task contexts:
+
+```bash
+# Main directory - use default tag
+task-master list
+
+# Worktree 1 - use separate tag
+cd ../claude-task-master-worktrees/auto-main/
+task-master add-tag --name=claude-auto
+task-master use-tag --name=claude-auto
+task-master list  # Shows claude-auto tasks only
+```
+
+## Managing Worktrees
+
+### List All Worktrees
+
+```bash
+./scripts/list-worktrees.sh
+
+# Or directly with git
+git worktree list
+```
+
+### Remove a Worktree
+
+```bash
+# Remove specific worktree
+git worktree remove ../claude-task-master-worktrees/auto-main/
+
+# Or if there are uncommitted changes, force it
+git worktree remove --force ../claude-task-master-worktrees/auto-main/
+```
+
+### Sync Changes Between Worktrees
+
+Changes are automatically synced through git:
+
+```bash
+# In worktree
+git add .
+git commit -m "feat: implement feature"
+git push
+
+# In main directory
+git pull
+# Changes are now available
+```
+
+## Common Workflows
+
+### 1. Autonomous Claude with Task Master
+
+**Setup:**
+```bash
+./scripts/create-worktree.sh auto/claude-work
+cd ../claude-task-master-worktrees/auto-claude-work/
+```
+
+**Run:**
+```bash
+# Copy the autonomous script
+cp ../claude-task-master/run-autonomous-tasks.sh .
+
+# Run Claude autonomously
+./run-autonomous-tasks.sh
+```
+
+**Monitor from main directory:**
+```bash
+# In another terminal, in main directory
+watch -n 5 "task-master list"
+```
+
+### 2. Code Review Workflow
+
+**Main directory:**
+```bash
+# You write code
+cursor .
+git add .
+git commit -m "feat: new feature"
+```
+
+**Worktree:**
+```bash
+cd ../claude-task-master-worktrees/auto-main/
+git pull
+
+# Have Claude review
+claude -p "Review the latest commit and suggest improvements"
+```
+
+### 3. Parallel Feature Development
+
+**Worktree 1 (Backend):**
+```bash
+./scripts/create-worktree.sh backend/api
+cd ../claude-task-master-worktrees/backend-api/
+cursor .
+# Work on API
+```
+
+**Worktree 2 (Frontend):**
+```bash
+./scripts/create-worktree.sh frontend/ui
+cd ../claude-task-master-worktrees/frontend-ui/
+windsurf .
+# Work on UI
+```
+
+**Main directory:**
+```bash
+# Monitor and merge
+git log --all --graph --oneline
+```
+
+## Tips
+
+### 1. Branch Naming Convention
+
+Use prefixes to organize:
+- `auto/*` - For autonomous AI work
+- `cursor/*` - For Cursor-specific features
+- `claude/*` - For Claude-specific features
+- `review/*` - For code review worktrees
+
+### 2. Commit Often in Worktrees
+
+Worktrees make it easy to try things:
+```bash
+# In worktree
+git commit -m "experiment: trying approach X"
+# If it doesn't work, just delete the worktree
+git worktree remove .
+```
+
+### 3. Use Different npm Dependencies
+
+Each worktree can have different `node_modules`:
+```bash
+# Main directory
+npm install
+
+# Worktree (different dependencies)
+cd ../claude-task-master-worktrees/auto-main/
+npm install
+# Installs independently
+```
+
+### 4. .env Files
+
+Each worktree can have its own `.env`:
+```bash
+# Main directory
+echo "API_URL=http://localhost:3000" > .env
+
+# Worktree
+cd ../claude-task-master-worktrees/auto-main/
+echo "API_URL=http://localhost:4000" > .env
+# Different config!
+```
+
+## Cleanup
+
+### Remove All Worktrees
+
+```bash
+# List and manually remove
+./scripts/list-worktrees.sh
+
+# Remove each one
+git worktree remove ../claude-task-master-worktrees/auto-main/
+git worktree remove ../claude-task-master-worktrees/feature-x/
+
+# Or remove all at once (careful!)
+rm -rf ../claude-task-master-worktrees/
+git worktree prune  # Clean up git's worktree metadata
+```
+
+### Delete Remote Branches
+
+```bash
+# After merging/done with branches
+git branch -d auto/claude-work
+git push origin --delete auto/claude-work
+```
+
+## Troubleshooting
+
+### "Cannot create worktree: already exists"
+
+```bash
+# Remove the existing worktree first
+git worktree remove ../claude-task-master-worktrees/auto-main/
+```
+
+### "Branch already checked out"
+
+Git won't let you check out the same branch in multiple worktrees:
+```bash
+# Use a different branch name
+./scripts/create-worktree.sh auto/main-2
+```
+
+### Changes Not Syncing
+
+Worktrees don't auto-sync files. Use git:
+```bash
+# In worktree with changes
+git add .
+git commit -m "changes"
+git push
+
+# In other worktree
+git pull
+```
+
+### npm install Fails
+
+Each worktree needs its own `node_modules`:
+```bash
+cd ../claude-task-master-worktrees/auto-main/
+npm install
+```
+
+## Comparison to Docker
+
+| Feature | Git Worktrees | Docker |
+|---------|---------------|--------|
+| Setup time | Instant | Minutes (build) |
+| Disk usage | Minimal (shared .git) | GBs per container |
+| Editor support | Native (any editor) | Limited (need special setup) |
+| File sync | Via git | Via volumes (can be slow) |
+| Resource usage | None (native) | RAM/CPU overhead |
+| Complexity | Simple (just git) | Complex (Dockerfile, compose, etc.) |
+| npm install | Per worktree | Per container |
+| AI editor support | ✅ All editors work | ⚠️ Need web-based or special config |
+
+**TL;DR: Worktrees are simpler, faster, and more flexible for this use case.**
+
+---
+
+## Summary
+
+```bash
+# 1. Create worktree
+./scripts/create-worktree.sh auto/claude-work
+
+# 2. Open in AI editor
+cd ../claude-task-master-worktrees/auto-claude-work/
+cursor .   # or claude, windsurf, code, etc.
+
+# 3. Work in parallel
+# Main directory: You work
+# Worktree: AI works
+# No conflicts!
+```
+
+**Simple, fast, editor-agnostic.** 🚀

mcp-server/src/core/direct-functions/expand-all-tasks.js

@@ -8,7 +8,6 @@ import {
 	disableSilentMode
 } from '../../../../scripts/modules/utils.js';
 import { createLogWrapper } from '../../tools/utils.js';
-import { resolveComplexityReportOutputPath } from '../../../../src/utils/path-utils.js';
 
 /**
  * Expand all pending tasks with subtasks (Direct Function Wrapper)
@@ -26,30 +25,13 @@ import { resolveComplexityReportOutputPath } from '../../../../src/utils/path-ut
  */
 export async function expandAllTasksDirect(args, log, context = {}) {
 	const { session } = context; // Extract session
-	// Destructure expected args, including projectRoot and complexityReportPath
-	const {
-		tasksJsonPath,
-		num,
-		research,
-		prompt,
-		force,
-		projectRoot,
-		tag,
-		complexityReportPath: providedComplexityReportPath
-	} = args;
+	// Destructure expected args, including projectRoot
+	const { tasksJsonPath, num, research, prompt, force, projectRoot, tag } =
+		args;
 
 	// Create logger wrapper using the utility
 	const mcpLog = createLogWrapper(log);
 
-	// Use provided complexity report path or compute it
-	const complexityReportPath =
-		providedComplexityReportPath ||
-		resolveComplexityReportOutputPath(null, { projectRoot, tag }, log);
-
-	log.info(
-		`Expand all tasks will use complexity report at: ${complexityReportPath}`
-	);
-
 	if (!tasksJsonPath) {
 		log.error('expandAllTasksDirect called without tasksJsonPath');
 		return {
@@ -73,14 +55,14 @@ export async function expandAllTasksDirect(args, log, context = {}) {
 		const additionalContext = prompt || '';
 		const forceFlag = force === true;
 
-		// Call the core function, passing options and the context object { session, mcpLog, projectRoot, tag, complexityReportPath }
+		// Call the core function, passing options and the context object { session, mcpLog, projectRoot }
 		const result = await expandAllTasks(
 			tasksJsonPath,
 			numSubtasks,
 			useResearch,
 			additionalContext,
 			forceFlag,
-			{ session, mcpLog, projectRoot, tag, complexityReportPath },
+			{ session, mcpLog, projectRoot, tag },
 			'json'
 		);
 

mcp-server/src/core/utils/path-utils.js

@@ -3,7 +3,6 @@ import {
 	findTasksPath as coreFindTasksPath,
 	findPRDPath as coreFindPrdPath,
 	findComplexityReportPath as coreFindComplexityReportPath,
-	resolveComplexityReportOutputPath as coreResolveComplexityReportOutputPath,
 	findProjectRoot as coreFindProjectRoot,
 	normalizeProjectRoot
 } from '../../../../src/utils/path-utils.js';
@@ -225,21 +224,6 @@ export function findComplexityReportPath(args, log = silentLogger) {
 	return resolveComplexityReportPath(args, log);
 }
 
-/**
- * Resolve complexity report output path (create if needed) - primary MCP function
- * @param {string|null} [explicitPath] - Explicit path to complexity report
- * @param {Object} args - Arguments object containing projectRoot and tag
- * @param {Object} [log] - Log function to prevent console logging
- * @returns {string} - Resolved output path for complexity report
- */
-export function resolveComplexityReportOutputPath(
-	explicitPath,
-	args,
-	log = silentLogger
-) {
-	return coreResolveComplexityReportOutputPath(explicitPath, args, log);
-}
-
 /**
  * Find PRD path - primary MCP function
  * @param {string} [explicitPath] - Explicit path to PRD file

mcp-server/src/tools/expand-all.js

@@ -10,10 +10,7 @@ import {
 	withNormalizedProjectRoot
 } from './utils.js';
 import { expandAllTasksDirect } from '../core/task-master-core.js';
-import {
-	findTasksPath,
-	resolveComplexityReportOutputPath
-} from '../core/utils/path-utils.js';
+import { findTasksPath } from '../core/utils/path-utils.js';
 import { resolveTag } from '../../../scripts/modules/utils.js';
 
 /**
@@ -88,14 +85,6 @@ export function registerExpandAllTool(server) {
 					);
 				}
 
-				// Resolve complexity report path to use recommendations from analyze-complexity
-				const complexityReportPath = resolveComplexityReportOutputPath(
-					null,
-					{ projectRoot: args.projectRoot, tag: resolvedTag },
-					log
-				);
-				log.info(`Using complexity report path: ${complexityReportPath}`);
-
 				const result = await expandAllTasksDirect(
 					{
 						tasksJsonPath: tasksJsonPath,
@@ -104,8 +93,7 @@ export function registerExpandAllTool(server) {
 						prompt: args.prompt,
 						force: args.force,
 						projectRoot: args.projectRoot,
-						tag: resolvedTag,
-						complexityReportPath
+						tag: resolvedTag
 					},
 					log,
 					{ session }

package-lock.json

@@ -1,12 +1,12 @@
 {
 	"name": "task-master-ai",
-	"version": "0.28.0",
+	"version": "0.28.0-rc.1",
 	"lockfileVersion": 3,
 	"requires": true,
 	"packages": {
 		"": {
 			"name": "task-master-ai",
-			"version": "0.28.0",
+			"version": "0.28.0-rc.1",
 			"license": "MIT WITH Commons-Clause",
 			"workspaces": [
 				"apps/*",
@@ -125,13 +125,13 @@
 			}
 		},
 		"apps/docs": {
-			"version": "0.0.5",
+			"version": "0.0.4",
 			"devDependencies": {
 				"mintlify": "^4.2.111"
 			}
 		},
 		"apps/extension": {
-			"version": "0.25.5",
+			"version": "0.25.5-rc.0",
 			"dependencies": {
 				"task-master-ai": "*"
 			},

package.json

@@ -1,6 +1,6 @@
 {
 	"name": "task-master-ai",
-	"version": "0.28.0",
+	"version": "0.28.0-rc.2",
 	"description": "A task management system for ambitious AI-driven development that doesn't overwhelm and confuse Cursor.",
 	"main": "index.js",
 	"type": "module",
@@ -118,13 +118,7 @@
 	"bugs": {
 		"url": "https://github.com/eyaltoledano/claude-task-master/issues"
 	},
-	"files": [
-		"dist/**",
-		"README-task-master.md",
-		"README.md",
-		"LICENSE",
-		"CHANGELOG.md"
-	],
+	"files": ["dist/**", "README-task-master.md", "README.md", "LICENSE"],
 	"overrides": {
 		"node-fetch": "^2.6.12",
 		"whatwg-url": "^11.0.0"

packages/ai-sdk-provider-grok-cli/CHANGELOG.md

@@ -1,3 +0,0 @@
-# @tm/ai-sdk-provider-grok-cli
-
-## null

packages/ai-sdk-provider-grok-cli/package.json

@@ -31,6 +31,5 @@
 	"files": ["dist/**/*", "README.md"],
 	"publishConfig": {
 		"access": "public"
-	},
-	"version": ""
+	}
 }

packages/build-config/CHANGELOG.md

@@ -2,6 +2,4 @@
 
 ## null
 
-## null
-
 ## 1.0.1

packages/build-config/package.json

@@ -24,6 +24,5 @@
 	},
 	"dependencies": {
 		"tsup": "^8.5.0"
-	},
-	"version": ""
+	}
 }

packages/tm-core/CHANGELOG.md

@@ -2,8 +2,6 @@
 
 ## null
 
-## null
-
 ## 0.26.1
 
 All notable changes to the @task-master/tm-core package will be documented in this file.

packages/tm-core/package.json

@@ -42,6 +42,5 @@
 	"files": ["src", "README.md", "CHANGELOG.md"],
 	"keywords": ["task-management", "typescript", "ai", "prd", "parser"],
 	"author": "Task Master AI",
-	"license": "MIT",
-	"version": ""
+	"license": "MIT"
 }

packages/tm-core/src/index.ts

@@ -72,3 +72,14 @@ export {
 	type ComplexityAnalysis,
 	type TaskComplexityData
 } from './reports/index.js';
+
+// Re-export services
+export {
+	PreflightChecker,
+	TaskLoaderService,
+	type CheckResult,
+	type PreflightResult,
+	type TaskValidationResult,
+	type ValidationErrorType,
+	type DependencyIssue
+} from './services/index.js';

packages/tm-core/src/services/index.ts

@@ -6,8 +6,19 @@
 export { TaskService } from './task-service.js';
 export { OrganizationService } from './organization.service.js';
 export { ExportService } from './export.service.js';
+export { PreflightChecker } from './preflight-checker.service.js';
+export { TaskLoaderService } from './task-loader.service.js';
 export type { Organization, Brief } from './organization.service.js';
 export type {
 	ExportTasksOptions,
 	ExportResult
 } from './export.service.js';
+export type {
+	CheckResult,
+	PreflightResult
+} from './preflight-checker.service.js';
+export type {
+	TaskValidationResult,
+	ValidationErrorType,
+	DependencyIssue
+} from './task-loader.service.js';

packages/tm-core/src/services/preflight-checker.service.ts

@@ -0,0 +1,395 @@
+/**
+ * @fileoverview Preflight Checker Service
+ * Validates environment and prerequisites for autopilot execution
+ */
+
+import { readFileSync, existsSync, readdirSync } from 'fs';
+import { join } from 'path';
+import { execSync } from 'child_process';
+import { getLogger } from '../logger/factory.js';
+import {
+	isGitRepository,
+	isGhCliAvailable,
+	getDefaultBranch
+} from '../utils/git-utils.js';
+
+const logger = getLogger('PreflightChecker');
+
+/**
+ * Result of a single preflight check
+ */
+export interface CheckResult {
+	/** Whether the check passed */
+	success: boolean;
+	/** The value detected/validated */
+	value?: any;
+	/** Error or warning message */
+	message?: string;
+}
+
+/**
+ * Complete preflight validation results
+ */
+export interface PreflightResult {
+	/** Overall success - all checks passed */
+	success: boolean;
+	/** Test command detection result */
+	testCommand: CheckResult;
+	/** Git working tree status */
+	gitWorkingTree: CheckResult;
+	/** Required tools availability */
+	requiredTools: CheckResult;
+	/** Default branch detection */
+	defaultBranch: CheckResult;
+	/** Summary message */
+	summary: string;
+}
+
+/**
+ * Tool validation result
+ */
+interface ToolCheck {
+	name: string;
+	available: boolean;
+	version?: string;
+	message?: string;
+}
+
+/**
+ * PreflightChecker validates environment for autopilot execution
+ */
+export class PreflightChecker {
+	private projectRoot: string;
+
+	constructor(projectRoot: string) {
+		if (!projectRoot) {
+			throw new Error('projectRoot is required for PreflightChecker');
+		}
+		this.projectRoot = projectRoot;
+	}
+
+	/**
+	 * Detect test command from package.json
+	 */
+	async detectTestCommand(): Promise<CheckResult> {
+		try {
+			const packageJsonPath = join(this.projectRoot, 'package.json');
+			const packageJsonContent = readFileSync(packageJsonPath, 'utf-8');
+			const packageJson = JSON.parse(packageJsonContent);
+
+			if (!packageJson.scripts || !packageJson.scripts.test) {
+				return {
+					success: false,
+					message:
+						'No test script found in package.json. Please add a "test" script.'
+				};
+			}
+
+			const testCommand = packageJson.scripts.test;
+
+			return {
+				success: true,
+				value: testCommand,
+				message: `Test command: ${testCommand}`
+			};
+		} catch (error: any) {
+			if (error.code === 'ENOENT') {
+				return {
+					success: false,
+					message: 'package.json not found in project root'
+				};
+			}
+
+			return {
+				success: false,
+				message: `Failed to read package.json: ${error.message}`
+			};
+		}
+	}
+
+	/**
+	 * Check git working tree status
+	 */
+	async checkGitWorkingTree(): Promise<CheckResult> {
+		try {
+			// Check if it's a git repository
+			const isRepo = await isGitRepository(this.projectRoot);
+			if (!isRepo) {
+				return {
+					success: false,
+					message: 'Not a git repository. Initialize git first.'
+				};
+			}
+
+			// Check for changes (staged/unstaged/untracked) without requiring HEAD
+			const status = execSync('git status --porcelain', {
+				cwd: this.projectRoot,
+				encoding: 'utf-8',
+				timeout: 5000
+			});
+			if (status.trim().length > 0) {
+				return {
+					success: false,
+					value: 'dirty',
+					message:
+						'Working tree has uncommitted or untracked changes. Please commit or stash them.'
+				};
+			}
+			return {
+				success: true,
+				value: 'clean',
+				message: 'Working tree is clean'
+			};
+		} catch (error: any) {
+			return {
+				success: false,
+				message: `Git check failed: ${error.message}`
+			};
+		}
+	}
+
+	/**
+	 * Detect project types based on common configuration files
+	 */
+	private detectProjectTypes(): string[] {
+		const types: string[] = [];
+
+		if (existsSync(join(this.projectRoot, 'package.json'))) types.push('node');
+		if (
+			existsSync(join(this.projectRoot, 'requirements.txt')) ||
+			existsSync(join(this.projectRoot, 'setup.py')) ||
+			existsSync(join(this.projectRoot, 'pyproject.toml'))
+		)
+			types.push('python');
+		if (
+			existsSync(join(this.projectRoot, 'pom.xml')) ||
+			existsSync(join(this.projectRoot, 'build.gradle'))
+		)
+			types.push('java');
+		if (existsSync(join(this.projectRoot, 'go.mod'))) types.push('go');
+		if (existsSync(join(this.projectRoot, 'Cargo.toml'))) types.push('rust');
+		if (existsSync(join(this.projectRoot, 'composer.json'))) types.push('php');
+		if (existsSync(join(this.projectRoot, 'Gemfile'))) types.push('ruby');
+		const files = readdirSync(this.projectRoot);
+		if (files.some((f) => f.endsWith('.csproj') || f.endsWith('.sln')))
+			types.push('dotnet');
+
+		return types;
+	}
+
+	/**
+	 * Get required tools for a project type
+	 */
+	private getToolsForProjectType(
+		type: string
+	): Array<{ command: string; args: string[] }> {
+		const toolMap: Record<
+			string,
+			Array<{ command: string; args: string[] }>
+		> = {
+			node: [
+				{ command: 'node', args: ['--version'] },
+				{ command: 'npm', args: ['--version'] }
+			],
+			python: [
+				{ command: 'python3', args: ['--version'] },
+				{ command: 'pip3', args: ['--version'] }
+			],
+			java: [{ command: 'java', args: ['--version'] }],
+			go: [{ command: 'go', args: ['version'] }],
+			rust: [{ command: 'cargo', args: ['--version'] }],
+			php: [
+				{ command: 'php', args: ['--version'] },
+				{ command: 'composer', args: ['--version'] }
+			],
+			ruby: [
+				{ command: 'ruby', args: ['--version'] },
+				{ command: 'bundle', args: ['--version'] }
+			],
+			dotnet: [{ command: 'dotnet', args: ['--version'] }]
+		};
+
+		return toolMap[type] || [];
+	}
+
+	/**
+	 * Validate required tools availability
+	 */
+	async validateRequiredTools(): Promise<CheckResult> {
+		const tools: ToolCheck[] = [];
+
+		// Always check git and gh CLI
+		tools.push(this.checkTool('git', ['--version']));
+		tools.push(await this.checkGhCli());
+
+		// Detect project types and check their tools
+		const projectTypes = this.detectProjectTypes();
+
+		if (projectTypes.length === 0) {
+			logger.warn('No recognized project type detected');
+		} else {
+			logger.info(`Detected project types: ${projectTypes.join(', ')}`);
+		}
+
+		for (const type of projectTypes) {
+			const typeTools = this.getToolsForProjectType(type);
+			for (const tool of typeTools) {
+				tools.push(this.checkTool(tool.command, tool.args));
+			}
+		}
+
+		// Determine overall success
+		const allAvailable = tools.every((tool) => tool.available);
+		const missingTools = tools
+			.filter((tool) => !tool.available)
+			.map((tool) => tool.name);
+
+		if (!allAvailable) {
+			return {
+				success: false,
+				value: tools,
+				message: `Missing required tools: ${missingTools.join(', ')}`
+			};
+		}
+
+		return {
+			success: true,
+			value: tools,
+			message: 'All required tools are available'
+		};
+	}
+
+	/**
+	 * Check if a command-line tool is available
+	 */
+	private checkTool(command: string, versionArgs: string[]): ToolCheck {
+		try {
+			const version = execSync(`${command} ${versionArgs.join(' ')}`, {
+				cwd: this.projectRoot,
+				encoding: 'utf-8',
+				stdio: 'pipe',
+				timeout: 5000
+			})
+				.trim()
+				.split('\n')[0];
+
+			return {
+				name: command,
+				available: true,
+				version,
+				message: `${command} ${version}`
+			};
+		} catch (error) {
+			return {
+				name: command,
+				available: false,
+				message: `${command} not found`
+			};
+		}
+	}
+
+	/**
+	 * Check GitHub CLI installation and authentication status
+	 */
+	private async checkGhCli(): Promise<ToolCheck> {
+		try {
+			const version = execSync('gh --version', {
+				cwd: this.projectRoot,
+				encoding: 'utf-8',
+				stdio: 'pipe',
+				timeout: 5000
+			})
+				.trim()
+				.split('\n')[0];
+			const authed = await isGhCliAvailable(this.projectRoot);
+			return {
+				name: 'gh',
+				available: true,
+				version,
+				message: authed
+					? 'GitHub CLI installed (authenticated)'
+					: 'GitHub CLI installed (not authenticated)'
+			};
+		} catch {
+			return { name: 'gh', available: false, message: 'GitHub CLI not found' };
+		}
+	}
+
+	/**
+	 * Detect default branch
+	 */
+	async detectDefaultBranch(): Promise<CheckResult> {
+		try {
+			const defaultBranch = await getDefaultBranch(this.projectRoot);
+
+			if (!defaultBranch) {
+				return {
+					success: false,
+					message:
+						'Could not determine default branch. Make sure remote is configured.'
+				};
+			}
+
+			return {
+				success: true,
+				value: defaultBranch,
+				message: `Default branch: ${defaultBranch}`
+			};
+		} catch (error: any) {
+			return {
+				success: false,
+				message: `Failed to detect default branch: ${error.message}`
+			};
+		}
+	}
+
+	/**
+	 * Run all preflight checks
+	 */
+	async runAllChecks(): Promise<PreflightResult> {
+		logger.info('Running preflight checks...');
+
+		const testCommand = await this.detectTestCommand();
+		const gitWorkingTree = await this.checkGitWorkingTree();
+		const requiredTools = await this.validateRequiredTools();
+		const defaultBranch = await this.detectDefaultBranch();
+
+		const allSuccess =
+			testCommand.success &&
+			gitWorkingTree.success &&
+			requiredTools.success &&
+			defaultBranch.success;
+
+		// Build summary
+		const passed: string[] = [];
+		const failed: string[] = [];
+
+		if (testCommand.success) passed.push('Test command');
+		else failed.push('Test command');
+
+		if (gitWorkingTree.success) passed.push('Git working tree');
+		else failed.push('Git working tree');
+
+		if (requiredTools.success) passed.push('Required tools');
+		else failed.push('Required tools');
+
+		if (defaultBranch.success) passed.push('Default branch');
+		else failed.push('Default branch');
+
+		const total = passed.length + failed.length;
+		const summary = allSuccess
+			? `All preflight checks passed (${passed.length}/${total})`
+			: `Preflight checks failed: ${failed.join(', ')} (${passed.length}/${total} passed)`;
+
+		logger.info(summary);
+
+		return {
+			success: allSuccess,
+			testCommand,
+			gitWorkingTree,
+			requiredTools,
+			defaultBranch,
+			summary
+		};
+	}
+}

packages/tm-core/src/services/task-loader.service.ts

@@ -0,0 +1,401 @@
+/**
+ * @fileoverview Task Loader Service
+ * Loads and validates tasks for autopilot execution
+ */
+
+import type { Task, Subtask, TaskStatus } from '../types/index.js';
+import { TaskService } from './task-service.js';
+import { ConfigManager } from '../config/config-manager.js';
+import { getLogger } from '../logger/factory.js';
+
+const logger = getLogger('TaskLoader');
+
+/**
+ * Validation error types
+ */
+export type ValidationErrorType =
+	| 'task_not_found'
+	| 'task_completed'
+	| 'no_subtasks'
+	| 'circular_dependencies'
+	| 'missing_dependencies'
+	| 'invalid_structure';
+
+/**
+ * Validation result for task loading
+ */
+export interface TaskValidationResult {
+	/** Whether validation passed */
+	success: boolean;
+	/** Loaded task (only present if validation succeeded) */
+	task?: Task;
+	/** Error type */
+	errorType?: ValidationErrorType;
+	/** Human-readable error message */
+	errorMessage?: string;
+	/** Actionable suggestion for fixing the error */
+	suggestion?: string;
+	/** Dependency analysis (only for dependency errors) */
+	dependencyIssues?: DependencyIssue[];
+}
+
+/**
+ * Dependency issue details
+ */
+export interface DependencyIssue {
+	/** Subtask ID with the issue */
+	subtaskId: string;
+	/** Type of dependency issue */
+	issueType: 'circular' | 'missing' | 'invalid';
+	/** Description of the issue */
+	message: string;
+	/** The problematic dependency reference */
+	dependencyRef?: string;
+}
+
+/**
+ * TaskLoaderService loads and validates tasks for autopilot execution
+ */
+export class TaskLoaderService {
+	private taskService: TaskService | null = null;
+	private projectRoot: string;
+
+	constructor(projectRoot: string) {
+		if (!projectRoot) {
+			throw new Error('projectRoot is required for TaskLoaderService');
+		}
+		this.projectRoot = projectRoot;
+	}
+
+	/**
+	 * Ensure TaskService is initialized
+	 */
+	private async ensureInitialized(): Promise<void> {
+		if (this.taskService) return;
+
+		const configManager = await ConfigManager.create(this.projectRoot);
+		this.taskService = new TaskService(configManager);
+		await this.taskService.initialize();
+	}
+
+	/**
+	 * Load and validate a task for autopilot execution
+	 */
+	async loadAndValidateTask(taskId: string): Promise<TaskValidationResult> {
+		logger.info(`Loading task ${taskId}...`);
+
+		// Step 1: Load task
+		const task = await this.loadTask(taskId);
+		if (!task) {
+			return {
+				success: false,
+				errorType: 'task_not_found',
+				errorMessage: `Task with ID "${taskId}" not found`,
+				suggestion:
+					'Use "task-master list" to see available tasks or verify the task ID is correct.'
+			};
+		}
+
+		// Step 2: Validate task status
+		const statusValidation = this.validateTaskStatus(task);
+		if (!statusValidation.success) {
+			return statusValidation;
+		}
+
+		// Step 3: Check for subtasks
+		const subtaskValidation = this.validateSubtasksExist(task);
+		if (!subtaskValidation.success) {
+			return subtaskValidation;
+		}
+
+		// Step 4: Validate subtask structure
+		const structureValidation = this.validateSubtaskStructure(task);
+		if (!structureValidation.success) {
+			return structureValidation;
+		}
+
+		// Step 5: Analyze dependencies
+		const dependencyValidation = this.validateDependencies(task);
+		if (!dependencyValidation.success) {
+			return dependencyValidation;
+		}
+
+		logger.info(`Task ${taskId} validated successfully`);
+
+		return {
+			success: true,
+			task
+		};
+	}
+
+	/**
+	 * Load task using TaskService
+	 */
+	private async loadTask(taskId: string): Promise<Task | null> {
+		try {
+			await this.ensureInitialized();
+			if (!this.taskService) {
+				throw new Error('TaskService initialization failed');
+			}
+			return await this.taskService.getTask(taskId);
+		} catch (error) {
+			logger.error(`Failed to load task ${taskId}:`, error);
+			return null;
+		}
+	}
+
+	/**
+	 * Validate task status is appropriate for autopilot
+	 */
+	private validateTaskStatus(task: Task): TaskValidationResult {
+		const completedStatuses: TaskStatus[] = ['done', 'completed', 'cancelled'];
+
+		if (completedStatuses.includes(task.status)) {
+			return {
+				success: false,
+				errorType: 'task_completed',
+				errorMessage: `Task "${task.title}" is already ${task.status}`,
+				suggestion:
+					'Autopilot can only execute tasks that are pending or in-progress. Use a different task.'
+			};
+		}
+
+		return { success: true };
+	}
+
+	/**
+	 * Validate task has subtasks
+	 */
+	private validateSubtasksExist(task: Task): TaskValidationResult {
+		if (!task.subtasks || task.subtasks.length === 0) {
+			return {
+				success: false,
+				errorType: 'no_subtasks',
+				errorMessage: `Task "${task.title}" has no subtasks`,
+				suggestion: this.buildExpansionSuggestion(task)
+			};
+		}
+
+		return { success: true };
+	}
+
+	/**
+	 * Build helpful suggestion for expanding tasks
+	 */
+	private buildExpansionSuggestion(task: Task): string {
+		const suggestions: string[] = [
+			`Autopilot requires tasks to be broken down into subtasks for execution.`
+		];
+
+		// Add expansion command suggestion
+		suggestions.push(`\nExpand this task using:`);
+		suggestions.push(`  task-master expand --id=${task.id}`);
+
+		// If task has complexity analysis, mention it
+		if (task.complexity || task.recommendedSubtasks) {
+			suggestions.push(
+				`\nThis task has complexity analysis available. Consider reviewing it first:`
+			);
+			suggestions.push(`  task-master show ${task.id}`);
+		} else {
+			suggestions.push(
+				`\nOr analyze task complexity first to determine optimal subtask count:`
+			);
+			suggestions.push(`  task-master analyze-complexity --from=${task.id}`);
+		}
+
+		return suggestions.join('\n');
+	}
+
+	/**
+	 * Validate subtask structure
+	 */
+	private validateSubtaskStructure(task: Task): TaskValidationResult {
+		for (const subtask of task.subtasks) {
+			// Check required fields
+			if (!subtask.title || !subtask.description) {
+				return {
+					success: false,
+					errorType: 'invalid_structure',
+					errorMessage: `Subtask ${task.id}.${subtask.id} is missing required fields`,
+					suggestion:
+						'Subtasks must have title and description. Re-expand the task or manually fix the subtask structure.'
+				};
+			}
+
+			// Validate dependencies are arrays
+			if (subtask.dependencies && !Array.isArray(subtask.dependencies)) {
+				return {
+					success: false,
+					errorType: 'invalid_structure',
+					errorMessage: `Subtask ${task.id}.${subtask.id} has invalid dependencies format`,
+					suggestion:
+						'Dependencies must be an array. Fix the task structure manually.'
+				};
+			}
+		}
+
+		return { success: true };
+	}
+
+	/**
+	 * Validate subtask dependencies
+	 */
+	private validateDependencies(task: Task): TaskValidationResult {
+		const issues: DependencyIssue[] = [];
+		const subtaskIds = new Set(task.subtasks.map((st) => String(st.id)));
+
+		for (const subtask of task.subtasks) {
+			const subtaskId = `${task.id}.${subtask.id}`;
+
+			// Check for missing dependencies
+			if (subtask.dependencies && subtask.dependencies.length > 0) {
+				for (const depId of subtask.dependencies) {
+					const depIdStr = String(depId);
+
+					if (!subtaskIds.has(depIdStr)) {
+						issues.push({
+							subtaskId,
+							issueType: 'missing',
+							message: `References non-existent subtask ${depIdStr}`,
+							dependencyRef: depIdStr
+						});
+					}
+				}
+			}
+
+			// Check for circular dependencies
+			const circularCheck = this.detectCircularDependency(
+				subtask,
+				task.subtasks,
+				new Set()
+			);
+
+			if (circularCheck) {
+				issues.push({
+					subtaskId,
+					issueType: 'circular',
+					message: `Circular dependency detected: ${circularCheck.join(' -> ')}`
+				});
+			}
+		}
+
+		if (issues.length > 0) {
+			const errorType =
+				issues[0].issueType === 'circular'
+					? 'circular_dependencies'
+					: 'missing_dependencies';
+
+			return {
+				success: false,
+				errorType,
+				errorMessage: `Task "${task.title}" has dependency issues`,
+				suggestion:
+					'Fix dependency issues manually or re-expand the task:\n' +
+					issues
+						.map((issue) => `  - ${issue.subtaskId}: ${issue.message}`)
+						.join('\n'),
+				dependencyIssues: issues
+			};
+		}
+
+		return { success: true };
+	}
+
+	/**
+	 * Detect circular dependencies using depth-first search
+	 */
+	private detectCircularDependency(
+		subtask: Subtask,
+		allSubtasks: Subtask[],
+		visited: Set<string>
+	): string[] | null {
+		const subtaskId = String(subtask.id);
+
+		if (visited.has(subtaskId)) {
+			return [subtaskId];
+		}
+
+		visited.add(subtaskId);
+
+		if (subtask.dependencies && subtask.dependencies.length > 0) {
+			for (const depId of subtask.dependencies) {
+				const depIdStr = String(depId);
+				const dependency = allSubtasks.find((st) => String(st.id) === depIdStr);
+
+				if (dependency) {
+					const circular = this.detectCircularDependency(
+						dependency,
+						allSubtasks,
+						new Set(visited)
+					);
+
+					if (circular) {
+						return [subtaskId, ...circular];
+					}
+				}
+			}
+		}
+
+		return null;
+	}
+
+	/**
+	 * Get ordered subtask execution sequence
+	 * Returns subtasks in dependency order (tasks with no deps first)
+	 */
+	getExecutionOrder(task: Task): Subtask[] {
+		const ordered: Subtask[] = [];
+		const completed = new Set<string>();
+
+		// Keep adding subtasks whose dependencies are all completed
+		while (ordered.length < task.subtasks.length) {
+			let added = false;
+
+			for (const subtask of task.subtasks) {
+				const subtaskId = String(subtask.id);
+
+				if (completed.has(subtaskId)) {
+					continue;
+				}
+
+				// Check if all dependencies are completed
+				const allDepsCompleted =
+					!subtask.dependencies ||
+					subtask.dependencies.length === 0 ||
+					subtask.dependencies.every((depId) => completed.has(String(depId)));
+
+				if (allDepsCompleted) {
+					ordered.push(subtask);
+					completed.add(subtaskId);
+					added = true;
+					break;
+				}
+			}
+
+			// Safety check to prevent infinite loop
+			if (!added && ordered.length < task.subtasks.length) {
+				logger.warn(
+					`Could not determine complete execution order for task ${task.id}`
+				);
+				// Add remaining subtasks in original order
+				for (const subtask of task.subtasks) {
+					if (!completed.has(String(subtask.id))) {
+						ordered.push(subtask);
+					}
+				}
+				break;
+			}
+		}
+
+		return ordered;
+	}
+
+	/**
+	 * Clean up resources
+	 */
+	async cleanup(): Promise<void> {
+		// TaskService doesn't require explicit cleanup
+		// Resources are automatically released when instance is garbage collected
+	}
+}

packages/tm-core/src/utils/git-utils.ts

@@ -0,0 +1,421 @@
+/**
+ * @fileoverview Git utilities for Task Master
+ * Git integration utilities using raw git commands and gh CLI
+ */
+
+import { exec, execSync } from 'child_process';
+import { promisify } from 'util';
+
+const execAsync = promisify(exec);
+
+/**
+ * GitHub repository information
+ */
+export interface GitHubRepoInfo {
+	name: string;
+	owner: { login: string };
+	defaultBranchRef: { name: string };
+}
+
+/**
+ * Check if the specified directory is inside a git repository
+ */
+export async function isGitRepository(projectRoot: string): Promise<boolean> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for isGitRepository');
+	}
+
+	try {
+		await execAsync('git rev-parse --git-dir', { cwd: projectRoot });
+		return true;
+	} catch (error) {
+		return false;
+	}
+}
+
+/**
+ * Synchronous check if directory is in a git repository
+ */
+export function isGitRepositorySync(projectRoot: string): boolean {
+	if (!projectRoot) {
+		return false;
+	}
+
+	try {
+		execSync('git rev-parse --git-dir', {
+			cwd: projectRoot,
+			stdio: 'ignore'
+		});
+		return true;
+	} catch (error) {
+		return false;
+	}
+}
+
+/**
+ * Get the current git branch name
+ */
+export async function getCurrentBranch(
+	projectRoot: string
+): Promise<string | null> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for getCurrentBranch');
+	}
+
+	try {
+		const { stdout } = await execAsync('git rev-parse --abbrev-ref HEAD', {
+			cwd: projectRoot
+		});
+		return stdout.trim();
+	} catch (error) {
+		return null;
+	}
+}
+
+/**
+ * Synchronous get current git branch name
+ */
+export function getCurrentBranchSync(projectRoot: string): string | null {
+	if (!projectRoot) {
+		return null;
+	}
+
+	try {
+		const stdout = execSync('git rev-parse --abbrev-ref HEAD', {
+			cwd: projectRoot,
+			encoding: 'utf8'
+		});
+		return stdout.trim();
+	} catch (error) {
+		return null;
+	}
+}
+
+/**
+ * Get list of all local git branches
+ */
+export async function getLocalBranches(projectRoot: string): Promise<string[]> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for getLocalBranches');
+	}
+
+	try {
+		const { stdout } = await execAsync(
+			'git branch --format="%(refname:short)"',
+			{ cwd: projectRoot, maxBuffer: 10 * 1024 * 1024 }
+		);
+		return stdout
+			.trim()
+			.split('\n')
+			.filter((branch) => branch.length > 0)
+			.map((branch) => branch.trim());
+	} catch (error) {
+		return [];
+	}
+}
+
+/**
+ * Get list of all remote branches
+ */
+export async function getRemoteBranches(
+	projectRoot: string
+): Promise<string[]> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for getRemoteBranches');
+	}
+
+	try {
+		const { stdout } = await execAsync(
+			'git branch -r --format="%(refname:short)"',
+			{ cwd: projectRoot, maxBuffer: 10 * 1024 * 1024 }
+		);
+		const names = stdout
+			.trim()
+			.split('\n')
+			.filter((branch) => branch.length > 0 && !branch.includes('HEAD'))
+			.map((branch) => branch.replace(/^[^/]+\//, '').trim());
+		return Array.from(new Set(names));
+	} catch (error) {
+		return [];
+	}
+}
+
+/**
+ * Check if gh CLI is available and authenticated
+ */
+export async function isGhCliAvailable(projectRoot?: string): Promise<boolean> {
+	try {
+		const options = projectRoot ? { cwd: projectRoot } : {};
+		await execAsync('gh auth status', options);
+		return true;
+	} catch (error) {
+		return false;
+	}
+}
+
+/**
+ * Get GitHub repository information using gh CLI
+ */
+export async function getGitHubRepoInfo(
+	projectRoot: string
+): Promise<GitHubRepoInfo | null> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for getGitHubRepoInfo');
+	}
+
+	try {
+		const { stdout } = await execAsync(
+			'gh repo view --json name,owner,defaultBranchRef',
+			{ cwd: projectRoot }
+		);
+		return JSON.parse(stdout) as GitHubRepoInfo;
+	} catch (error) {
+		return null;
+	}
+}
+
+/**
+ * Get git repository root directory
+ */
+export async function getGitRepositoryRoot(
+	projectRoot: string
+): Promise<string | null> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for getGitRepositoryRoot');
+	}
+
+	try {
+		const { stdout } = await execAsync('git rev-parse --show-toplevel', {
+			cwd: projectRoot
+		});
+		return stdout.trim();
+	} catch (error) {
+		return null;
+	}
+}
+
+/**
+ * Get the default branch name for the repository
+ */
+export async function getDefaultBranch(
+	projectRoot: string
+): Promise<string | null> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for getDefaultBranch');
+	}
+
+	try {
+		// Try to get from GitHub first (if gh CLI is available)
+		if (await isGhCliAvailable(projectRoot)) {
+			const repoInfo = await getGitHubRepoInfo(projectRoot);
+			if (repoInfo && repoInfo.defaultBranchRef) {
+				return repoInfo.defaultBranchRef.name;
+			}
+		}
+
+		// Fallback to git remote info (support non-origin remotes)
+		const remotesRaw = await execAsync('git remote', { cwd: projectRoot });
+		const remotes = remotesRaw.stdout.trim().split('\n').filter(Boolean);
+		if (remotes.length > 0) {
+			const primary = remotes.includes('origin') ? 'origin' : remotes[0];
+			// Parse `git remote show` (preferred)
+			try {
+				const { stdout } = await execAsync(`git remote show ${primary}`, {
+					cwd: projectRoot,
+					maxBuffer: 10 * 1024 * 1024
+				});
+				const m = stdout.match(/HEAD branch:\s+([^\s]+)/);
+				if (m) return m[1].trim();
+			} catch {}
+			// Fallback to symbolic-ref of remote HEAD
+			try {
+				const { stdout } = await execAsync(
+					`git symbolic-ref refs/remotes/${primary}/HEAD`,
+					{ cwd: projectRoot }
+				);
+				return stdout.replace(`refs/remotes/${primary}/`, '').trim();
+			} catch {}
+		}
+		// If we couldn't determine, throw to trigger final fallbacks
+		throw new Error('default-branch-not-found');
+	} catch (error) {
+		// Final fallback - common default branch names
+		const commonDefaults = ['main', 'master'];
+		const branches = await getLocalBranches(projectRoot);
+		const remoteBranches = await getRemoteBranches(projectRoot);
+
+		for (const defaultName of commonDefaults) {
+			if (
+				branches.includes(defaultName) ||
+				remoteBranches.includes(defaultName)
+			) {
+				return defaultName;
+			}
+		}
+
+		return null;
+	}
+}
+
+/**
+ * Check if we're currently on the default branch
+ */
+export async function isOnDefaultBranch(projectRoot: string): Promise<boolean> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for isOnDefaultBranch');
+	}
+
+	try {
+		const [currentBranch, defaultBranch] = await Promise.all([
+			getCurrentBranch(projectRoot),
+			getDefaultBranch(projectRoot)
+		]);
+		return (
+			currentBranch !== null &&
+			defaultBranch !== null &&
+			currentBranch === defaultBranch
+		);
+	} catch (error) {
+		return false;
+	}
+}
+
+/**
+ * Check if the current working directory is inside a Git work-tree
+ */
+export function insideGitWorkTree(): boolean {
+	try {
+		execSync('git rev-parse --is-inside-work-tree', {
+			stdio: 'ignore',
+			cwd: process.cwd()
+		});
+		return true;
+	} catch {
+		return false;
+	}
+}
+
+/**
+ * Sanitize branch name to be a valid tag name
+ */
+export function sanitizeBranchNameForTag(branchName: string): string {
+	if (!branchName || typeof branchName !== 'string') {
+		return 'unknown-branch';
+	}
+
+	// Replace invalid characters with hyphens and clean up
+	return branchName
+		.replace(/[^a-zA-Z0-9_.-]/g, '-') // Replace invalid chars with hyphens (allow dots)
+		.replace(/^-+|-+$/g, '') // Remove leading/trailing hyphens
+		.replace(/-+/g, '-') // Collapse multiple hyphens
+		.toLowerCase() // Convert to lowercase
+		.substring(0, 50); // Limit length
+}
+
+/**
+ * Check if a branch name would create a valid tag name
+ */
+export function isValidBranchForTag(branchName: string): boolean {
+	if (!branchName || typeof branchName !== 'string') {
+		return false;
+	}
+
+	// Check if it's a reserved branch name that shouldn't become tags
+	const reservedBranches = ['main', 'master', 'develop', 'dev', 'head'];
+	if (reservedBranches.includes(branchName.toLowerCase())) {
+		return false;
+	}
+
+	// Check if sanitized name would be meaningful
+	const sanitized = sanitizeBranchNameForTag(branchName);
+	return sanitized.length > 0 && sanitized !== 'unknown-branch';
+}
+
+/**
+ * Git worktree information
+ */
+export interface GitWorktree {
+	path: string;
+	branch: string | null;
+	head: string;
+}
+
+/**
+ * Get list of all git worktrees
+ */
+export async function getWorktrees(
+	projectRoot: string
+): Promise<GitWorktree[]> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for getWorktrees');
+	}
+
+	try {
+		const { stdout } = await execAsync('git worktree list --porcelain', {
+			cwd: projectRoot
+		});
+
+		const worktrees: GitWorktree[] = [];
+		const lines = stdout.trim().split('\n');
+		let current: Partial<GitWorktree> = {};
+
+		for (const line of lines) {
+			if (line.startsWith('worktree ')) {
+				// flush previous entry if present
+				if (current.path) {
+					worktrees.push({
+						path: current.path,
+						branch: current.branch || null,
+						head: current.head || ''
+					});
+					current = {};
+				}
+				current.path = line.substring(9);
+			} else if (line.startsWith('HEAD ')) {
+				current.head = line.substring(5);
+			} else if (line.startsWith('branch ')) {
+				current.branch = line.substring(7).replace('refs/heads/', '');
+			} else if (line === '' && current.path) {
+				worktrees.push({
+					path: current.path,
+					branch: current.branch || null,
+					head: current.head || ''
+				});
+				current = {};
+			}
+		}
+
+		// Handle last entry if no trailing newline
+		if (current.path) {
+			worktrees.push({
+				path: current.path,
+				branch: current.branch || null,
+				head: current.head || ''
+			});
+		}
+
+		return worktrees;
+	} catch (error) {
+		return [];
+	}
+}
+
+/**
+ * Check if a branch is checked out in any worktree
+ * Returns the worktree path if found, null otherwise
+ */
+export async function isBranchCheckedOut(
+	projectRoot: string,
+	branchName: string
+): Promise<string | null> {
+	if (!projectRoot) {
+		throw new Error('projectRoot is required for isBranchCheckedOut');
+	}
+	if (!branchName) {
+		throw new Error('branchName is required for isBranchCheckedOut');
+	}
+
+	const worktrees = await getWorktrees(projectRoot);
+	const worktree = worktrees.find((wt) => wt.branch === branchName);
+	return worktree ? worktree.path : null;
+}

packages/tm-core/src/utils/index.ts

@@ -13,6 +13,25 @@ export {
 	getParentTaskId
 } from './id-generator.js';
 
+// Export git utilities
+export {
+	isGitRepository,
+	isGitRepositorySync,
+	getCurrentBranch,
+	getCurrentBranchSync,
+	getLocalBranches,
+	getRemoteBranches,
+	isGhCliAvailable,
+	getGitHubRepoInfo,
+	getGitRepositoryRoot,
+	getDefaultBranch,
+	isOnDefaultBranch,
+	insideGitWorkTree,
+	sanitizeBranchNameForTag,
+	isValidBranchForTag,
+	type GitHubRepoInfo
+} from './git-utils.js';
+
 // Additional utility exports
 
 /**

scripts/create-worktree.sh

@@ -0,0 +1,71 @@
+#!/bin/bash
+
+# Create a git worktree for parallel Claude Code development
+# Usage: ./scripts/create-worktree.sh [branch-name]
+
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
+WORKTREES_DIR="$(cd "$PROJECT_ROOT/.." && pwd)/claude-task-master-worktrees"
+cd "$PROJECT_ROOT"
+
+# Get branch name (default to current branch with auto/ prefix)
+if [ -z "$1" ]; then
+    CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
+    if [ "$CURRENT_BRANCH" = "HEAD" ]; then
+        echo "Detached HEAD detected. Please specify a branch: ./scripts/create-worktree.sh <branch-name>"
+        exit 1
+    fi
+    BRANCH_NAME="auto/$CURRENT_BRANCH"
+    echo "No branch specified, using: $BRANCH_NAME"
+else
+    BRANCH_NAME="$1"
+fi
+
+# Create worktrees directory if it doesn't exist
+mkdir -p "$WORKTREES_DIR"
+
+# Sanitize branch name for directory (replace / with -)
+DIR_NAME=$(echo "$BRANCH_NAME" | sed 's/\//-/g')
+WORKTREE_PATH="$WORKTREES_DIR/$DIR_NAME"
+
+echo "Creating git worktree..."
+echo "  Branch: $BRANCH_NAME"
+echo "  Path: $WORKTREE_PATH"
+
+# Check if worktree already exists
+if [ -d "$WORKTREE_PATH" ]; then
+    echo "❌ Worktree already exists at: $WORKTREE_PATH"
+    echo "   Remove it first with: git worktree remove $WORKTREE_PATH"
+    exit 1
+fi
+
+# Create worktree (new or existing branch)
+if git show-ref --verify --quiet "refs/heads/$BRANCH_NAME"; then
+  git worktree add "$WORKTREE_PATH" "$BRANCH_NAME"
+elif git remote get-url origin >/dev/null 2>&1 && git ls-remote --exit-code --heads origin "$BRANCH_NAME" >/dev/null 2>&1; then
+  # Create a local branch from the remote and attach worktree
+  git worktree add -b "$BRANCH_NAME" "$WORKTREE_PATH" "origin/$BRANCH_NAME"
+  # Ensure the new branch tracks the remote
+  git -C "$WORKTREE_PATH" branch --set-upstream-to="origin/$BRANCH_NAME" "$BRANCH_NAME"
+else
+  git worktree add -b "$BRANCH_NAME" "$WORKTREE_PATH"
+fi
+
+echo ""
+echo "✅ Worktree created successfully!"
+echo ""
+echo "📂 Location: $WORKTREE_PATH"
+echo "🌿 Branch: $BRANCH_NAME"
+echo ""
+echo "Next steps:"
+echo "  1. cd $WORKTREE_PATH"
+echo "  2. Open with your AI editor:"
+echo "     - Cursor: cursor ."
+echo "     - VS Code: code ."
+echo "     - Windsurf: windsurf ."
+echo "     - Claude Code: claude"
+echo ""
+echo "To remove this worktree later:"
+echo "  git worktree remove $WORKTREE_PATH"

scripts/init.js

@@ -628,12 +628,6 @@ function createProjectStructure(
 	// Copy example_prd.txt to NEW location
 	copyTemplateFile('example_prd.txt', path.join(targetDir, EXAMPLE_PRD_FILE));
 
-	// Copy example_prd_rpg.txt to templates directory
-	copyTemplateFile(
-		'example_prd_rpg.txt',
-		path.join(targetDir, TASKMASTER_TEMPLATES_DIR, 'example_prd_rpg.txt')
-	);
-
 	// Initialize git repository if git is available
 	try {
 		if (initGit === false) {
@@ -862,10 +856,10 @@ function createProjectStructure(
 				)}\n${chalk.white('   ├─ ')}${chalk.dim('Models: Use `task-master models` commands')}\n${chalk.white('   └─ ')}${chalk.dim(
 					'Keys: Add provider API keys to .env (or inside the MCP config file i.e. .cursor/mcp.json)'
 				)}\n${chalk.white('2. ')}${chalk.yellow(
-					'Discuss your idea with AI and ask for a PRD, and save it to .taskmaster/docs/prd.txt'
-				)}\n${chalk.white('   ├─ ')}${chalk.dim('Simple projects: Use ')}${chalk.cyan('example_prd.txt')}${chalk.dim(' template')}\n${chalk.white('   └─ ')}${chalk.dim('Complex systems: Use ')}${chalk.cyan('example_prd_rpg.txt')}${chalk.dim(' template (for dependency-aware task graphs)')}\n${chalk.white('3. ')}${chalk.yellow(
+					'Discuss your idea with AI and ask for a PRD using example_prd.txt, and save it to scripts/PRD.txt'
+				)}\n${chalk.white('3. ')}${chalk.yellow(
 					'Ask Cursor Agent (or run CLI) to parse your PRD and generate initial tasks:'
-				)}\n${chalk.white('   └─ ')}${chalk.dim('MCP Tool: ')}${chalk.cyan('parse_prd')}${chalk.dim(' | CLI: ')}${chalk.cyan('task-master parse-prd .taskmaster/docs/prd.txt')}\n${chalk.white('4. ')}${chalk.yellow(
+				)}\n${chalk.white('   └─ ')}${chalk.dim('MCP Tool: ')}${chalk.cyan('parse_prd')}${chalk.dim(' | CLI: ')}${chalk.cyan('task-master parse-prd scripts/prd.txt')}\n${chalk.white('4. ')}${chalk.yellow(
 					'Ask Cursor to analyze the complexity of the tasks in your PRD using research'
 				)}\n${chalk.white('   └─ ')}${chalk.dim('MCP Tool: ')}${chalk.cyan('analyze_project_complexity')}${chalk.dim(' | CLI: ')}${chalk.cyan('task-master analyze-complexity')}\n${chalk.white('5. ')}${chalk.yellow(
 					'Ask Cursor to expand all of your tasks using the complexity analysis'

scripts/list-worktrees.sh

@@ -0,0 +1,15 @@
+#!/bin/bash
+
+# List all git worktrees with helpful information
+
+set -e
+
+echo "📋 Git Worktrees:"
+echo ""
+git worktree list
+echo ""
+echo "To remove a worktree:"
+echo "  git worktree remove <path>"
+echo ""
+echo "To remove all worktrees:"
+echo "  git worktree list | grep -v '(bare)' | tail -n +2 | awk '{print \$1}' | xargs -I {} git worktree remove {}"

scripts/modules/commands.js

@@ -5111,8 +5111,7 @@ async function runCLI(argv = process.argv) {
 			// Display the upgrade notification first
 			displayUpgradeNotification(
 				updateInfo.currentVersion,
-				updateInfo.latestVersion,
-				updateInfo.highlights
+				updateInfo.latestVersion
 			);
 
 			// Then automatically perform the update

scripts/modules/dependency-manager.js

@@ -312,23 +312,18 @@ async function removeDependency(tasksPath, taskId, dependencyId, context = {}) {
 
 	// Check if the dependency exists by comparing string representations
 	const dependencyIndex = targetTask.dependencies.findIndex((dep) => {
-		// Direct string comparison (handles both numeric IDs and dot notation)
-		const depStr = String(dep);
-		if (depStr === normalizedDependencyId) {
-			return true;
-		}
+		// Convert both to strings for comparison
+		let depStr = String(dep);
 
-		// For subtasks: handle numeric dependencies that might be references to other subtasks
-		// in the same parent (e.g., subtask 1.2 depending on subtask 1.1 stored as just "1")
+		// Special handling for numeric IDs that might be subtask references
 		if (typeof dep === 'number' && dep < 100 && isSubtask) {
+			// It's likely a reference to another subtask in the same parent task
+			// Convert to full format for comparison (e.g., 2 -> "1.2" for a subtask in task 1)
 			const [parentId] = formattedTaskId.split('.');
-			const fullSubtaskRef = `${parentId}.${dep}`;
-			if (fullSubtaskRef === normalizedDependencyId) {
-				return true;
-			}
+			depStr = `${parentId}.${dep}`;
 		}
 
-		return false;
+		return depStr === normalizedDependencyId;
 	});
 
 	if (dependencyIndex === -1) {
@@ -401,9 +396,8 @@ function isCircularDependency(tasks, taskId, chain = []) {
 			task = parentTask.subtasks.find((st) => st.id === subtaskId);
 		}
 	} else {
-		// Regular task - handle both string and numeric task IDs
-		const taskIdNum = parseInt(taskIdStr, 10);
-		task = tasks.find((t) => t.id === taskIdNum || String(t.id) === taskIdStr);
+		// Regular task
+		task = tasks.find((t) => String(t.id) === taskIdStr);
 	}
 
 	if (!task) {

tests/fixture/test-tasks.json

@@ -0,0 +1,14 @@
+{
+  "tasks": [
+    {
+      "id": 1,
+      "dependencies": [],
+      "subtasks": [
+        {
+          "id": 1,
+          "dependencies": []
+        }
+      ]
+    }
+  ]
+}

tests/fixtures/sample-tasks.js

@@ -88,38 +88,3 @@ export const emptySampleTasks = {
 	},
 	tasks: []
 };
-
-export const crossLevelDependencyTasks = {
-	tasks: [
-		{
-			id: 2,
-			title: 'Task 2 with subtasks',
-			description: 'Parent task',
-			status: 'pending',
-			dependencies: [],
-			subtasks: [
-				{
-					id: 1,
-					title: 'Subtask 2.1',
-					description: 'First subtask',
-					status: 'pending',
-					dependencies: []
-				},
-				{
-					id: 2,
-					title: 'Subtask 2.2',
-					description: 'Second subtask that should depend on Task 11',
-					status: 'pending',
-					dependencies: []
-				}
-			]
-		},
-		{
-			id: 11,
-			title: 'Task 11',
-			description: 'Top-level task that 2.2 should depend on',
-			status: 'done',
-			dependencies: []
-		}
-	]
-};

tests/unit/commands.test.js

@@ -279,14 +279,12 @@ describe('Version comparison utility', () => {
 
 describe('Update check functionality', () => {
 	let displayUpgradeNotification;
-	let parseChangelogHighlights;
 	let consoleLogSpy;
 
 	beforeAll(async () => {
 		// Import from @tm/cli instead of commands.js
 		const cliModule = await import('../../apps/cli/src/utils/auto-update.js');
 		displayUpgradeNotification = cliModule.displayUpgradeNotification;
-		parseChangelogHighlights = cliModule.parseChangelogHighlights;
 	});
 
 	beforeEach(() => {
@@ -304,61 +302,6 @@ describe('Update check functionality', () => {
 		expect(consoleLogSpy.mock.calls[0][0]).toContain('1.0.0');
 		expect(consoleLogSpy.mock.calls[0][0]).toContain('1.1.0');
 	});
-
-	test('displays upgrade notification with highlights when provided', () => {
-		const highlights = [
-			'Add Codex CLI provider with OAuth authentication',
-			'Cursor IDE custom slash command support',
-			'Move to AI SDK v5'
-		];
-		displayUpgradeNotification('1.0.0', '1.1.0', highlights);
-		expect(consoleLogSpy).toHaveBeenCalled();
-		const output = consoleLogSpy.mock.calls[0][0];
-		expect(output).toContain('Update Available!');
-		expect(output).toContain('1.0.0');
-		expect(output).toContain('1.1.0');
-		expect(output).toContain("What's New:");
-		expect(output).toContain(
-			'Add Codex CLI provider with OAuth authentication'
-		);
-		expect(output).toContain('Cursor IDE custom slash command support');
-		expect(output).toContain('Move to AI SDK v5');
-	});
-
-	test('displays upgrade notification without highlights section when empty array', () => {
-		displayUpgradeNotification('1.0.0', '1.1.0', []);
-		expect(consoleLogSpy).toHaveBeenCalled();
-		const output = consoleLogSpy.mock.calls[0][0];
-		expect(output).toContain('Update Available!');
-		expect(output).not.toContain("What's New:");
-		expect(output).toContain(
-			'Auto-updating to the latest version with new features and bug fixes'
-		);
-	});
-
-	test('parseChangelogHighlights validates version format to prevent ReDoS', () => {
-		const mockChangelog = `
-## 1.0.0
-
-### Minor Changes
-
-- [#123](https://example.com) Thanks [@user](https://example.com)! - Test feature
-		`;
-
-		// Valid versions should work
-		expect(parseChangelogHighlights(mockChangelog, '1.0.0')).toEqual([
-			'Test feature'
-		]);
-		expect(parseChangelogHighlights(mockChangelog, '1.0.0-rc.1')).toEqual([]);
-
-		// Invalid versions should return empty array (ReDoS protection)
-		expect(parseChangelogHighlights(mockChangelog, 'invalid')).toEqual([]);
-		expect(parseChangelogHighlights(mockChangelog, '1.0')).toEqual([]);
-		expect(parseChangelogHighlights(mockChangelog, 'a.b.c')).toEqual([]);
-		expect(
-			parseChangelogHighlights(mockChangelog, '((((((((((((((((((((((((((((((a')
-		).toEqual([]);
-	});
 });
 
 // -----------------------------------------------------------------------------

tests/unit/dependency-manager.test.js

@@ -4,47 +4,18 @@
 
 import { jest } from '@jest/globals';
 import {
-	sampleTasks,
-	crossLevelDependencyTasks
-} from '../fixtures/sample-tasks.js';
-
-// Create mock functions that we can control in tests
-const mockTaskExists = jest.fn();
-const mockFormatTaskId = jest.fn();
-const mockFindCycles = jest.fn();
-const mockLog = jest.fn();
-const mockReadJSON = jest.fn();
-const mockWriteJSON = jest.fn();
-
-// Mock the utils module using the same pattern as move-task-cross-tag.test.js
-jest.mock('../../scripts/modules/utils.js', () => ({
-	log: mockLog,
-	readJSON: mockReadJSON,
-	writeJSON: mockWriteJSON,
-	taskExists: mockTaskExists,
-	formatTaskId: mockFormatTaskId,
-	findCycles: mockFindCycles,
-	traverseDependencies: jest.fn(() => []),
-	isSilentMode: jest.fn(() => true),
-	findProjectRoot: jest.fn(() => '/test'),
-	resolveEnvVariable: jest.fn(() => undefined),
-	isEmpty: jest.fn((v) =>
-		v == null
-			? true
-			: Array.isArray(v)
-				? v.length === 0
-				: typeof v === 'object'
-					? Object.keys(v).length === 0
-					: false
-	),
-	// Common extras
-	enableSilentMode: jest.fn(),
-	disableSilentMode: jest.fn(),
-	getTaskManager: jest.fn(async () => ({})),
-	getTagAwareFilePath: jest.fn((basePath, _tag, projectRoot = '.') => basePath),
-	readComplexityReport: jest.fn(() => null)
-}));
+	validateTaskDependencies,
+	isCircularDependency,
+	removeDuplicateDependencies,
+	cleanupSubtaskDependencies,
+	ensureAtLeastOneIndependentSubtask,
+	validateAndFixDependencies,
+	canMoveWithDependencies
+} from '../../scripts/modules/dependency-manager.js';
+import * as utils from '../../scripts/modules/utils.js';
+import { sampleTasks } from '../fixtures/sample-tasks.js';
 
+// Mock dependencies
 jest.mock('path');
 jest.mock('chalk', () => ({
 	green: jest.fn((text) => `<green>${text}</green>`),
@@ -56,16 +27,22 @@ jest.mock('chalk', () => ({
 
 jest.mock('boxen', () => jest.fn((text) => `[boxed: ${text}]`));
 
-// Now import SUT after mocks are in place
-import {
-	validateTaskDependencies,
-	isCircularDependency,
-	removeDuplicateDependencies,
-	cleanupSubtaskDependencies,
-	ensureAtLeastOneIndependentSubtask,
-	validateAndFixDependencies,
-	canMoveWithDependencies
-} from '../../scripts/modules/dependency-manager.js';
+// Mock utils module
+const mockTaskExists = jest.fn();
+const mockFormatTaskId = jest.fn();
+const mockFindCycles = jest.fn();
+const mockLog = jest.fn();
+const mockReadJSON = jest.fn();
+const mockWriteJSON = jest.fn();
+
+jest.mock('../../scripts/modules/utils.js', () => ({
+	log: mockLog,
+	readJSON: mockReadJSON,
+	writeJSON: mockWriteJSON,
+	taskExists: mockTaskExists,
+	formatTaskId: mockFormatTaskId,
+	findCycles: mockFindCycles
+}));
 
 jest.mock('../../scripts/modules/ui.js', () => ({
 	displayBanner: jest.fn()
@@ -75,8 +52,8 @@ jest.mock('../../scripts/modules/task-manager.js', () => ({
 	generateTaskFiles: jest.fn()
 }));
 
-// Use a temporary path for test files - Jest will clean up the temp directory
-const TEST_TASKS_PATH = '/tmp/jest-test-tasks.json';
+// Create a path for test files
+const TEST_TASKS_PATH = 'tests/fixture/test-tasks.json';
 
 describe('Dependency Manager Module', () => {
 	beforeEach(() => {
@@ -707,8 +684,6 @@ describe('Dependency Manager Module', () => {
 			// IMPORTANT: Verify no calls to writeJSON with actual tasks.json
 			expect(mockWriteJSON).not.toHaveBeenCalledWith(
 				'tasks/tasks.json',
-				expect.anything(),
-				expect.anything(),
 				expect.anything()
 			);
 		});
@@ -762,8 +737,6 @@ describe('Dependency Manager Module', () => {
 			// IMPORTANT: Verify no calls to writeJSON with actual tasks.json
 			expect(mockWriteJSON).not.toHaveBeenCalledWith(
 				'tasks/tasks.json',
-				expect.anything(),
-				expect.anything(),
 				expect.anything()
 			);
 		});
@@ -777,8 +750,6 @@ describe('Dependency Manager Module', () => {
 			// IMPORTANT: Verify no calls to writeJSON with actual tasks.json
 			expect(mockWriteJSON).not.toHaveBeenCalledWith(
 				'tasks/tasks.json',
-				expect.anything(),
-				expect.anything(),
 				expect.anything()
 			);
 		});
@@ -832,8 +803,6 @@ describe('Dependency Manager Module', () => {
 			// IMPORTANT: Verify no calls to writeJSON with actual tasks.json
 			expect(mockWriteJSON).not.toHaveBeenCalledWith(
 				'tasks/tasks.json',
-				expect.anything(),
-				expect.anything(),
 				expect.anything()
 			);
 		});
@@ -947,297 +916,4 @@ describe('Dependency Manager Module', () => {
 			expect(result.conflicts).toEqual([]);
 		});
 	});
-
-	describe('Cross-level dependency tests (Issue #542)', () => {
-		let originalExit;
-
-		beforeEach(async () => {
-			// Ensure a fresh module instance so ESM mocks apply to dynamic imports
-			jest.resetModules();
-			originalExit = process.exit;
-			process.exit = jest.fn();
-
-			// For ESM dynamic imports, use the same pattern
-			await jest.unstable_mockModule('../../scripts/modules/utils.js', () => ({
-				log: mockLog,
-				readJSON: mockReadJSON,
-				writeJSON: mockWriteJSON,
-				taskExists: mockTaskExists,
-				formatTaskId: mockFormatTaskId,
-				findCycles: mockFindCycles,
-				traverseDependencies: jest.fn(() => []),
-				isSilentMode: jest.fn(() => true),
-				findProjectRoot: jest.fn(() => '/test'),
-				resolveEnvVariable: jest.fn(() => undefined),
-				isEmpty: jest.fn((v) =>
-					v == null
-						? true
-						: Array.isArray(v)
-							? v.length === 0
-							: typeof v === 'object'
-								? Object.keys(v).length === 0
-								: false
-				),
-				enableSilentMode: jest.fn(),
-				disableSilentMode: jest.fn(),
-				getTaskManager: jest.fn(async () => ({})),
-				getTagAwareFilePath: jest.fn(
-					(basePath, _tag, projectRoot = '.') => basePath
-				),
-				readComplexityReport: jest.fn(() => null)
-			}));
-
-			// Also mock transitive imports to keep dependency surface minimal
-			await jest.unstable_mockModule('../../scripts/modules/ui.js', () => ({
-				displayBanner: jest.fn()
-			}));
-			await jest.unstable_mockModule(
-				'../../scripts/modules/task-manager/generate-task-files.js',
-				() => ({ default: jest.fn() })
-			);
-			// Set up test data that matches the issue report
-			// Clone fixture data before each test to prevent mutation issues
-			mockReadJSON.mockImplementation(() =>
-				structuredClone(crossLevelDependencyTasks)
-			);
-
-			// Configure mockTaskExists to properly validate cross-level dependencies
-			mockTaskExists.mockImplementation((tasks, taskId) => {
-				if (typeof taskId === 'string' && taskId.includes('.')) {
-					const [parentId, subtaskId] = taskId.split('.').map(Number);
-					const task = tasks.find((t) => t.id === parentId);
-					return (
-						task &&
-						task.subtasks &&
-						task.subtasks.some((st) => st.id === subtaskId)
-					);
-				}
-
-				const numericId =
-					typeof taskId === 'string' ? parseInt(taskId, 10) : taskId;
-				return tasks.some((task) => task.id === numericId);
-			});
-
-			mockFormatTaskId.mockImplementation((id) => {
-				if (typeof id === 'string' && id.includes('.')) return id; // keep dot notation
-				return parseInt(id, 10); // normalize top-level task IDs to number
-			});
-		});
-
-		afterEach(() => {
-			process.exit = originalExit;
-		});
-
-		test('should allow subtask to depend on top-level task', async () => {
-			const { addDependency } = await import(
-				'../../scripts/modules/dependency-manager.js'
-			);
-
-			// Test the specific scenario from Issue #542: subtask 2.2 depending on task 11
-			await addDependency(TEST_TASKS_PATH, '2.2', 11, { projectRoot: '/test' });
-
-			// Verify we wrote to the test path (and not the real tasks.json)
-			expect(mockWriteJSON).toHaveBeenCalledWith(
-				TEST_TASKS_PATH,
-				expect.anything(),
-				'/test',
-				undefined
-			);
-			expect(mockWriteJSON).not.toHaveBeenCalledWith(
-				'tasks/tasks.json',
-				expect.anything(),
-				expect.anything(),
-				expect.anything()
-			);
-			// Get the specific write call for TEST_TASKS_PATH
-			const writeCall = mockWriteJSON.mock.calls.find(
-				([p]) => p === TEST_TASKS_PATH
-			);
-			expect(writeCall).toBeDefined();
-			const savedData = writeCall[1];
-			const parent2 = savedData.tasks.find((t) => t.id === 2);
-			const subtask22 = parent2.subtasks.find((st) => st.id === 2);
-
-			// Verify the dependency was actually added to subtask 2.2
-			expect(subtask22.dependencies).toContain(11);
-			// Also verify a success log was emitted
-			const successCall = mockLog.mock.calls.find(
-				([level]) => level === 'success'
-			);
-			expect(successCall).toBeDefined();
-			expect(successCall[1]).toContain('2.2');
-			expect(successCall[1]).toContain('11');
-		});
-
-		test('should allow top-level task to depend on subtask', async () => {
-			const { addDependency } = await import(
-				'../../scripts/modules/dependency-manager.js'
-			);
-
-			// Test reverse scenario: task 11 depending on subtask 2.1
-			await addDependency(TEST_TASKS_PATH, 11, '2.1', { projectRoot: '/test' });
-
-			// Stronger assertions for writeJSON call and locating the correct task
-			expect(mockWriteJSON).toHaveBeenCalledWith(
-				TEST_TASKS_PATH,
-				expect.anything(),
-				'/test',
-				undefined
-			);
-			expect(mockWriteJSON).not.toHaveBeenCalledWith(
-				'tasks/tasks.json',
-				expect.anything(),
-				expect.anything(),
-				expect.anything()
-			);
-			const writeCall = mockWriteJSON.mock.calls.find(
-				([p]) => p === TEST_TASKS_PATH
-			);
-			expect(writeCall).toBeDefined();
-			const savedData = writeCall[1];
-			const task11 = savedData.tasks.find((t) => t.id === 11);
-
-			// Verify the dependency was actually added to task 11
-			expect(task11.dependencies).toContain('2.1');
-			// Verify a success log was emitted mentioning both task 11 and subtask 2.1
-			const successCall = mockLog.mock.calls.find(
-				([level]) => level === 'success'
-			);
-			expect(successCall).toBeDefined();
-			expect(successCall[1]).toContain('11');
-			expect(successCall[1]).toContain('2.1');
-		});
-
-		test('should properly validate cross-level dependencies exist', async () => {
-			// Test that validation correctly identifies when a cross-level dependency target doesn't exist
-			mockTaskExists.mockImplementation((tasks, taskId) => {
-				// Simulate task 99 not existing
-				if (taskId === '99' || taskId === 99) {
-					return false;
-				}
-
-				if (typeof taskId === 'string' && taskId.includes('.')) {
-					const [parentId, subtaskId] = taskId.split('.').map(Number);
-					const task = tasks.find((t) => t.id === parentId);
-					return (
-						task &&
-						task.subtasks &&
-						task.subtasks.some((st) => st.id === subtaskId)
-					);
-				}
-
-				const numericId =
-					typeof taskId === 'string' ? parseInt(taskId, 10) : taskId;
-				return tasks.some((task) => task.id === numericId);
-			});
-
-			const { addDependency } = await import(
-				'../../scripts/modules/dependency-manager.js'
-			);
-
-			const exitError = new Error('process.exit invoked');
-			process.exit.mockImplementation(() => {
-				throw exitError;
-			});
-
-			await expect(
-				addDependency(TEST_TASKS_PATH, '2.2', 99, { projectRoot: '/test' })
-			).rejects.toBe(exitError);
-
-			expect(process.exit).toHaveBeenCalledWith(1);
-			expect(mockWriteJSON).not.toHaveBeenCalled();
-			// Verify that an error was reported to the user
-			expect(mockLog).toHaveBeenCalled();
-		});
-
-		test('should remove top-level task dependency from a subtask', async () => {
-			const { addDependency, removeDependency } = await import(
-				'../../scripts/modules/dependency-manager.js'
-			);
-
-			// Start with cloned data and add 11 to 2.2
-			await addDependency(TEST_TASKS_PATH, '2.2', 11, { projectRoot: '/test' });
-
-			// Get the saved data from the add operation
-			const addWriteCall = mockWriteJSON.mock.calls.find(
-				([p]) => p === TEST_TASKS_PATH
-			);
-			expect(addWriteCall).toBeDefined();
-			const dataWithDep = addWriteCall[1];
-
-			// Verify the dependency was added
-			const subtask22AfterAdd = dataWithDep.tasks
-				.find((t) => t.id === 2)
-				.subtasks.find((st) => st.id === 2);
-			expect(subtask22AfterAdd.dependencies).toContain(11);
-
-			// Clear mocks and re-setup mockReadJSON with the modified data
-			jest.clearAllMocks();
-			mockReadJSON.mockImplementation(() => structuredClone(dataWithDep));
-
-			await removeDependency(TEST_TASKS_PATH, '2.2', 11, {
-				projectRoot: '/test'
-			});
-
-			const writeCall = mockWriteJSON.mock.calls.find(
-				([p]) => p === TEST_TASKS_PATH
-			);
-			expect(writeCall).toBeDefined();
-			const saved = writeCall[1];
-			const subtask22 = saved.tasks
-				.find((t) => t.id === 2)
-				.subtasks.find((st) => st.id === 2);
-			expect(subtask22.dependencies).not.toContain(11);
-			// Verify success log was emitted
-			const successCall = mockLog.mock.calls.find(
-				([level]) => level === 'success'
-			);
-			expect(successCall).toBeDefined();
-			expect(successCall[1]).toContain('2.2');
-			expect(successCall[1]).toContain('11');
-		});
-
-		test('should remove subtask dependency from a top-level task', async () => {
-			const { addDependency, removeDependency } = await import(
-				'../../scripts/modules/dependency-manager.js'
-			);
-
-			// Add subtask dependency to task 11
-			await addDependency(TEST_TASKS_PATH, 11, '2.1', { projectRoot: '/test' });
-
-			// Get the saved data from the add operation
-			const addWriteCall = mockWriteJSON.mock.calls.find(
-				([p]) => p === TEST_TASKS_PATH
-			);
-			expect(addWriteCall).toBeDefined();
-			const dataWithDep = addWriteCall[1];
-
-			// Verify the dependency was added
-			const task11AfterAdd = dataWithDep.tasks.find((t) => t.id === 11);
-			expect(task11AfterAdd.dependencies).toContain('2.1');
-
-			// Clear mocks and re-setup mockReadJSON with the modified data
-			jest.clearAllMocks();
-			mockReadJSON.mockImplementation(() => structuredClone(dataWithDep));
-
-			await removeDependency(TEST_TASKS_PATH, 11, '2.1', {
-				projectRoot: '/test'
-			});
-
-			const writeCall = mockWriteJSON.mock.calls.find(
-				([p]) => p === TEST_TASKS_PATH
-			);
-			expect(writeCall).toBeDefined();
-			const saved = writeCall[1];
-			const task11 = saved.tasks.find((t) => t.id === 11);
-			expect(task11.dependencies).not.toContain('2.1');
-			// Verify success log was emitted
-			const successCall = mockLog.mock.calls.find(
-				([level]) => level === 'success'
-			);
-			expect(successCall).toBeDefined();
-			expect(successCall[1]).toContain('11');
-			expect(successCall[1]).toContain('2.1');
-		});
-	});
 });

tests/unit/scripts/modules/task-manager/expand-all-tasks.test.js

@@ -244,53 +244,6 @@ describe('expandAllTasks', () => {
 			);
 		});
 
-		test('should pass complexityReportPath to expandTask when provided in context', async () => {
-			// Arrange
-			const mockComplexityReportPath =
-				'/test/project/.taskmaster/reports/task-complexity-report.json';
-			mockExpandTask.mockResolvedValue({
-				telemetryData: { commandName: 'expand-task', totalCost: 0.05 }
-			});
-
-			// Act
-			const result = await expandAllTasks(
-				mockTasksPath,
-				undefined, // numSubtasks not specified, should use complexity report
-				false,
-				'',
-				false,
-				{
-					session: mockSession,
-					mcpLog: mockMcpLog,
-					projectRoot: mockProjectRoot,
-					tag: 'master',
-					complexityReportPath: mockComplexityReportPath
-				},
-				'json'
-			);
-
-			// Assert
-			expect(result.success).toBe(true);
-			expect(result.expandedCount).toBe(2); // Tasks 1 and 2
-
-			// Verify expandTask was called with complexityReportPath in context
-			expect(mockExpandTask).toHaveBeenCalledWith(
-				mockTasksPath,
-				expect.any(Number), // task id
-				undefined, // numSubtasks
-				false, // useResearch
-				'', // additionalContext
-				expect.objectContaining({
-					session: mockSession,
-					mcpLog: mockMcpLog,
-					projectRoot: mockProjectRoot,
-					tag: 'master',
-					complexityReportPath: mockComplexityReportPath
-				}),
-				false // force
-			);
-		});
-
 		test('should return success with message when no tasks are eligible', async () => {
 			// Arrange - Mock tasks data with no eligible tasks
 			const noEligibleTasksData = {