agentleFS
Sign inStart free
minosinminosin/gtdbrain-claude-plugin/skills/waiting-for/SKILL.md

waiting-for

Skill0 starsChanged 38 days agoMITView on GitHub

Track what the user is waiting on from other people (their GTD Brain Waiting For list). Use when they say "I'm waiting on Sam for…", "I asked Alex to…", "follow up with…", "chase…", "who owes me a reply?", or before a weekend or deadline.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. alz-ahm/gtdbrain-claude-plugin★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    If no GTD Brain tool is available, follow /gtdbrain:setup instead of guessing.

    line 7
  2. Very specific:

    If the user names something new they are waiting on, get the Waiting For column id from list_columns and create_card it there with who and …

    line 9
  3. Very specific:

    Call list_waiting_for. For each card say who the user is waiting on and since when, and flag the ones that look stale (older than two …

    line 13
  4. Very specific:

    If something has already arrived, move_card it to where it belongs or archive_card it.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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

Chase the user's Waiting For list. If no GTD Brain tool is available, follow /gtdbrain:setup instead of guessing.

If the user names something new they are waiting on, get the Waiting For column id from list_columns and create_card it there with who and since (today if not said), confirm in one line, and stop there unless they also want the whole list reviewed.

  1. Call list_waiting_for. For each card say who the user is waiting on and since when, and flag the ones that look stale (older than two weeks, or with no since date).
  2. For each stale one ask whether to chase it. If yes, get the Next Actions column id from list_columns and create_card a verb-first follow-up action there (for example "Email Sam about the electrician quote") with a context such as calls or computer, leaving the Waiting For card in place until they answer.
  3. If something has already arrived, move_card it to where it belongs or archive_card it.
  4. Close with the count of items still open and the next follow-up date to check back.

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