progress-tracking
The progress-tracking skill generates standup reports and status dashboards by aggregating task data from GitHub, execution results, and project artifacts. Use it to monitor project completion, identify blockers, manage blocked tasks with categorization and escalation recommendations, and verify work against PRD criteria while synchronizing tracking updates back to GitHub repositories.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/progress-tracking && cp -r /tmp/progress-tracking/library/methodologies/ccpm/skills/progress-tracking ~/.claude/skills/progress-trackingSKILL.md
# 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
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement