← ClaudeAtlas

agent-progress-loglisted

Keep an append-only progress log in a repo that more than one agent or person works in. Use at the start of a session to find out where the work stands, and at the end of every session (also a failed one) to record what was done, what comes next and what is blocked. Each session adds one small file; PROGRESS.md is generated from them, so parallel sessions never conflict.
DevCrazyCube/claude-skill-agent-progress-log · ★ 0 · AI & Automation · score 72
Install: claude install-skill DevCrazyCube/claude-skill-agent-progress-log
# Agent progress log A repo that several sessions work in needs one place that says where the work stands. A hand-edited status file does not survive that: two sessions edit the same lines, and the later one silently wins. Here every session writes **one new file**, and a script builds `PROGRESS.md` from all of them. `scripts/progress.mjs` is in this skill's folder. Copy it into the project once (for example to `scripts/progress.mjs`) so every agent and CI can run it; it has no dependencies (Node 18+). ## At the start of a session Read `PROGRESS.md`. Its "Now" block names the milestone in hand, who touched it last, the next action and what is blocked. Start from "Next action" unless the user asks for something else. If there is no `PROGRESS.md` yet, the project has not been set up: see "Setting up" below. ## At the end of a session 1. Make the fragment (it prints the path of the new file): ```bash node scripts/progress.mjs new --agent claude --milestone M1 --tests green --lint not-applicable ``` Add `--done` only when the milestone's demo was actually run and worked. Give each check the result of running it **in this session**: `green`, `red`, or `not-applicable` when it was not run. Never write `green` from memory. 2. Fill in the three lines in that file: ```markdown **Did:** what changed, with the numbers that prove it (tests passed, rows imported, files touched). **Next:** the single next action, concrete enough for a session that knows n