← ClaudeAtlas

sprint-dashboardlisted

Render, serve, or stop the branded sprint-progress dashboard (`cleargate sprint dashboard`). Use when a human wants a visual view of the active sprint's story states, milestone/wave grouping, token spend by agent, worktrees, and dispatch reports. Triggers: explicit user phrases "show me the dashboard", "open the sprint dashboard", "sprint progress view"; started automatically (best-effort) after `cleargate sprint init` succeeds. Not for CI/automation — this is a human-facing visual surface, not a data source other tooling should scrape (use `state.json` / `token-ledger.jsonl` directly for that).
sandrinio/cleargate · ★ 3 · AI & Automation · score 76
Install: claude install-skill sandrinio/cleargate
# Sprint Dashboard — Branded Progress View (CR-084, CR-097, CR-101, CR-102) A self-contained, zero-network HTML view of the active sprint. Ships inside the `cleargate` CLI binary (`src/dashboard/{collect,render,serve,open,daemon,snapshot}.ts`) — no separate tool file, no payload sync beyond this skill. ## The four modes | Command | What it does | |---|---| | `cleargate sprint dashboard` | Writes `.cleargate/sprint-runs/<id>/dashboard.html` and exits. Opens nothing. The artifact/CI path, and what the SubagentStop hook calls. | | `cleargate sprint dashboard --open` | Ensures a **background** dashboard is running, opens it in the browser, exits 0. This is the one you want. | | `cleargate sprint dashboard --serve` | Runs the server in **this terminal** and blocks until Ctrl-C. The escape hatch. | | `cleargate sprint dashboard --stop` | Terminates the background dashboard and drops its record. | `--port <n>` applies to `--open` and `--serve`. Default `4713`. ## It updates itself (CR-101) The page polls `/data` every ~2s and patches the DOM in place — no reload, no flicker, scroll position and open modals preserved. Two independent things keep it current: - **The live server** re-runs `collect()` on every request, so a served page is never stale by more than one poll tick. - **The snapshot** (`dashboard.html`) is re-rendered whenever its inputs change: after `cleargate state update`, and by the SubagentStop token-ledger hook after each agent completes. Both are best-ef