tq-triage

To diagnose root causes for blocked or failed tasks, you must review acceptance criteria, execution logs, architecture docs, and Notion comments before resetting any task. This ensures a thorough failure reconstruction and accurate root cause classification for effective recovery.

The best way to run a nightly review for failed task recovery is to query the Task Queue Blocked - Failed view and execute a diagnostic workflow that captures project context, classifies root causes, and generates a recovery hypothesis before taking controlled actions.

You should increment retries or bump budgeted iterations for a blocked task only after completing a full root-cause diagnosis. Controlled actions like resetting tasks or rewriting prompts must follow a confirmed recovery hypothesis to prevent unnecessary resets.

You cannot reset a failed task without reviewing execution logs and Notion comments. The triage process mandates pulling acceptance criteria, project docs, and comments to ensure no context is missed before deciding how to act on the failed task.

Your task triage workflow may keep hitting the same blockers if it lacks a systematic diagnostic framework. Applying intent review, failure reconstruction, and root cause classification before resetting tasks ensures you address the underlying issue rather than just retrying.

Yes, task triage works with Notion comments and standard project docs. The workflow explicitly requires gathering Notion comments, architecture docs, and acceptance criteria to build complete project context before attempting any task recovery actions.