Task tools not automatically used during multi-step implementations
Summary
When Claude Code has access to task management tools (TaskCreate, TaskList, TaskGet, TaskUpdate), they are not automatically used when implementing larger plans or multi-step work—even though the tool description explicitly states they should be used proactively.
Expected Behavior
According to the TaskCreate tool description:
Use this tool proactively in these scenarios: - Complex multi-step tasks - When a task requires 3 or more distinct steps - Plan mode - When using plan mode, create a task list to track the work - User provides multiple tasks - When users provide a list of things to be done
The expectation is that task tracking would automatically engage when:
- Exiting plan mode with an approved implementation plan
- Starting work that clearly has 3+ distinct steps
- User provides a list of items to work through
Actual Behavior
Task tools remain unused unless the user explicitly requests task tracking. The model acknowledges this is inconsistent behavior but doesn't self-correct.
Proposed Improvement
Consider stronger prompting or a system-level trigger that automatically creates a task list when:
- A plan is approved in plan mode
- The model identifies 3+ implementation steps
- Multiple distinct work items are detected
This would improve visibility into progress for longer-running work and help users understand where Claude is in a multi-step process.
Workaround
Users can add explicit instructions to their CLAUDE.md:
## Task Tracking
Always use TaskCreate for implementations with 3+ steps.
But this feels like behavior that should be default given the tool's stated purpose.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗