Description
"Direct quote or clear summary of user request or need or user story."
Motivation
After expanding a complex task into subtasks, the complexity analysis and report still show the task as having the same complexity, suggesting the same solution, even though the task has been expanded and the complexity distributed among subtasks. This makes it less useful as the main task isn't actionable.
Proposed Solution
The complexity of the main task should be delegated to the subtasks if they exist.
High-Level Workflow
When gathering the tasks to analyse, check if the subtasks array isn't empty; if it is, push the list of subtasks instead of the task to be analysed. Or a variation of the same idea that might work best.
Key Elements
- Bullet-point list of technical or UX/UI enhancements
- Mention specific integrations or APIs
- Highlight changes needed in existing data models or commands
Example Workflow
Provide a clear, concrete example demonstrating the feature:
$ task-master analyze-complexity
┌────────────┬─────────────────────────────────────────────┬────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ ID │ Title │ Score │ Subta… │ Expansion Command │
├────────────┼─────────────────────────────────────────────┼────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ 1.1 │ first subtask │ 🔴 9 │ 7 │ task-master expand --id=1.1 --num=7 --prompt="" │
├────────────┼─────────────────────────────────────────────┼────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤Considerations
This might not be the desired behaviour for some people, not sure why, but it might be so, it could be a better option to use --with-subtasks instead