Progress Tracking
Status dashboards, standup reports, and blocked task management with GitHub synchronization.
Best use case
Progress Tracking is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Status dashboards, standup reports, and blocked task management with GitHub synchronization.
Teams using Progress Tracking should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/progress-tracking/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Progress Tracking Compares
| Feature / Agent | Progress Tracking | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Status dashboards, standup reports, and blocked task management with GitHub synchronization.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Progress Tracking Status dashboards, standup reports, and blocked task management with GitHub synchronization. ## Agent Project Tracker - `project-tracker` ## Workflow 1. Gather current state from all sources (tasks, GitHub, artifacts) 2. Generate standup report (accomplished, in-progress, blockers, next) 3. Manage blocked tasks with categorization and escalation 4. Create status dashboard with stream breakdown and traceability 5. Verify completion against PRD criteria 6. Sync tracking data to GitHub ## Inputs - `projectName` - Project name - `featureName` - Feature identifier - `githubRepo` - GitHub repository (optional) - `tasks` - Task list (optional) - `executionResults` - Execution results (optional) ## Outputs - Standup report with accomplished/in-progress/blockers/next - Status dashboard with visual progress indicators - Blocked task report with resolution suggestions - Completion verification status ## Process Files - `ccpm-tracking.js` - Standalone tracking - `ccpm-orchestrator.js` - Final tracking report
Related Skills
benefits-tracking-dashboard
Track and visualize benefit realization against targets
brand-tracking
Brand health measurement and tracking platform integration
cli-progress-bar-setup
Configure cli-progress with custom formatters, multi-bar support, and ETA calculations for CLI progress indication.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
Streaming Progress
Emit real-time progress events for streaming UI consumption.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.