dashboard
dashboard
Overview
Workflow to get a quick overview of project health by checking task counts by status, current in-progress tasks, and high-priority ready tasks.
Workflow
1. Get task counts by status
agkan task count --json
Display a summary table of all statuses:
| Status | Count |
|---|---|
| icebox | N |
| backlog | N |
| ready | N |
| in_progress | N |
| review | N |
| done | N |
| closed | N |
| total | N |
2. Show in-progress tasks
agkan task list --status in_progress --json
Display each in-progress task with its ID, title, and priority (from metadata).
3. Show high-priority ready tasks
agkan task list --status ready --json
Filter and display tasks where metadata contains priority: critical or priority: high.
Display each task with its ID, title, and priority value.
Output Format
Present the dashboard in the following order:
- Status Counts — table showing counts for all statuses
- In Progress (
in_progress) — list of tasks currently being worked on - High Priority Ready (
readywithcriticalorhighpriority) — tasks ready to start with high urgency
Example output:
## Task Dashboard
### Status Counts
| Status | Count |
|------------|-------|
| icebox | 2 |
| backlog | 5 |
| ready | 3 |
| in_progress| 1 |
| review | 0 |
| done | 12 |
| closed | 4 |
| **total** | **27**|
### In Progress
- #5 Implement login feature
### High Priority Ready
- #3 Fix critical bug in payment flow [critical]
- #7 Update authentication library [high]
Notes
- Priority is stored as task metadata with key
priority - Priority values:
critical>high>medium>low - If there are no in-progress tasks or no high-priority ready tasks, display a message indicating none exist
- This skill is read-only and does not modify any tasks
More from gendosu/agkan-skills
agkan-planning-subtask
Use when reviewing a single backlog task to assess decomposition, implementation readiness, and priority ordering.
7agkan
Use when managing tasks with the agkan CLI tool - creating, listing, updating tasks, managing tags, blocking relationships, or tracking project progress with the kanban board.
6agkan-review
Use when checking review tasks against GitHub PR status to automatically move them to done or closed.
6agkan-subtask
Use when a task has been selected and you need to implement it in an isolated (forked) context - handles in_progress update, branch creation, implementation, PR creation, and marking review.
6execute-subtask
[DEPRECATED] Use agkan-subtask instead. Use when a task has been selected and you need to implement it in an isolated (forked) context - handles in_progress update, branch creation, implementation, PR creation, and marking done.
6execute-add
[DEPRECATED] Use agkan-add instead. Use when adding a new task to the backlog — collects title, body, tags, priority, and parent task, then creates it with agkan.
6