follow-up-tasks

Follow-up tasks are structured action items proposed before task completion to track ongoing maintenance, future enhancements, or incomplete scope. You should generate them when project work needs clear delineation to ensure nothing is left undone and scope creep is prevented.

You can categorize follow-up tasks using four predefined types: incomplete_scope, next_steps, tech_debt, and test_gaps. This categorization ensures structured tracking of unfinished work and prevents overlaps with existing tasks across your project workflow.

Yes, the proposeFollowUpTasks mechanism generates clear, non-technical titles for up to three follow-up tasks linked to your current task. This ensures broad audiences can understand the impact without needing engineering knowledge.

To avoid duplicating work, the task proposal mechanism enforces avoidance of overlaps and irrelevance. It limits proposals to up to three high-impact follow-up tasks and optionally links to related files and contexts to enable a smooth handoff.

The main limitation is that generation is capped at a maximum of three follow-up tasks per current task. Additionally, the mechanism focuses on avoiding trivial tasks and irrelevance, but requires clear scope delineation to effectively categorize tech_debt and test_gaps.