scrum-dashboard

Centralize Scrum data in scrum.ts with a type-checked schema.

3|1|Updated Feb 3, 2012
One-click install
npx skills add https://github.com/shishi/dotfiles --skill scrum-dashboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scrum-dashboard
Source: https://github.com/shishi/dotfiles/tree/main/claude/skills/scrum-dashboard
Command: npx skills add https://github.com/shishi/dotfiles --skill scrum-dashboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes the Scrum dashboard data stored in scrum.ts, ensuring a single source of truth for backlog, sprint status, and governance artifacts.

Core Features & Use Cases

  • Single source of truth: All Scrum artifacts live in scrum.ts to prevent drift.
  • Type-safe governance: Uses scrum.template.ts to enforce data structures for PBIs, sprints, and DoD.
  • Operational workflow: Use when editing scrum.ts, updating sprint status, or managing the Product Backlog across multiple sprints.
  • Initialization & validation: Initialize dashboards with the provided template and validate with deno checks to ensure type safety and consistency.

Quick Start

Initialize a new dashboard using the scrum.template.ts in this skill directory. Edit scrum.ts to update sprint status and the product_backlog as your project evolves. Validate with: deno check scrum.ts; deno run scrum.ts | jq .

Frequently Asked Questions about scrum-dashboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain a single source of truth for Scrum sprint data and product backlog?

To maintain a single source of truth for Scrum sprint data, centralize all Product Backlog items, sprint statuses, and governance artifacts in a single TypeScript file to prevent configuration drift across multiple sprints.

How does TypeScript enforce data governance for a Scrum dashboard?

TypeScript enforces data governance for a Scrum dashboard by applying a fixed data schema through templates, ensuring that PBIs, sprints, and definitions of done are type-checked for deterministic and safe structural changes.

What is the best way to validate scrum.ts dashboard updates before committing changes?

The best way to validate scrum.ts dashboard updates is by running Deno checks to enforce type safety and consistency, followed by executing the file and piping the output through jq to verify the generated data structure.

Can I use Deno to manage a type-safe Product Backlog across multiple sprints?

Yes, you can use Deno to manage a type-safe Product Backlog by initializing your dashboard with a template, editing the centralized file as sprints evolve, and validating the fixed schema with Deno's native TypeScript checks.

When do I need to update the scrum.ts file for sprint management?

You need to update the scrum.ts file for sprint management whenever editing sprint statuses, modifying the Product Backlog, or managing governance artifacts across multiple active sprints to maintain operational workflow consistency.

Why use a centralized TypeScript file for Scrum governance instead of separate documents?

Using a centralized TypeScript file for Scrum governance prevents data drift between separate documents, enforcing a fixed template schema that type-checks definitions of done and product backlog items for deterministic project tracking.