follow-up-tasks

To suggest follow-up tasks before closing a project task, use a controlled workflow that proposes actionable items linked to your current work. This ensures nothing is left unresolved and enables a clean handoff to the next phase.

You can classify follow-up tasks for project management into predefined categories like incomplete_scope, next_steps, tech_debt, and test_gaps to keep the scope clear and actionable.

Task linking for follow-up items works by tying each generated follow-up to the current task, creating a parent-child relationship that preserves the task hierarchy and maintains project context.

You need to propose next steps for code reviews and documentation work before marking your current task complete, ensuring that all test gaps, tech debt, and incomplete scope items are captured as linked tasks.

Yes, you can generate up to three actionable follow-up tasks for a single project wrap-up, provided they are concrete, validated for quality and relevance, and linked directly to the current task.

The best way to ensure follow-up tasks are actionable and non-overlapping is to validate their quality and relevance through a controlled workflow, generating concrete items tied to the current task hierarchy.