eliteforge-task-progress-tracker

Create and maintain a Markdown task file with git checkpoints.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/CloudSen/eliteforge-skills --skill eliteforge-task-progress-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eliteforge-task-progress-tracker
Source: https://github.com/CloudSen/eliteforge-skills/tree/main/skills/eliteforge-task-progress-tracker
Command: npx skills add https://github.com/CloudSen/eliteforge-skills --skill eliteforge-task-progress-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams manage and persist plan, TODOs, acceptance criteria, and progress for a concrete task by creating and maintaining a single Markdown file under the default docs/tasks/ directory, or a user-specified task directory, with git checkpoints after meaningful changes.

Core Features & Use Cases

  • Default directory: docs/tasks/
  • Creates/updates a task file for each requirement and keeps acceptance criteria in sync with progress
  • Each meaningful change is committed and the commit id is written into the related step note for recovery
  • Supports explicit task directories and integration with other eliteforge skills to coordinate workflows
  • Maintains status and process progress with a structured Steps table for traceability

Quick Start

Create or update the task file under docs/tasks/<task-description>.md and maintain commit-backed checkpoints as work progresses.

Frequently Asked Questions about eliteforge-task-progress-tracker

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

FAQPage Schema
How do I track task progress with git commit checkpoints in markdown?

Track task progress with git commit checkpoints by maintaining a markdown file containing your TODOs and acceptance criteria, where each meaningful change is committed and the commit id is recorded for recovery. This approach ensures traceability and resumable work across interruptions.

What is the best way to maintain resumable work tracking across project interruptions?

Maintain resumable work tracking across project interruptions by creating a single markdown task file under the docs/tasks/ directory, enforcing strict status and process percentages alongside structured steps with commit references for reliable recovery points.

Can I specify a custom task directory instead of using the default docs/tasks/ path?

You can specify a custom task directory instead of using the default docs/tasks/ path. The task tracker supports explicit directories to organize your markdown task files and acceptance criteria according to your project's specific workflow requirements.

How does commit-backed task recovery work for markdown checkpoints?

Commit-backed task recovery works by writing the git commit id into the related step note within your markdown task file after each meaningful change. This creates structured recovery points that map exact progress states to specific repository versions.

Do I need any external dependencies to create commit-backed checkpoints for task tracking?

You do not need any external dependencies to create commit-backed checkpoints for task tracking. The system relies solely on your existing markdown files and git commits to enforce status, process percentages, and traceability without additional components.