follow-up-tasks

To propose follow-up tasks, prompt the assistant to identify and surface up to three linked items with clear titles, categories, and descriptions before task completion. It uses proposeFollowUpTasks to link each item to the parent task.

Follow-up tasks are categorized as incomplete_scope, next_steps, tech_debt, or test_gaps. This categorization ensures that scope extensions, actionable next steps, technical debt, and test coverage gaps are tracked as separate units.

Yes, the process produces clear, non-technical titles and descriptions for follow-up tasks. This ensures project stakeholders can easily understand the impact and rationale behind each proposed extension or test gap.

You can propose up to three follow-up tasks before marking your current task complete. This limit ensures thorough completion by focusing on the most relevant incomplete scope, tech debt, or test gaps.

Follow-up tasks surface incomplete scope by creating separate, focused units of work. Instead of extending the current task, you propose linked next steps and tech debt items to ensure additional work is tracked thoroughly.

Yes, this workflow operates independently without requiring external dependencies or components. It focuses on categorizing and proposing follow-up tasks directly within your project management environment.