bf-save-progress

Append session progress and decisions to .aw/brownfield-progress/progress.txt.

Updated Apr 4, 2026

Search Tags:#git #workflow #decisions #save #session #brownfield #progress

Ready to run

npx skills add https://github.com/ricky-yosh/agent-workflows --skill bf-save-progress

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bf-save-progress
Source: https://github.com/ricky-yosh/agent-workflows/tree/main/skills/brownfield/bf-save-progress
Command: npx skills add https://github.com/ricky-yosh/agent-workflows --skill bf-save-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brownfield work often lacks a complete trail of decisions and session context; this skill saves the current session's progress and the rationale behind actions to a centralized progress file for later review.

Core Features & Use Cases

Save session progress to .aw/brownfield-progress/progress.txt, including the decisions behind actions.
Read existing progress and tasks to append new entries without overwriting history.
Prompt for confirmation and mark tasks as done to keep task tracking synchronized.

Quick Start

Run bf-save-progress after finishing a session to append your latest progress and decisions to the progress file.

Frequently Asked Questions about bf-save-progress

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

FAQPage Schema

How do I save brownfield session progress and decisions to a file?▼

To save brownfield session progress, run the command to append your latest work entries and decisions to a centralized progress file. It reads existing tasks to identify completed items and appends new records without overwriting previous history.

What is the best way to track decisions made during a brownfield workflow?▼

Tracking decisions in a brownfield workflow involves documenting the session context and rationale behind actions into a centralized text file. This ensures the reasoning behind work on tickets is preserved for later review instead of being lost.

Does saving session progress overwrite existing data in the progress file?▼

Saving session progress does not overwrite existing data. The process appends new entries to the centralized progress file, preserving the complete historical trail of decisions and tasks from previous sessions.

How do I keep task tracking synchronized when wrapping up work on tickets?▼

To keep task tracking synchronized when wrapping up ticket work, the process reads a tasks file to identify completed items and prompts for confirmation. It then marks identified tasks as done while appending the session summary to the progress file.

Can I document git workflow decisions without losing previous session context?▼

You can document git workflow decisions without losing context by appending them to a centralized progress file. The system reads existing progress data and adds new entries sequentially, ensuring the complete decision trail remains intact.

When do I need to save brownfield progress to a centralized file?▼

You need to save brownfield progress to a centralized file when documenting decisions, tracking tasks, or wrapping up work on tickets. This captures the session context and rationale that brownfield workflows often lack for future reference.