Enhance Task Expansion Rule with Objective Metrics and Structured Templates

[certylion]

Problem Statement

The current task expansion rule relies heavily on subjective assessment, making it difficult to consistently and objectively determine when a task requires breaking down into subtasks. This leads to inconsistent task sizing and potential inefficiencies in project management.

Proposed Solution

Implement a quantitative point-based system with clear thresholds and structured templates to objectively evaluate task complexity and standardize the expansion process.

Key Improvements

1. Quantitative Assessment System

Replace subjective evaluations with a point-based scoring system:

• Assign specific point values to complexity factors (1-3 points each)
• Establish a clear threshold (≥8 points) for recommending task expansion
• Create a standardized assessment table for consistent evaluation

2. Objective Thresholds

Replace ambiguous language with specific metrics:

• "Estimated effort exceeds 16 work hours" instead of "seems likely to take more than a predefined threshold"
• "Task spans 3+ distinct components" instead of "multiple unrelated modules"
• "Contains 7+ distinct acceptance criteria" instead of "exceptionally long sections"
• "Blocks 3+ subsequent tasks" instead of "significant number of subsequent tasks"

3. Red Flag Language Detection

Add automated detection of complexity indicators in task descriptions:

• Excess connector words ("and", "also", "additionally")
• Scope indicators ("multiple features", "comprehensive solution")
• Breadth indicators ("all users", "complete redesign")

4. Enhanced Subtask Template

Extend the subtask recommendation template to include:

• Estimated effort in hours or story points
• Risk assessment (low/medium/high) with details
• MVP designation (Yes/No)
• Parallelization opportunities

5. Domain-specific Templates

Add specialized breakdown templates for:

• Front-end tasks
• Back-end tasks
• Infrastructure tasks

6. Verification Checklist

Include a quality assurance checklist to validate the proposed task breakdown:

• Clear, singular objectives for each subtask
• Minimal and well-defined dependencies
• Complete coverage of original scope
• Identification of critical path and bottlenecks

7. Dependency Visualization

Suggest visualization of task dependencies using Mermaid diagrams for complex task breakdowns

Implementation

1. Update the task-magic/expanding-large-tasks.mdc file with the new rule definition
2. Add the point-based evaluation table
3. Implement the enhanced subtask template
4. Add domain-specific templates and verification checklist

Expected Benefits

• More consistent and objective task sizing
• Clearer subtask definitions with better planning information
• Improved task prioritization and resource allocation
• Better visualization of complex task dependencies
• Reduced occurrence of stalled or blocked tasks

Acceptance Criteria

• Updated rule documentation with quantitative assessment system
• Implementation of point-based evaluation table
• Enhanced subtask template with additional fields
• Domain-specific templates for different project areas
• Verification checklist for quality assurance
• Optional Mermaid diagram support for dependency visualization

Related Documentation

• Current task-magic/expanding-large-tasks.mdc file
• Task Magic system documentation

[BradKML]

Looking at Task Magic, I can see that it is somewhat complementary to Task Master (and memory tools) when it comes to tracking issues, but something like a checklist/criteria or "task fractal" would be useful to make sure there are no breaking changes.

Cross-referencing information eyaltoledano/claude-task-master#900