progress-tracker

To save project progress, you can generate or update a PROGRESS.md file at the project root. This file captures completed work, in-progress items, decisions, and next steps, ensuring context is preserved for seamless handoffs and session resumption.

Maintaining a durable record of work progress involves automating a PROGRESS.md file to track completed tasks and key decisions. It restores session awareness by reading existing content and related in-progress files before updating, preventing context loss.

State persistence for long-running tasks works by capturing project state within a PROGRESS.md file. It logs completed work, known issues, and next steps, allowing the current session to restore awareness and resume work exactly where the previous session stopped.

You do not need an existing file to start tracking workflow documentation. The system can create a new PROGRESS.md file at the project root if one does not exist, or it can read and update your current documentation during a wrap-up.

You can update an existing project management log without data loss. The system reads the current PROGRESS.md content before updating, ensuring previous progress tracking entries, decisions, and known issues are preserved while adding new context.

You should use a progress tracker for project management documentation during long-running tasks, wrap-ups, or handoffs. It is essential whenever resuming context is critical, such as when stopping tasks or transferring work between different agents or sessions.