kanban-heartbeat

To identify stagnant tasks on a Kanban board, this Skill scans active projects for tasks with no agent activity for a configurable number of days. It outputs a Markdown table report detailing project, status, days, and title to surface aging work.

To log heartbeats for inactive Kanban tasks, the Skill optionally appends Heartbeat entries to each task's agent_log. This signals activity needs and aids notifications for stagnant work identified during the Kanban board scan.

Yes, you can scan multiple Kanban projects for aging work at once. The Skill detects stagnant tasks across multiple projects or a single project based on a configurable days-threshold, generating a unified Markdown table report.

The default threshold for detecting stagnant Kanban tasks is 3 days of no agent activity. The Skill scans for tasks with no agent activity for N days, allowing you to configure this threshold to suit your team's workflow.

Yes, you can validate Kanban stagnation reporting without modifying task logs using dry-run mode. This validates scan results and generates the Markdown report without appending heartbeat entries to the agent_log.

Yes, you need credentials to scan Kanban boards for stagnant tasks. The Skill requires access credentials via the standard Kanban auth store to authenticate with the Kanban API for fetching project, board, and task data.