Task Mover
Sync task document status when workflow state changes in multi-worker parallel development.
Trigger Conditions
AI Allowed Actions
| Agent Action | Target Section | Checkbox | Pre-requisite |
|---|---|---|---|
| Agent 1 starting work | Worker1 | - [ ] | Run task-segmentation first |
| Agent 2 starting work | Worker2 | - [ ] | Run task-segmentation first |
| Agent 3 starting work | Worker3 | - [ ] | Run task-segmentation first |
| AI completed work | Review | - [ ] | AI MUST stop here |
User/Reviewer Only Actions (AI FORBIDDEN)
| Action | Target Section | Checkbox | Who |
|---|---|---|---|
| User verified task | Done | - [x] | User/Reviewer ONLY |
| User defers task | Backlog | - [ ] | User ONLY |
Section Structure
markdown
## Backlog - Queued, not prioritized ## Worker1 - Agent 1 working (separate git branch) ## Worker2 - Agent 2 working (separate git branch) ## Worker3 - Agent 3 working (separate git branch) ## Review - Done, awaiting user review ## Done - Completed and verified
Movement Rules
- •When moving to Done:
- [ ]→- [x] - •When moving from Done:
- [x]→- [ ] - •Subtasks move with parent
- •Preserve metadata (#tags, !priority, Deadline)
Priority-aware Management
| Priority | Processing Order | Recommended Action |
|---|---|---|
!high | Top priority | Move to Worker immediately if possible |
!medium | Normal processing | Process in order |
!low | Low priority | Process after other tasks are complete |
⚠️ CRITICAL: Format Protection
Absolute Rules:
- •NEVER modify existing Task document structure
- •PRESERVE priority tags (
!high,!medium,!low) when moving tasks - •NEVER change section order, table structure, or markdown format
- •ONLY move task lines between sections and update checkbox state
⚠️ CRITICAL: Task Document Format Rules
Strict Format Requirements:
- •Subtasks MUST use exactly 2-space indentation (no more, no less)
- •NO intermediate grouping headers (e.g.,
### Phase 1,#### Step A) are allowed - •Task hierarchy is flat: Parent task → Subtasks (2-space indent) ONLY
- •When moving tasks, preserve the 2-space indent for all subtasks
⛔ CRITICAL: Duplicate Section Prevention
Before ANY edit, verify document structure:
- •Read entire file first - Check existing section headers
- •Count section occurrences - Each section (
## Backlog,## Worker1, etc.) MUST appear exactly ONCE - •If duplicates found - STOP and fix by merging duplicate sections
Detection Pattern:
code
## Review ← First occurrence (KEEP) ...tasks... ## Done ← First occurrence (KEEP) ...tasks... ## Review ← DUPLICATE (REMOVE - merge tasks to first ## Review) ## Done ← DUPLICATE (REMOVE - merge tasks to first ## Done)
Fix Procedure:
- •Identify all duplicate sections
- •Merge tasks from duplicate sections into first occurrence
- •Delete duplicate section headers and empty lines
- •Verify only ONE of each section exists
Workflow
- •Read entire Task file - Verify no duplicate sections exist
- •Identify task being worked on
- •Check task priority (prioritize
!hightasks) - •Determine new status from agent action
- •If moving to Worker1/Worker2/Worker3: Run
task-segmentationfirst - •Locate task block (partial title match)
- •Move to target section (preserve all metadata)
- •Update checkbox if needed
- •Before saving - Verify no duplicate sections created
- •Save file
⛔ CRITICAL: AI FORBIDDEN ACTIONS
AI MUST NEVER perform these actions:
code
❌ AI CANNOT move Review → Done ❌ AI CANNOT move Review → Backlog ❌ AI CANNOT move Worker → Done directly ❌ AI CANNOT move Worker → Backlog directly ✅ AI CAN: Backlog → Worker (when starting work) ✅ AI CAN: Worker → Review (when completing work)
AI Workflow When Completing Work:
- •AI completes work → Move from Worker → Review
- •AI MUST STOP HERE - Leave task in Review
- •User/Reviewer verifies and moves Review → Done
Related Skills
| Skill | When to Use |
|---|---|
task-segmentation | BEFORE moving task to Worker, segment subtasks into granular items |
task-add | When discovering new work items during implementation |