How do I install the Progress Updating skill?

Run npx skillmds@latest add aman-bhandari/progress-updating in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Progress Updating safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Progress Updating?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Progress Updating free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Progress Updating?

aman-bhandari (@aman-bhandari) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Progress Updating by aman-bhandari — Agent Skill

Name: Progress Updating
Author: aman-bhandari

Progress Updating

Updates PROGRESS.md with session entry and captures exactly where we stopped. Triggers on /progress, update progress, or at end of session before commit. Tracks what was done, what was learned, where we are in the flow, and what comes next. The repo never lies.

aman-bhandari Updated Sep 17, 2026

File contents

Progress Update -- Session Log

The repo never lies. This keeps the record honest, current, and useful for the next session start.

Trigger

/progress or "update progress"
At end of session, before commit

Execution

Read last entry in PROGRESS.md (get current session number and state).
Gather from session context (or ask the student if unclear):
- What did we do this session? (specific activities: theory, build, review, brainstorm)
- What's the key thing learned? (one sentence, specific)
- Where exactly are we stopping? (mid-prep? exercise done? review pending?)
- Approximately how long was this session? (even rough: 15m, 1h, 3h)
- What concepts go into the spaced review deck?
Append new row to PROGRESS.md table:
```
| {session} | {date} | {time} | {topic} | {key learning} | {state} |
```
Time format: ~15m, ~1h, ~3h. Even rough estimates help future students plan.

Session state examples:
- exercise complete, reviewed -- fully done
- theory discussed, exercise not started -- mid-flow
- exercise built, review pending -- will review next session
- brainstorm only -- wiki page created -- knowledge session
Update ROADMAP.md current status if topic or project state changed.
If concepts were learned, prompt to add them to spaced review deck.
Remind: "Run /post for your X post, then commit and push."

What Gets Captured

Every progress entry must tell the next session exactly where to pick up:

What was DONE (so we don't repeat it)
What is IN PROGRESS (so we continue it)
What is NEXT (so we can plan the session)

Rules

Every session ends with a progress update + commit. Non-negotiable.
Key learning must be specific, not vague. "Learned about dicts" → rejected. "Learned that defaultdict avoids KeyError checks in frequency counting" → accepted.
If the student can't articulate a key learning, the session wasn't focused enough. Flag it.
Session state must be precise enough that next session's /checkin can pick up exactly where we left off.
If wiki pages were created during the session, note them in the entry.

---name: progress-updatingdescription: Updates PROGRESS.md with session entry and captures exactly where we stopped. Triggers on /progress, update progress, or at end of session before commit. Tracks what was done, what was learned, where we are in the flow, and what comes next. The repo never lies.---# Progress Update -- Session LogThe repo never lies. This keeps the record honest, current, and useful for the next session start.## Trigger- `/progress` or "update progress"- At end of session, before commit## Execution1. **Read** last entry in PROGRESS.md (get current session number and state).2. **Gather from session context (or ask the student if unclear):** - What did we do this session? (specific activities: theory, build, review, brainstorm) - What's the key thing learned? (one sentence, specific) - Where exactly are we stopping? (mid-prep? exercise done? review pending?) - Approximately how long was this session? (even rough: 15m, 1h, 3h) - What concepts go into the spaced review deck?3. **Append** new row to PROGRESS.md table: ``` | {session} | {date} | {time} | {topic} | {key learning} | {state} | ``` Time format: `~15m`, `~1h`, `~3h`. Even rough estimates help future students plan. Session state examples: - `exercise complete, reviewed` -- fully done - `theory discussed, exercise not started` -- mid-flow - `exercise built, review pending` -- will review next session - `brainstorm only -- wiki page created` -- knowledge session4. **Update ROADMAP.md** current status if topic or project state changed.5. **If concepts were learned**, prompt to add them to spaced review deck.6. **Remind:** "Run `/post` for your X post, then commit and push."## What Gets CapturedEvery progress entry must tell the next session exactly where to pick up:- What was DONE (so we don't repeat it)- What is IN PROGRESS (so we continue it)- What is NEXT (so we can plan the session)## Rules- Every session ends with a progress update + commit. Non-negotiable.- Key learning must be specific, not vague. "Learned about dicts" → rejected. "Learned that defaultdict avoids KeyError checks in frequency counting" → accepted.- If the student can't articulate a key learning, the session wasn't focused enough. Flag it.- Session state must be precise enough that next session's /checkin can pick up exactly where we left off.- If wiki pages were created during the session, note them in the entry.

Frequently asked questions