#1064 b82d858 Thanks @Crunchyman-ralph! - 🎉 Introducing TaskMaster Extension!
We're thrilled to launch the first version of our Code extension, bringing the power of TaskMaster directly into your favorite code editor. While this is our initial release and we've kept things focused, it already packs powerful features to supercharge your development workflow.
📋 Visual Task Management
- Kanban Board View: Visualize all your tasks in an intuitive board layout directly in VS Code
- Drag & Drop: Easily change task status by dragging cards between columns
- Real-time Updates: See changes instantly as you work through your project
🏷️ Multi-Context Support
- Tag Switching: Seamlessly switch between different project contexts/tags
- Isolated Workflows: Keep different features or experiments organized separately
🤖 AI-Powered Task Updates
- Smart Updates: Use TaskMaster's AI capabilities to update tasks and subtasks
- Context-Aware: Leverages your existing TaskMaster configuration and models
📊 Rich Task Information
- Complexity Scores: See task complexity ratings at a glance
- Subtask Visualization: Expand tasks to view and manage subtasks
- Dependency Graphs: Understand task relationships and dependencies visually
⚙️ Configuration Management
- Visual Config Editor: View and understand your .taskmaster/config.json settings
- Easy Access: No more manual JSON editing for common configuration tasks
🚀 Quick Actions
- Status Updates: Change task status with a single click
- Task Details: Access full task information without leaving VS Code
- Integrated Commands: All TaskMaster commands available through the command palette
🎯 What's Next?
This is just the beginning! We wanted to get a solid foundation into your hands quickly and this release is mostly experimental but fully usable. The extension will evolve rapidly with your feedback, adding more advanced features, better visualizations, and deeper integration with your development workflow. Please send feedback!
Thank you for being part of the TaskMaster journey. Your workflow has never looked better! 🚀
Minor Changes
-
#1064
53903f1
Thanks @eyaltoledano! - Add newscope-up
andscope-down
commands for dynamic task complexity adjustmentThis release introduces two powerful new commands that allow you to dynamically adjust the complexity of your tasks and subtasks without recreating them from scratch.
New CLI Commands:
task-master scope-up
- Increase task complexity (add more detail, requirements, or implementation steps)task-master scope-down
- Decrease task complexity (simplify, remove unnecessary details, or streamline)
Key Features:
- Multiple tasks: Support comma-separated IDs to adjust multiple tasks at once (
--id=5,7,12
) - Strength levels: Choose adjustment intensity with
--strength=light|regular|heavy
(defaults to regular) - Custom prompts: Use
--prompt
flag to specify exactly how you want tasks adjusted - MCP integration: Available as
scope_up_task
andscope_down_task
tools in Cursor and other MCP environments - Smart context: AI considers your project context and task dependencies when making adjustments
Usage Examples:
# Make a task more detailed task-master scope-up --id=5 # Simplify multiple tasks with light touch task-master scope-down --id=10,11,12 --strength=light # Custom adjustment with specific instructions task-master scope-up --id=7 --prompt="Add more error handling and edge cases"
Why use this?
- Iterative refinement: Adjust task complexity as your understanding evolves
- Project phase adaptation: Scale tasks up for implementation, down for planning
- Team coordination: Adjust complexity based on team member experience levels
- Milestone alignment: Fine-tune tasks to match project phase requirements
Perfect for agile workflows where task requirements change as you learn more about the problem space.
Patch Changes
-
#1063
2ae6e7e
Thanks @Crunchyman-ralph! - Fix for tasks not found when using string IDs -
#1049
45a14c3
Thanks @ben-vargas! - Fix tag-specific complexity report detection in expand commandThe expand command now correctly finds and uses tag-specific complexity reports (e.g.,
task-complexity-report_feature-xyz.json
) when operating in a tag context. Previously, it would always look for the generictask-complexity-report.json
file due to a default value in the CLI option definition.