--- name: todoist-project-health-review description: Audit one Todoist project for stalled work, unowned or unassigned tasks, empty or bloated sections, and collaborator gaps, then report findings and offer cleanup options without changing anything until the user approves. Use when the user asks how a project is doing, wants a project audit or cleanup, asks what is stuck in a project, or wants to know who is working on what in a project. --- # Review the health of one Todoist project This is an audit of a single project. The question is: **is this project still a working plan, or has it become a pile of old intentions?** Read everything first, report, then propose cleanup. Nothing is changed in this job. ## 1. Pin down the project and the account Confirm which Todoist account and workspace the user means, and resolve the project with `find-projects`. If several projects match the name, list them and ask which one. Note whether the project belongs to a workspace, since collaborator data and assignments depend on it. Do not switch accounts or workspaces to find the project. If the project is not visible to the current account, say so and stop. Changing the active account or workspace needs the user's explicit yes. ## 2. Pull the project's contents in bounded pages Use `find-tasks` scoped to the project, and `find-sections` for its structure. Page through results rather than loading everything at once. For a large project, sample the oldest and newest tasks plus every task in a section that looks problematic, and say that you sampled. Use `find-completed-tasks` only to answer "is anything moving?", over a recent window. Do not pull a whole year of history to judge health. Use `find-project-collaborators` to see who is on the project, so you can tell "unassigned" apart from "assigned to someone who left". ## 3. Check the signals, in this order Work through these checks and record a count and a few example tasks for each: 1. **Stalled work.** Open tasks with a due date far in the past and no recent activity. Overdue by a few days is normal; overdue by months is a signal that the task is dead or was never triaged. Use `find-activity` on a few of the oldest tasks to see whether anyone has touched them. 2. **Unowned work.** Tasks with no assignee in a project that has collaborators. In a solo project, ignore this check. A task with no owner is not automatically a problem; it matters when the project is shared and the task is due soon. 3. **Assignments to people who are not active.** Tasks assigned to someone not in the current collaborator list. Treat as a likely gap, and say it is likely rather than certain. 4. **Empty sections.** Sections with zero open tasks. Usually leftover scaffolding. Harmless alone, but a project full of them is hard to scan. 5. **Bloated sections.** A section with dozens of open tasks is a holding pen, not a plan. Flag it when it holds a large share of the project's open tasks. 6. **Stale completions.** If `find-completed-tasks` shows nothing over the window and the project still has open overdue work, the project is probably abandoned rather than busy. Say which, if the evidence allows. 7. **Duplicates.** Near-identical task titles in one section. Flag a few examples, do not declare duplicates from titles alone. ## 4. Separate what the data shows from what it suggests Each finding is one of: - **Shown:** a count or a dated fact (e.g. "34 open tasks, 21 overdue by more than 60 days"). - **Suggested:** an interpretation that needs the user's knowledge (e.g. "this looks abandoned"). Do not present suggestions as facts. A project with many overdue tasks may be an active backlog the user is deliberately keeping. ## 5. Offer options, do not act For each finding, offer cleanup options the user can pick from, for example: close out or re-date the stalled tasks, assign or drop the unowned ones, merge or remove empty sections, split a bloated section into new ones. Each option that writes to Todoist (`update-projects`, `complete-tasks`, `delete-object`, `add-sections`, `manage-assignments`, `project-move`) requires the user's explicit yes before it runs, and each should be listed with the exact tasks it would affect. ## Common patterns and traps - **The backlog that is not dead.** A long overdue list in a project the user checks rarely may be a shelf of ideas. Ask before recommending archival. - **Assignment is not progress.** A task can be assigned and untouched for months. Check activity before calling it in progress. - **Sample bias.** If you looked at the newest 50 tasks, say so; the old tail may look very different. - **Solo projects.** Collaborator checks are meaningless there. Do not report "no owner" for tasks in a personal project. - **Deleting is not reversible from this job.** Recommend removal only when the task is clearly a duplicate or empty, and never bundle deletions into a general "cleanup" option. - **Do not confuse health with volume.** A project with 200 open tasks and steady completions can be healthier than one with 12 untouched ones. ## Output ``` Project: () Open tasks: , overdue: , sections: , collaborators: Activity window checked: , completed in window: Findings 1. Stalled work: — e.g. "" (due , no activity since ) 2. Unowned work: — ... 3. Assignments to inactive people: — ... 4. Empty sections: 5. Bloated sections: ( open tasks) 6. Possible duplicates: Overall read: , with the reasoning, marked as suggestion Cleanup options (none applied): A.