progress-dashboard

Serve a local web dashboard for roadmap progress from a JSON file.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mikefullerton/cat-herding --skill progress-dashboard-mikefullerton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: progress-dashboard
Source: https://github.com/mikefullerton/cat-herding/tree/main/skills/progress-dashboard
Command: npx skills add https://github.com/mikefullerton/cat-herding --skill progress-dashboard-mikefullerton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Visualizing the real-time progress of roadmap work on a local machine eliminates the guesswork and status meetings by providing a single source of truth for task progress and events.

Core Features & Use Cases

  • Local web dashboard served by a small HTTP server to present steps, events, and ETA.
  • Real-time progress updates via the dash CLI or by editing the JSON progress file, enabling team-wide visibility.
  • Use Case: Track a multi-step feature rollout, monitor per-step status, and review a chronological event log during implementation.

Quick Start

Start the dashboard by running the dash CLI to initialize the dashboard and load a roadmap file.

Frequently Asked Questions about progress-dashboard

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

FAQPage Schema
How do I track roadmap progress with a local dashboard?

Track roadmap progress by running the dash CLI to initialize a local HTTP server that serves a live UI, providing a real-time view of task steps and events.

What is a local progress dashboard used for?

A local progress dashboard is used for visualizing the real-time execution of multi-step roadmaps, displaying per-step status, ETAs, and a chronological event log.

Can I update the roadmap progress file without using the CLI?

Yes, you can update the roadmap progress without the CLI by directly editing the underlying JSON progress model, which the local HTTP server reads to reflect changes on the dashboard.

Does the progress dashboard require a remote server to host the UI?

No, the progress dashboard does not require a remote server; it uses a tiny local HTTP server running on your machine to serve the UI and present steps, events, and ETA.

What is the best way to coordinate multi-step feature rollouts locally?

The best way to coordinate multi-step feature rollouts locally is using a JSON progress model served by a small HTTP server, enabling team-wide visibility into step status and a chronological event log.