gf-save-progress

Append session decisions to progress.txt and update tasks.json.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save current session work to .aw/greenfield-progress/progress.txt and updates tasks.json to reflect completed tasks, enabling continuity across sessions.

Core Features & Use Cases

  • Capture decisions, rationale, and next steps from a session into a persistent progress log.
  • Automatically mark completed tasks in tasks.json to keep workflow state synchronized.
  • Supports audit trails for greenfield development by preserving context between sessions.

Quick Start

Invoke the Save Progress skill to append your latest decisions to the progress log.

Frequently Asked Questions about gf-save-progress

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

FAQPage Schema
How do I save session progress and decisions for greenfield development?

To save session progress, the skill appends your decisions and rationale to a persistent log at .aw/greenfield-progress/progress.txt. It then updates tasks.json to mark completed tasks, ensuring your workflow state remains synchronized across development sessions.

How do I automatically update tasks.json to reflect completed workflow tasks?

Automatically updating tasks.json involves reading the existing file and modifying the status of completed tasks. The skill safely commits these changes alongside your progress log to maintain an accurate, auditable record of your current workflow state.

What is the best way to maintain an audit trail of development decisions across sessions?

Maintaining an audit trail requires capturing decisions, rationale, and next steps into a persistent text file. This skill automates that process by reading existing progress and appending new entries before committing the changes safely.

Can I use this progress logging skill for non-greenfield development workflows?

This progress logging skill is specifically intended for greenfield development workflows where capturing context is critical. Using it for non-greenfield projects may not align with its targeted approach of appending decisions to the .aw/greenfield-progress/ directory.

How does saving session progress handle existing entries in progress.txt?

Saving session progress reads the existing progress.txt file before appending a new entry. This ensures your historical decisions and rationale are preserved while the new session data is safely committed alongside the updated tasks.json file.

Do I need any dependencies to automate saving progress and committing tasks.json?

You do not need any external dependencies to automate saving progress and committing tasks.json. The skill operates independently to read your workflow state, append session decisions, and safely commit the changes.