scrum-dashboard

atusy's avatarfrom atusy

Maintain scrum.ts dashboard following Agentic Scrum principles. Use when reading and editing scrum.ts, updating sprint status, or managing Product Backlog.

⭐6stars🔀0forks📁View on GitHub🕐Updated Jan 2, 2026

When & Why to Use This Skill

This Claude skill automates the maintenance of a scrum.ts dashboard following Agentic Scrum principles. It centralizes all Scrum artifacts into a single source of truth, allowing for seamless management of product backlogs, sprint statuses, and project history through Git-integrated workflows and automated validation.

Use Cases

  • Product Backlog Management: Automatically organizing and prioritizing backlog items within the scrum.ts file to ensure the most critical tasks are addressed first.
  • Sprint Status Tracking: Updating and maintaining the current status of sprints and tasks, providing real-time visibility into project progress.
  • Project Initialization: Using standardized templates to quickly set up new Scrum dashboards for new repositories or workstreams.
  • Automated Data Validation: Running type checks and JSON queries to ensure the integrity of project data and maintain a clean, compact dashboard structure.
  • Historical Context Tracking: Leveraging Git commit history to track changes and background context for every update made to the Scrum dashboard.
namescrum-dashboard
descriptionMaintain scrum.ts dashboard following Agentic Scrum principles. Use when reading and editing scrum.ts, updating sprint status, or managing Product Backlog.

Core Principles

Principle Practice
Single Source of Truth All Scrum artifacts live in scrum.ts
Git is History Commit every meaningful change on scrum.ts to track the background context and to make timestamps unneeded
Order is Priority Higher in product_backlog array = higher priority
Schema is Fixed Only edit the data section; request human review for type changes

Validation

deno check scrum.ts          # Type check after edits
deno run scrum.ts | jq '.'   # Query data as JSON
wc -l scrum.ts               # Line count (target: ≤300, hard limit: 600)

Compaction

After retrospective, prune if >300 lines:

  • completed: Keep latest 2-3 sprints only
  • retrospectives: Remove completed/abandoned improvements
  • product_backlog: Remove done PBIs

Integration

  • /agentic-scrum:scrum:init - Create new dashboard
    • Use scrum.template.ts in this skill directory as the starting point for new dashboards.
  • @agentic-scrum:scrum:events:* agents - Deep facilitation for sprint events