task-mover

Task-mover syncs task status by automatically moving tasks between sections—Backlog, Worker1, Worker2, Worker3, Review, and Done—as work progresses. Tasks move to a Worker section when assignment begins and to Review upon completion, maintaining metadata like priority tags and deadlines throughout.

Task-mover enforces a staged workflow: tasks flow from Backlog to an assigned Worker section, then to Review, and finally to Done. AI agents can only move tasks to Worker or Review sections; only users or reviewers can move tasks to Done or back to Backlog, preventing accidental status changes.

Yes, task-mover preserves all metadata—priority tags, deadlines, and other properties—during section movements. It maintains exact markdown format, section order, and two-space indentation for subtasks, preventing data loss or formatting corruption across worker transitions.

Tasks must be properly segmented before AI moves them to Worker sections. AI cannot move tasks directly to Done or Backlog sections. Task-mover prevents duplicates and cross-section conflicts, and requires strict adherence to the Task.md format with correct section structure.

Task-mover enforces 1:1 task propagation with strict format validation, preventing duplicates and cross-section issues. Each task moves as a single unit between sections with all metadata intact, eliminating the risk of tasks appearing in multiple sections simultaneously.