solo-progress-dashboard

Generates and auto-updates HTML progress dashboards for multi-step tasks.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-progress-dashboard-cjrain-12505614
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solo-progress-dashboard
Source: https://github.com/cjrain-12505614/solo-forge-marketplace/tree/main/solo-forge-v0.6.0/skills/solo-progress-dashboard
Command: npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-progress-dashboard-cjrain-12505614

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step, long-running tasks are hard to track across sessions, and users lose visibility into which stage a task is at. This Skill creates a self-contained HTML dashboard at task start and automatically updates it at every stage transition, so progress is always visible in the browser. ## Core Features & Use Cases - Automatic Dashboard Generation: Detects complex multi-step work (3+ signals such as many stages, multiple files, or long duration) and creates a dashboard after a one-line notice. - Marker-Based Partial Updates: Replaces only dynamic regions between HTML markers (or via a selector-based update map), preserving the static layout and styling; updates are idempotent. - Six Task-Type Templates: Analysis, deliverable pipeline, design, development (TDD), standardization/multi-area, and batch migration types, each adding type-specific sections to a common core (progress bar, step list, current position, next step). - Auto-Refresh Display: Opens the HTML file once in the browser; an embedded visibilitychange/focus script reloads the tab automatically when the file changes. - Use Case: During a multi-stage market research task, the dashboard shows a 29% progress bar (6/21 cells), the current analysis stage, and the next step, updating itself as each stage completes. ## Quick Start Ask the assistant to create a progress dashboard for your current multi-step task and keep it updated as each stage completes.

Frequently Asked Questions about solo-progress-dashboard

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

FAQPage Schema
How do I create a progress dashboard for a multi-step task?▼

Ask for a progress dashboard with phrases like "create a dashboard" or "visualize progress", or let the assistant auto-detect complexity. When three or more signals appear (multiple stages, files, long duration), it announces tracking and generates the HTML dashboard automatically.

How does the HTML dashboard update without reopening the browser tab?▼

The dashboard embeds a JavaScript snippet listening for visibilitychange and focus events that reloads the page when you return to the tab. The assistant only edits the file after the initial open, so the existing tab always shows the latest state without accumulating new tabs.

What task types does the progress dashboard support?▼

Six catalog types are supported: analysis, deliverable pipeline, design, development (TDD), standardization/multi-area, and batch migration. Each adds type-specific sections like verification grids, stage flow bands, review gates, or completion counters on top of a shared five-element core.

How is the progress percentage calculated in the dashboard?▼

Progress uses a pure cell ratio: completed items divided by total items, with no weighting or estimation. For matrix-style tasks it is completed cells over total cells, and side achievements are shown as separate badges rather than mixed into the bar.

When should I not create a new task dashboard?▼

Do not create a new dashboard when a parent project or cycle dashboard already exists; instead update the corresponding item's status in the parent dashboard. Sub-task dashboards are only created when no higher-level dashboard is present.

Where are dashboard HTML files stored?▼

Dashboards are stored at docs/00_관리/dashboards/{task-name}.html, one file per task, creating the folder if missing. On task completion the file is kept and linked from the session log as the final visual snapshot of progress.