task-pick

To prioritize in-progress tasks, the workflow verifies tasks in progressing.txt before allowing new selection from to-do.txt, automatically moving task blocks between status files to enforce sequential completion. It skips tasks with unmet dependencies to ensure only ready work is picked.

Dependency-aware task selection works by checking task dependencies before adoption, skipping any tasks with unmet prerequisites to ensure only ready work is picked. It enforces verification of in-progress tasks and handles block movements between to-do.txt, progressing.txt, and done.txt.

Yes, you can use text files for automated task progression. The workflow manages to-do.txt, progressing.txt, and done.txt by implementing file movements, status updates, and verification reporting to guide task progression and maintain development discipline.

The best way to enforce task closure is by implementing a quality gate that verifies in-progress work before closing tasks and adopting new ones. This includes optional Prisma migrations and structured verification reporting to reduce workflow chaos.

You get an automated task briefing by triggering the task selection workflow, which provides a structured plan and next steps for the user. It handles priority, status updates, and reporting to guide ongoing task progression.

Text-based task management handles dependencies by skipping tasks with unmet prerequisites, but it is limited to managing blocks within to-do.txt, progressing.txt, and done.txt. It does not support complex dependency graphs beyond sequential verification and file movements.