save

Update PROGRESS.md, route learnings to docs, and record TECH_DEBT.md entries.

25|4|Updated Sep 5, 2010
One-click install
npx skills add https://github.com/divad12/dotfiles --skill save-divad12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save
Source: https://github.com/divad12/dotfiles/tree/main/.claude/skills/save
Command: npx skills add https://github.com/divad12/dotfiles --skill save-divad12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a living log of work across agents and sessions by updating a central coordination board (PROGRESS.md), routing learnings to the right documentation, and tracking TECH_DEBT.md.

Core Features & Use Cases

  • Updates PROGRESS.md with current state, last updated, in-progress, up-next, recently done, and blockers.
  • Routes learnings to the appropriate project docs and milestones for rapid knowledge capture.
  • Records and surfaces debt items in TECH_DEBT.md to guide future improvements.
  • Example: during a session, you add a new worktree to In Progress and later move it to Recently Done with the appropriate evidence.

Quick Start

Run the save workflow to capture current session progress, update PROGRESS.md, route learnings to docs, and log TECH_DEBT.md updates.

Frequently Asked Questions about save

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

FAQPage Schema
How do I track AI session progress across multiple agents and worktrees?

Save session progress by updating PROGRESS.md with current state, in-progress items, up-next tasks, recently done work, and blockers, keeping the file under 30 lines for clear cross-agent coordination.

What is the best way to log tech debt discovered during an AI coding session?

Log tech debt by recording items in a TECH_DEBT.md file to guide future improvements and surface outstanding issues for ongoing AI sessions. This separates debt tracking from active progress monitoring.

How do I route learnings to project docs without disrupting the coding workflow?

Route learnings to project docs by running a save workflow that captures session knowledge and directs it to the appropriate documentation and milestones for rapid knowledge capture. This happens alongside standard progress updates.

Does the PROGRESS.md coordination board enforce any specific file structure?

PROGRESS.md enforces a standardized structure with sections for Last Updated, Current State, In Progress, Up Next, Recently Done, and Blockers, capping Recently Done entries and keeping the file under 30 lines for readability.

Can I use this progress tracking approach for ongoing sessions across different worktrees?

Progress tracking applies to ongoing AI sessions across agents and worktrees by maintaining a living log in PROGRESS.md that coordinates work and captures knowledge. It updates the central board to reflect the latest session state.

When should I record entries in TECH_DEBT.md instead of PROGRESS.md?

Record entries in TECH_DEBT.md when surfacing debt items to guide future improvements, while using PROGRESS.md for active session state, in-progress work, and blockers. This separates immediate coordination from long-term debt tracking.