managing-task-lifecyclelisted

# PairCoder Task Lifecycle ## Decision Tree: Which Command to Use? ``` Is Trello connected? (check: bpsai-pair trello status) │ ├── YES → Use `ttask` commands (primary) │ ├── Start: bpsai-pair ttask start TRELLO-XX │ ├── Complete: bpsai-pair ttask done TRELLO-XX --summary "..." --list "Deployed/Done" │ └── Block: bpsai-pair ttask block TRELLO-XX --reason "..." │ └── NO → Use `task update` commands ├── Start: bpsai-pair task update TASK-XXX --status in_progress ├── Complete: bpsai-pair task update TASK-XXX --status done └── Block: bpsai-pair task update TASK-XXX --status blocked ``` **Rule of thumb:** If you see TRELLO-XX IDs, use `ttask`. If you only have TASK-XXX IDs, use `task update`. ## CRITICAL: Always Use CLI Commands Task state changes MUST go through the CLI to trigger hooks (Trello sync, timers, state updates). **Never** just edit task files or say "marking as done" - run the command. ## Automatic Hooks When you change task status via CLI, these hooks fire automatically: ### On `task update --status in_progress`: - `start_timer` - Begins time tracking - `sync_trello` - Moves card to "In Progress" - `update_state` - Updates state.md current focus ### On `task update --status done`: - `stop_timer` - Stops timer, records duration - `record_metrics` - Records token usage and costs - `record_velocity` - Tracks sprint velocity - `sync_trello` - Moves card to "Deployed/Done" - `update_state` - Updates state.md - `check_unblocked` - Id