agentleFS
Sign inStart free
caidanwcaidanw/skills/skills/progress/SKILL.md

progress

Skill11 starsChanged 27 days agoMITView on GitHub

Report progress against the current plan in plain English: on track or not, done, running, blocked, needs you, next. Use for /progress.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quiz and review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • andrewn6Skill

    quiz

    Test understanding with targeted questions — adapts to skill level and researches the stack for relevant questions

    Also in 4 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check live state before you write anything: running jobs, each subagent (working, stuck, or waiting on you), PRs and CI, and the newest …

    line 12
  2. Distinctive:

    Done when: every line is checked against live state, not memory.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Progress

Report where the work stands against its plan, then keep working.

  1. Find the plan: the day-plan file, a plan file, the todos, or the ticket. Without one, measure against the goal the user stated.
  2. Check live state before you write anything: running jobs, each subagent (working, stuck, or waiting on you), PRs and CI, and the newest results files. Answer any subagent that is waiting on you first.
  3. Reply in plain English, under 150 words:
    • One line: on track or not, and why.
    • Done since the last report.
    • Running now, each with an honest ETA or "unknown".
    • Blocked, and what unblocks it.
    • What needs the user, each item with your recommendation.
    • The next step you will take.
  4. Continue the work unless the user told you to stop.

Done when: every line is checked against live state, not memory.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free