agentleFS
veraetogrex-portfolioveraetogrex-portfolio/solo-sdd/skills/work-status/SKILL.md

work-status

Skill0 starsChanged yesterdayMITView on GitHub

Use when the user asks where the work stands or whether anything is still running - "status?", "what is the status", "are you there?", "what are we waiting for", "are you done?", "what is active now", "is the process running or stuck", "is it frozen?" - and before context compaction or a handoff to another session - "describe where we stopped", "I will press compact".

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before answering check the facts, not memory: the list of background processes and tasks, git status, tasks.md of the current change.

    line 10

“Common” is measured: kept by at least 6 in 10 of the 4 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

work-status: five lines about the state

The answer is exactly the five lines below, in the user's language, without an introduction. It must show whether one can step away from the screen.

Before answering check the facts, not memory: the list of background processes and tasks, git status, tasks.md of the current change.

"Done" counts light: commits apart from changes: light: <n> commits from git log --oneline --grep='^light:' --since=<the session's first message time>, and names the archived changes by id.

Done: <what is finished and checked>
Running now: <process, how long so far and how much more, by what sign it ends> | nothing running
Left: <items until "done">
Blocking: <what we wait for, who can lift it, what cannot be checked yet, when to come back> | nothing
Needs from you: <a specific action> | nothing

Conditions

  • A process is stuck or dead: write it in "Running now", restart it and say that you restarted it.
  • "Running now: nothing" while "Left" is not empty: right after the answer continue the work, do not wait for a command.
  • The user mentioned a compaction, a move to another chat or another agent: write the same five lines and the list of decisions made into handoff.md in the current change's folder (no change: the project root) and name the path.

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.