agentleFS
AlomoesDataScienceAlomoesDataScience/claude-skills/.claude/skills/waiting-checklist/SKILL.md

waiting-checklist

Skill1 starsChanged 13 days agoNo licenceView on GitHub

Make a checklist document for work that is PARKED until something happens - the game or app is free, the user gives the go, a file or answer arrives, a machine is available - so it can start cold later without re-deriving anything. checklist.py writes it into the work's folder (<folder>/checklists/<slug>.md) from a fixed template (Status / Waits on / Go from header, a gate of conditions that must all be true, the session's safety rules, numbered items each with steps, "done when" and where results go, an After section and a dated log), lists every waiting checklist in the workspace, and sets status (waiting, ready, in-progress, done). Use when the user says he'll wait for something or do it later, when a plan's remaining items need a game, screen, file or go that isn't available now, when phase 2 of a job is blocked, and at session start (checklist.py list) to see what may now be unblocked.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.