Progress Tracking
Scannednpx machina-cli add skill a5c-ai/babysitter/progress-tracking --openclawProgress Tracking
Maintain progress.md with session logs, test results, error records, and phase status indicators.
Agent
Execution Monitor - pwf-execution-monitor
Workflow
- Initialize progress.md with session header and phase sections
- Log session entries with timestamps during execution
- Record test results and their outcomes
- Track phase completion status indicators
- Detect continuity gaps across sessions
- Analyze progress for verification
Inputs
projectPath- Root path for planning filesphaseName- Current phase nameresult- Phase execution resultiteration- Current iteration number
Outputs
- Updated progress.md with session log and status indicators
- Continuity analysis for verification
Process Files
planning-orchestrator.js- Progress initialization and updatesplanning-execution.js- Phase progress updatesplanning-verification.js- Progress continuity analysis
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/planning-with-files/skills/progress-tracking/SKILL.mdView on GitHub Overview
Progress Tracking keeps progress.md updated with session logs, test results, error records, and phase status indicators. It leverages the Execution Monitor to log timed entries, record outcomes, and surface continuity gaps so teams can verify progress through each project phase.
How This Skill Works
The skill uses planning-orchestrator.js to initialize progress.md with a session header and phase sections, planning-execution.js to log timestamped session entries and update phase progress, and planning-verification.js to analyze continuity across sessions. It outputs an updated progress.md and a continuity verification report to confirm project alignment.
When to Use It
- When starting a new project phase to establish a baseline in progress.md
- During execution to log timestamped session entries and test outcomes
- When a phase completes to record results and update status indicators
- To detect continuity gaps across sessions and verify progress
- For stakeholder reporting and QA to show verified progress against plan
Quick Start
- Step 1: Gather inputs projectPath phaseName result and iteration
- Step 2: Run planning-orchestrator.js to initialize progress.md with session header and phase sections
- Step 3: During execution, use planning-execution.js to log sessions and planning-verification.js to analyze continuity
Best Practices
- Initialize a single progress.md at the project root defined by projectPath
- Use a clear session header and per phase sections to organize data
- Log every session with a timestamp and concise notes
- Record test results with outcomes and any errors observed
- Run continuity analysis after iterations to catch gaps and verify consistency
Example Use Cases
- A multi phase product plan uses progress tracking to visualize phase progression and bottlenecks
- An automated workflow logs each execution step and outcomes into progress.md for auditability
- QA teams verify continuity across sprints by inspecting the progress log and verification results
- Developers surface test results and errors in progress.md to enable rapid triage
- Project managers generate stakeholder reports from the latest progress.md and continuity analysis
