davila7__claude-code-templates/dashboard/public/component-content/commands/orchestration/move.json

{"content": "# Task Move Command\n\nMove tasks between status folders following the task management protocol.\n\n## Usage\n\n```\n/task-move TASK-ID new-status [reason]\n```\n\n## Description\n\nUpdates task status by moving files between status folders and updating tracking information. Follows all protocol rules including validation and audit trails.\n\n## Basic Commands\n\n### Start Working on a Task\n```\n/task-move TASK-001 in_progress\n```\nMoves from todos → in_progress\n\n### Complete Implementation\n```\n/task-move TASK-001 qa \"Implementation complete, ready for testing\"\n```\nMoves from in_progress → qa\n\n### Task Passed QA\n```\n/task-move TASK-001 completed \"All tests passed\"\n```\nMoves from qa → completed\n\n### Block a Task\n```\n/task-move TASK-004 on_hold \"Waiting for TASK-001 API completion\"\n```\nMoves to on_hold with reason\n\n### Unblock a Task\n```\n/task-move TASK-004 todos \"Dependencies resolved\"\n```\nMoves from on_hold → todos\n\n### Failed QA\n```\n/task-move TASK-001 in_progress \"Failed integration test - fixing null pointer\"\n```\nMoves from qa → in_progress\n\n## Bulk Operations\n\n### Move Multiple Tasks\n```\n/task-move TASK-001,TASK-002,TASK-003 in_progress\n```\n\n### Move by Filter\n```\n/task-move --filter \"priority:high status:todos\" in_progress\n```\n\n### Move with Pattern\n```\n/task-move TASK-00* qa \"Batch testing ready\"\n```\n\n## Validation Rules\n\nThe command enforces:\n1. **Valid Transitions**: Only allowed status changes\n2. **One Task Per Agent**: Warns if agent has task in_progress\n3. **Dependency Check**: Warns if dependencies not met\n4. **File Existence**: Verifies task exists before moving\n\n## Status Transition Map\n\n```\ntodos ──────→ in_progress ──────→ qa ──────→ completed\n  ↓               ↓               ↓\n  └───────────→ on_hold ←─────────┘\n                  ↓\n                todos/in_progress\n```\n\n## Options\n\n### Force Move\n```\n/task-move TASK-001 completed --force\n```\nBypasses validation (use with caution)\n\n### Dry Run\n```\n/task-move TASK-001 qa --dry-run\n```\nShows what would happen without executing\n\n### With Assignment\n```\n/task-move TASK-001 in_progress --assign dev-frontend\n```\nAssigns task to specific agent\n\n### With Time Estimate\n```\n/task-move TASK-001 in_progress --estimate 4h\n```\nUpdates time estimate when starting\n\n## Error Handling\n\n### Task Not Found\n```\nError: TASK-999 not found in any status folder\nSuggestion: Use /task-status to see available tasks\n```\n\n### Invalid Transition\n```\nError: Cannot move from 'completed' to 'todos'\nValid transitions from completed: None (terminal state)\n```\n\n### Agent Conflict\n```\nWarning: dev-frontend already has TASK-002 in progress\nContinue? (y/n)\n```\n\n### Dependency Block\n```\nWarning: TASK-004 depends on TASK-001 (currently in_progress)\nMoving to on_hold instead? (y/n)\n```\n\n## Automation\n\n### Auto-move on Completion\n```\n/task-move TASK-001 --auto-progress\n```\nAutomatically moves to next status when conditions met\n\n### Scheduled Moves\n```\n/task-move TASK-005 in_progress --at \"tomorrow 9am\"\n```\n\n### Conditional Moves\n```\n/task-move TASK-007 qa --when \"TASK-006 completed\"\n```\n\n## Examples\n\n### Example 1: Developer Workflow\n```\n# Start work\n/task-move TASK-001 in_progress\n\n# Complete and test\n/task-move TASK-001 qa \"Implementation done, tests passing\"\n\n# After review\n/task-move TASK-001 completed \"Code review approved\"\n```\n\n### Example 2: Handling Blocks\n```\n# Block due to dependency\n/task-move TASK-004 on_hold \"Waiting for auth API from TASK-001\"\n\n# Unblock when ready\n/task-move TASK-004 todos \"TASK-001 now in QA, API available\"\n```\n\n### Example 3: QA Workflow\n```\n# QA picks up task\n/task-move TASK-001 qa --assign qa-engineer\n\n# Found issues\n/task-move TASK-001 in_progress \"Bug: handling empty responses\"\n\n# Fixed and retesting\n/task-move TASK-001 qa \"Bug fixed, ready for retest\"\n```\n\n## Status Update Details\n\nEach move updates:\n1. **File Location**: Physical file movement\n2. **Status Tracker**: TASK-STATUS-TRACKER.yaml entry\n3. **Task Metadata**: Status field in task file\n4. **Execution Tracker**: Overall progress metrics\n\n## Best Practices\n\n1. **Always Provide Reasons**: Especially for blocks and failures\n2. **Check Dependencies**: Before moving to in_progress\n3. **Update Estimates**: When starting work\n4. **Clear Block Reasons**: Help others understand delays\n\n## Integration\n\n- Use after `/task-status` to see available tasks\n- Updates reflected in `/task-report`\n- Triggers notifications if configured\n- Logs all moves for audit trail\n\n## Notes\n\n- Moves are atomic - either fully complete or rolled back\n- Status history is permanent and cannot be edited\n- Timestamp uses current time in ISO-8601 format\n- Agent name is automatically detected from context"}