follow-up-tasks

Follow-up task generation converts completed work into categorized actionable items using the proposeFollowUpTasks callback, creating up to three tasks sorted into incomplete_scope, next_steps, tech_debt, and test_gaps categories.

The best way to categorize tech debt and test gaps is using the structured four-category system, which automatically sorts derived work into incomplete_scope, next_steps, tech_debt, and test_gaps for clear prioritization.

Yes, follow-up tasks for Agile sprint reviews are created using the proposeFollowUpTasks callback, which links new items to the current task hierarchy and includes relevant file paths and context for traceable downstream creation.

To ensure follow-up task titles are understandable for non-technical members, the system enforces concise, non-technical task titles so non-engineers can quickly read and execute the proposed actions.

Yes, this follow-up task workflow supports critical path project planning by deriving categorized next steps and incomplete scopes from critical path tasks, ensuring high-impact follow-ups are proposed without duplicating existing items.