Status dashboards, standup reports, and blocked task management with GitHub synchronization.
Scanned 5/29/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill progress-tracking --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Progress Tracking?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-progress-tracking)More formats (shields.io, HTML) on the badges page.
# 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...