follow-up-tasks

To identify follow-up tasks before closing a ticket, you can propose categorized follow-ups such as incomplete_scope, next_steps, tech_debt, and test_gaps linked to the current work. This ensures related high-impact work is surfaced and structured for downstream task systems.

Managing tech debt and test gaps when finishing a task involves proposing structured follow-up tasks with clear titles and descriptions. You can categorize these items specifically as tech_debt or test_gaps to ensure they are tracked rather than lost during project closure.

Yes, you can generate multiple task proposals in a single operation for project planning. The skill proposes up to three high-impact follow-up tasks at once, providing clear titles, descriptions, and categories to extend work before closing the current task.

To ensure proposed follow-up tasks are actionable and non-overlapping, the system validates inputs and guides users to craft clear, impact-focused titles and descriptions. This structured approach keeps generated follow-ups distinct and ready for downstream task systems.

No, this task management workflow does not require specific dependencies or components to function. It operates independently to validate inputs and output structured follow-up task proposals, making it easy to integrate into existing project planning workflows.