AGENT SKILL

sprint-dashboard

Build a visual read-only Jira sprint or board dashboard with atl. USE WHEN the user wants a standup view, WIP picture, or sprint snapshot. DO NOT USE WHEN the output is a narrative report, raw Jira list, or codebase dashboard.

License 许可
Apache-2.0
所属仓库
isukharev/atl
最近更新
2026-09-14
Stars
★ 7
Forks
1

01 前言 Front Matter

name
sprint-dashboard
description
Build a visual read-only Jira sprint or board dashboard with atl. USE WHEN the user wants a standup view, WIP picture, or sprint snapshot. DO NOT USE WHEN the output is a narrative report, raw Jira list, or codebase dashboard.

02 资源文件 1

03 SKILL.md 正文

Sprint dashboard with atl

A decision-support dashboard, not a prose report: its job is to show an engineering manager or tech lead what needs attention. Strictly read-only — never create, update, transition, assign, or comment from this recipe; offer writes as follow-ups only. Command details live in the jira skill.

Make export ATL_READ_ONLY=1 the first statement of every Bash block in this recipe so every later atl call and child process inherits the guard. A prefix on one atl command does not protect later commands in the block. Never override the export in this workflow.

Preflight: atl must be installed and configured. If command -v atl fails or a command exits 7 ("not configured"), run {{atl.setup_cmd}} and stop.

Workflow

1. Resolve scope

<!-- atl:read-only-shell -->

export ATL_READ_ONLY=1
atl jira board list --project KEY --limit 50 # skip when the exact id is supplied
atl jira board config <id>                   # route by Scrum/Kanban and real columns

When discovery is ambiguous, follow each exact next_cursor until the returned page says complete:true; do not repeatedly list boards after the id is known. Treat that qualified flag, not merely an empty cursor, as evidence that the discovery list is terminal. If it is false when absence matters, ask for an exact id. For Scrum, read the active sprint; on exit 4 offer the latest closed sprint or a plain JQL scope. For Kanban, do not invent a sprint—use the normalized board snapshot. If the user gave a project or filter rather than a board, go straight to JQL.

2. Fetch the data

<!-- atl:read-only-shell -->

export ATL_READ_ONLY=1
# Scrum
atl jira sprint current --board <id>
atl jira sprint issues <sprintId> \
  --columns position,key,summary,status,assignee,priority,issuetype,updated \
  --limit 50

# Kanban or another complete board-scope dashboard: keep bulk rows out of chat.
atl jira board export <id> --scope all --limit 0 \
  --columns position,key,summary,status,board.column,assignee,priority,issuetype,updated \
  --format jsonl --out <private-dir>/board.jsonl

Choose one branch, not both. The sprint API caps each call at 50 — paginate with --cursor until exhausted. A native board export returns a small receipt; process its qualified JSONL locally rather than printing the whole snapshot. JQL fallback: atl jira issue search --jql 'project = KEY AND sprint in openSprints()' --columns key,summary,status,assignee,priority,issuetype,updated --limit 100. If anything is still truncated, say so on the dashboard — never present a partial picture as complete.

3. Compute locally (no further API calls)

  • Status columns: use the board's configured ordered columns and keep unmapped statuses explicit. Only label a To Do / In Progress / In Review / Done grouping as heuristic when there is no board configuration.
  • Attention signals: in-progress items not updated for 2+ days; unassigned non-Done work; high-priority items not started; WIP concentration (one assignee holding several in-flight items).
  • Progress: done vs total. This is issue-count math — label it as such unless story points were explicitly fetched (--fields with the instance's points field).

4. Render

Use the richest renderer the current client supports, keeping content identical across formats:

  1. An interactive HTML artifact, when the environment can host one.
  2. Otherwise a self-contained dashboard.html file (inline CSS, no external assets) delivered to the user.
  3. Otherwise markdown in chat.

Layout, in order: header (sprint name, dates, done/total progress bar); a "needs attention" strip — each signal with issue key and one-line reason; status columns with compact cards (key, truncated summary, assignee, priority marker); per-assignee load table; appendix (board/sprint id or JQL, fetch time, truncation notes). Link keys to <jira-url>/browse/KEY. Read only the base URL with a failure-visible local projection:

<!-- atl:read-only-shell -->

export ATL_READ_ONLY=1
set -o pipefail
atl config show | jq -r '.jira_url'

5. Close the loop

After the dashboard, give a three-bullet text digest of the top attention items, then offer — without performing — follow-up writes (assign, move, comment).

04 同仓库更多 Skills

isukharev
isukharev/atl

triage-issue

Triage a bug against Jira with atl before proposing a ticket. USE WHEN an error or stack trace comes with duplicate, prior-fix, or file-a-bug intent. DO NOT USE WHEN debugging code only, inspecting a known issue, or creating an ordinary task.

★ 7
isukharev
isukharev/atl

status-report

Draft an audience-oriented Jira status report with atl. USE WHEN the user wants a weekly/daily progress narrative, blocker summary, or period report. DO NOT USE WHEN the output is a visual dashboard, direct Jira query, knowledge search, or codebase summary.

★ 7
isukharev
isukharev/atl

sprint-dashboard

Build a visual read-only Jira sprint or board dashboard with atl. USE WHEN the user wants a standup view, WIP picture, or sprint snapshot. DO NOT USE WHEN the output is a narrative report, raw Jira list, or codebase dashboard.

★ 7
isukharev
isukharev/atl

spec-to-backlog

Convert a specification into a reviewed Jira epic and backlog with atl. USE WHEN decomposing requirements, RFCs, or designs into linked Jira work. DO NOT USE WHEN the source is meeting notes, only a summary is wanted, or the task is a direct service operation.

★ 7
isukharev
isukharev/atl

setup

Install and configure atl authentication, backends, and mirror defaults. USE WHEN the user explicitly requests install, authentication, setup repair, or /atl:setup. DO NOT USE WHEN handling normal Jira, Confluence, search, reporting, or mirror work; explicit-only.

★ 7
isukharev
isukharev/atl

search-knowledge

Answer from qualified Jira and Confluence evidence with atl. USE WHEN organizational knowledge is unknown or split across both services. DO NOT USE WHEN one exact resource is known, the task is a report/dashboard, or the answer belongs in the codebase.

★ 7