ex-save-progress

Mark current tasks complete and persist progress to progress.json and tasks.json.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ricky-yosh/agent-workflows --skill ex-save-progress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ex-save-progress
Source: https://github.com/ricky-yosh/agent-workflows/tree/main/skills/example/ex-save-progress
Command: npx skills add https://github.com/ricky-yosh/agent-workflows --skill ex-save-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save progress by marking a task as done and updating progress trackers, reducing manual bookkeeping in multi-step workflows.

Core Features & Use Cases

  • Mark current task as complete and write progress.json with a timestamp and task ID.
  • Update tasks.json to reflect the completed task, enabling multi-output completion detection.
  • Use in YAML-driven workflows to automatically advance phases after a step finishes.

Quick Start

Say 'Progress saved' to mark the current task as done and update the progress files.

Frequently Asked Questions about ex-save-progress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically save task progress in a multi-step YAML workflow?

To save task progress, this Skill marks the current task as done and writes a timestamp and task ID to progress.json. It also updates tasks.json to reflect completion, enabling multi-step YAML workflows to automatically advance phases.

What is the best way to track task status across project phases using JSON files?

Tracking task status across phases is handled by updating progress.json and tasks.json when a step completes. This approach persists task IDs and timestamps locally, providing a reliable record of workflow advancement without external network calls.

Does workflow-automation progress tracking require external network calls or API connections?

No, workflow-automation progress tracking does not require external network calls. This Skill operates entirely within the project workspace, persisting completion details by modifying only local JSON files like progress.json and tasks.json.

Can I use this task-tracking method to detect multi-output completion in devops pipelines?

Yes, you can use this task-tracking method for multi-output completion detection in devops pipelines. By updating tasks.json when a step finishes, it enables systems to verify that all required outputs across different workflow phases are complete.

Are there limitations on where progress.json files can be saved during task-tracking workflows?

Yes, there are limitations on where progress.json files are saved during task-tracking workflows. The Skill strictly operates within the project workspace and will not modify files or directories outside of the defined project boundary.