follow-up-tasks

Automating follow-up task proposals involves identifying and categorizing completed tasks, then generating up to 3 linked follow-up tasks. This ensures no critical project workflow steps are overlooked before marking a task complete.

Follow-up tasks are categorized into 'incomplete_scope', 'next_steps', 'tech_debt', or 'test_gaps'. This classification helps identify specific areas requiring further action within the project workflow.

Yes, Python is required for task management and categorization. The scripts component executes the logic to identify task gaps, propose follow-ups, and link them to the parent task.

Yes, the task follow-up proposal mechanism generates clear, non-technical titles for tasks. This ensures that proposed follow-ups are user-friendly and easily understood across the project team.

The system proposes up to 3 follow-up tasks per completed parent task. It ensures one-shot proposals, meaning follow-ups are generated only once per task to prevent duplicate task entries.

Follow-up tasks are linked directly to the parent task to maintain a correct task hierarchy. This integration ensures that proposed next steps, tech debt, and test gaps are properly tracked under their originating task.