follow-up-tasks

To identify follow-up tasks before task completion, review the current task scope to generate up to three categorized follow-up tasks with rationales that link back to the parent task for seamless project handoffs.

The best way to track tech debt and incomplete scope during backlog grooming is to classify generated follow-up tasks into predefined categories like tech_debt and incomplete_scope, attaching them directly to the parent task for clear visibility.

Categorizing follow-up tasks helps with sprint planning by sorting work into incomplete_scope, next_steps, tech_debt, and test_gaps, communicating clear intent to non-technical stakeholders during backlog grooming.

No, you cannot generate more than three follow-up tasks for a single parent task. The Skill proposes up to three high-impact follow-up tasks, each with a concise title and descriptive rationale, to prevent scope creep.

You need to create follow-up tasks for project handoffs when additional work is required after a task is completed, ensuring essential next steps are captured with enough context for teammates to pick up the work easily.

Generating follow-up tasks before completion prevents work from slipping through the cracks by proactively capturing incomplete scope and test gaps, linking these essential downstream actions to the parent task for immediate backlog visibility.