skills.rest
MysMon
MysMonCOMMUNITY
Explore all skills by this author →
GitHub

progress-tracking

Track and persist JSON-based progress across sessions for resumable workflows.

2|Updated Jan 16, 2026
Search Tags:#automation#context#workspace#long-running#resume#multi-session#progress-tracking
One-click install
npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill progress-tracking-mysmon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: progress-tracking
Source: https://github.com/MysMon/Spec-Workflow-Toolkit/tree/main/skills/workflows/progress-tracking
Command: npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill progress-tracking-mysmon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

JSON-based progress tracking for long-running tasks that must span multiple sessions, ensuring continuity and easy resumption.

Core Features & Use Cases

  • Per-workspace progress logs and feature tracking to manage multi-phase work
  • Session-state persistence across context windows to enable resumable workflows
  • Multi-project isolation to prevent cross-workspace interference

Quick Start

Initialize a new progress-tracking workspace and start the first tracking session.

Frequently Asked Questions about progress-tracking

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

FAQPage Schema
How do I track progress for long-running tasks across multiple sessions?▼

Track long-running tasks across multiple sessions by persisting workflow state in a JSON-based progress log. This ensures session continuity and safe recovery after context compaction, enabling resumable workflows for complex projects.

What is the best way to resume a multi-phase migration after a context window resets?▼

Resuming a multi-phase migration after a context window reset requires a resumption context generated from persisted session state. This mechanism safely recovers previous work and continues the workflow exactly where it left off.

How does per-workspace feature tracking prevent cross-project interference?▼

Per-workspace feature tracking prevents cross-project interference by isolating progress logs and session state within each project workspace. This multi-project isolation ensures resumable workflows remain independent and safely contained.

Do I need a specific framework to maintain session continuity across context windows?▼

No specific framework is required to maintain session continuity across context windows. The process relies on a JSON-based progress log and per-workspace feature lists to automatically persist state for resumable workflows.

When should I use automated JSON-based progress logs for software engineering tasks?▼

Use automated JSON-based progress logs for software engineering tasks involving complex projects, database migrations, or multi-phase work. They are essential when workflows require resumable sessions and safe recovery after context compaction.

Related Skills

Explore More Software Engineering Skills→
Shade666Shade666
1

Radberi-UsingGitWorktrees

Create isolated Git worktrees with priority-based directory selection and safety checks.

Community
Advanced
NarubyRiverlioneNarubyRiverlione

task-completion-report

Parse tasks.md to compute per-phase and overall completion percentages.

Community
Basic
Chang-Shih-YungChang-Shih-Yung

checkpoint

Save git state, decisions, and pending tasks into a reusable checkpoint.

Community
Advanced
mishahaninmishahanin
10

setup-browser-cookies

Import Chromium browser cookies into a JSON store for Playwright automation.

Community
Intermediate