agentleFS
enaptenapt/SwarmLLM/.claude/skills/next-task/SKILL.md

next-task

Skill82 starsChanged 28 days agoApache-2.0View on GitHub

Pick the top item of SwarmLLM's live work queue whose preconditions are met, and start it

10 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 9 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:

    Read the queue: ~/.claude/projects/-home-user-SwarmLLM/memory/next_up.md § "START HERE", and docs/FUTURE_WORK.md § "▶ PRIORITIES".

    line 10

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

Next Task

  1. Read the queue: ~/.claude/projects/-home-user-SwarmLLM/memory/next_up.md § "START HERE", and docs/FUTURE_WORK.md § "▶ PRIORITIES". Take the highest item whose preconditions are met; read its FUTURE_WORK entry BODY — its scope is a hypothesis (gotcha #654) and its line numbers drift (#645).
  2. Research it before touching code (.claude/rules/workflow.md § "Research EVERY task"): how a system with more scars does it, the pinned crate's current API, and what gotchas.md / docs/invariants/ already know.
  3. Say in two lines what you will change and how you will know it worked (the mechanism, not just the outcome).
  4. Implement it yourself (never delegate production code). Use Explore (model: sonnet) for wide searches, digest (Haiku) for any bulky log/output/diff, and a sonnet feature-dev:code-architect only for a design spanning 3+ interconnected files (CLAUDE.md § Subagents).
  5. Finish with cargo fmt && cargo lint and the narrowest cargo dev-test that covers the change, then commit and push (.claude/rules/workflow.md), and update next_up.md.

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.