Board Hygiene

skill

Keep the board healthy: list tasks, check progress, and close out completed work.

Download .md

Board Hygiene Skill

Keep the shared task board clean and current by listing open tasks, checking their progress, and closing out completed work.

When to use

  • At the start or end of a work session, to see what is claimed, in progress, or stalled.
  • When a delegated task may have finished and needs to be reviewed and closed.
  • Before handing off, to confirm the board reflects real status rather than stale entries.
  • When asked for a status update on fleet work in progress.

Tools

  • list-tasks: pull the current set of tasks on the board, filtered by status, to see what is open, in progress, or blocked.
  • check-task: inspect a specific task's detail and history to confirm what has actually happened on it.
  • complete-task: close out a task with a structured result once its work is verified as done.

Playbook

  1. Call list-tasks to get the full current board state, noting task IDs, statuses, and owners.
  2. Group the results mentally into open, in-progress, blocked, and done-but-unclosed buckets.
  3. For any task whose status looks stale or ambiguous, call check-task on that task ID to read its latest detail and activity.
  4. If check-task shows the task's work is genuinely finished, call complete-task with a concise structured result summarizing what was produced.
  5. If check-task shows a task is blocked, leave it open and note the blocker in your own summary rather than forcing a close.
  6. Repeat steps 3-4 across all tasks flagged in step 2 until every stale or ambiguous entry has been checked.
  7. Re-run list-tasks after closing items to confirm the board now reflects the updated statuses.
  8. If any task needs a field updated (title, description, priority) rather than closed, that requires PATCH/PUT and is NOT POSSIBLE here — compile the needed change into a note and hand it off to a human via send-message.
  9. Summarize the resulting board state (counts open, in progress, blocked, closed this pass) as your own task's result.

Failure modes

  • 401/403 on list-tasks or check-task -> missing Integration for the board; stop and escalate via send-message.
  • Empty result from list-tasks -> verify the filter/status parameters used rather than assuming the board is empty.
  • Rate limit while calling list-tasks or check-task repeatedly -> back off and note the limit in memory via update-memory before retrying.
  • Task detail changed shape or a linked page is referenced -> do not guess; fall back to browser-search to confirm before acting.

Done when

  • list-tasks shows no stale or ambiguous entries left unchecked.
  • Every task confirmed complete via check-task has been closed with complete-task.
  • Any task needing an update beyond closing has been handed off to a human with a clear change list.