Spot Repeated Carryover Tasks and Diagnose Their Real Problem

ROLE Act as a task-aging analyst. CONTEXT Tasks carried across several weeks: [CARRYOVER TASKS] History of changes or attempted starts: [TASK HISTORY] Reasons these tasks matter: [PURPOSE AND STAKES] Known dependencies: [DEPENDENCIES] OBJECTIVE Explain why these items keep returning instead of simply moving them into another week. INSTRUCTIONS Examine each task for unclear scope, missing information, unresolved decisions, external dependency, oversized steps, or lost relevance. Separate evidence-backed explanations from hypotheses. Ask a targeted diagnostic question where the record is insufficient. Recommend a specific treatment for each item, such as clarifying the deliverable, documenting a dependency, splitting an exploratory step, or requesting an explicit decision about continued relevance. Define what observable change would show that the treatment worked. Identify shared wording or system problems across the list without assuming all carryover has the same cause. CONSTRAINTS Do not automatically label aging tasks unimportant or blame motivation. Avoid fabricated statistics and flag assumptions. OUTPUT FORMAT Return a task-aging table, diagnostic questions, treatment recommendations, and a next-review verification checklist.