* fix(prompts): add JSON output format instruction to complexity analysis prompt
The complexity analysis prompt was missing the final instruction specifying
that output should be a JSON object with a 'complexityAnalysis' key containing
the array of analysis objects. This caused inconsistent output formatting.
This fix ensures the AI model returns properly structured JSON output that
can be reliably parsed by the complexity analysis module.
* chore: add changeset for complexity prompt fix
---------
Co-authored-by: Your Name <you@example.com>
* feat: add support for claude code context
- code context for:
- add-task
- update-subtask
- update-task
- update
* feat: fix CI and format + refactor
* chore: format
* chore: fix broken tests
* chore: fix test
* fix: handle missing @anthropic-ai/claude-code SDK gracefully
Add defensive checks to prevent "Right-hand side of 'instanceof' is not an object" errors when the optional Claude Code SDK is not installed.
Changes:
- Check if AbortError exists before using instanceof
- Check if query function exists before calling it
- Provide clear error messages when SDK is missing
This fixes the issue reported by users in v0.24.0 and v0.25.0 where Task Master would crash with instanceof errors when using the claude-code provider without the SDK installed.
* chore: bump @anthropic-ai/claude-code to ^1.0.88 and regenerate lockfile
* initial cutover
* update log to debug
* update tracker to pass units
* update test to match new base tracker format
* add streamTextService mocks
* remove unused imports
* Ensure the CLI waits for async main() completion
* refactor to reduce code duplication
* update comment
* reuse function
* ensure targetTag is defined in streaming mode
* avoid throwing inside process.exit spy
* check for null
* remove reference to generate
* fix formatting
* fix textStream assignment
* ensure no division by 0
* fix jest chalk mocks
* refactor for maintainability
* Improve bar chart calculation logic for consistent visual representation
* use custom streaming error types; fix mocks
* Update streamText extraction in parse-prd.js to match actual service response
* remove check - doesn't belong here
* update mocks
* remove streaming test that wasn't really doing anything
* add comment
* make parsing logic more DRY
* fix formatting
* Fix textStream extraction to match actual service response
* fix mock
* Add a cleanup method to ensure proper resource disposal and prevent memory leaks
* debounce progress updates to reduce UI flicker during rapid updates
* Implement timeout protection for streaming operations (60-second timeout) with automatic fallback to non-streaming mode.
* clear timeout properly
* Add a maximum buffer size limit (1MB) to prevent unbounded memory growth with very large streaming responses.
* fix formatting
* remove duplicate mock
* better docs
* fix formatting
* sanitize the dynamic property name
* Fix incorrect remaining progress calculation
* Use onError callback instead of console.warn
* Remove unused chalk import
* Add missing custom validator in fallback parsing configuration
* add custom validator parameter in fallback parsing
* chore: fix package-lock.json
* chore: large code refactor
* chore: increase timeout from 1 minute to 3 minutes
* fix: refactor and fix streaming
* Merge remote-tracking branch 'origin/next' into joedanz/parse-prd-progress
* fix: cleanup and fix unit tests
* chore: fix unit tests
* chore: fix format
* chore: run format
* chore: fix weird CI unit test error
* chore: fix format
---------
Co-authored-by: Ralph Khreish <35776126+Crunchyman-ralph@users.noreply.github.com>
* feat: Add Kilo Code integration to TaskMaster
* feat: Add Kilo profile configuration to rule transformer tests
* refactor: Improve code formatting and consistency in Kilo profile and tests
* fix: Correct formatting of workspaces in package.json
* chore: add changeset for Kilo Code integration
* feat: add Kilo Code rules and mode configurations
- Add comprehensive rule sets for all modes (architect, ask, code, debug, orchestrator, test)
- Update .kilocodemodes configuration with mode-specific settings
- Configure MCP integration for Kilo Code profile
- Establish consistent rule structure across all modes
* refactor(kilo): simplify profile to reuse roo rules with replacements
Remove duplicate Kilo-specific rule files and assets in favor of reusing roo rules with dynamic replacements, eliminating 900+ lines of duplicated code while maintaining full Kilo functionality.
The profile now:
- Reuses ROO_MODES constant instead of maintaining separate KILO_MODES
- Applies text replacements to convert roo references to kilo
- Maps roo rule files to kilo equivalents via fileMap
- Removes all duplicate rule files from assets/kilocode directory
* refactor(kilo): restructure object literals for consistency and remove duplicate customReplacements array based on CodeRabbit's suggestion
* chore: remove disabled .mcp.json by mistake
---------
Co-authored-by: Ralph Khreish <35776126+Crunchyman-ralph@users.noreply.github.com>
- Fixed bug where expand task generated generic authentication subtasks
- The complexity-report prompt variant now includes parent task details
- Added comprehensive unit tests to prevent regression
- Added debug logging to help diagnose similar issues
Previously, when using a complexity report with expansionPrompt, only the
expansion guidance was sent to the AI, missing the actual task context.
This caused the AI to generate unrelated generic subtasks.
Fixes the issue where all tasks would get the same generic auth-related
subtasks regardless of their actual purpose (AWS infrastructure, Docker
containerization, etc.)
Co-authored-by: Sadaqat Ali <32377500+sadaqat12@users.noreply.github.com>
* feat(task-104): Complete task 104 - Implement scope-up and scope-down CLI Commands
- Added new CLI commands 'scope-up' and 'scope-down' with comma-separated ID support
- Implemented strength levels (light/regular/heavy) and custom prompt functionality
- Created core complexity adjustment logic with AI integration
- Added MCP tool equivalents for integrated environments
- Comprehensive error handling and task validation
- Full test coverage with TDD approach
- Updated task manager core and UI components
Task 104: Implement 'scope-up' and 'scope-down' CLI Commands for Dynamic Task Complexity Adjustment - Complete implementation with CLI, MCP integration, and testing
* chore: Add changeset for scope-up and scope-down features
- Comprehensive user-facing description with usage examples
- Key features and benefits explanation
- CLI and MCP integration details
- Real-world use cases for agile workflows
* feat(extension): Add scope-up and scope-down to VS Code extension task details
- Added useScopeUpTask and useScopeDownTask hooks in useTaskQueries.ts
- Enhanced AIActionsSection with Task Complexity Adjustment section
- Added strength selection (light/regular/heavy) and custom prompt support
- Integrated scope buttons with proper loading states and error handling
- Uses existing mcpRequest handler for scope_up_task and scope_down_task tools
- Maintains consistent UI patterns with existing AI actions
Extension now supports dynamic task complexity adjustment directly from task details view.
