agentleFS
wamalalawrencewamalalawrence/agent-skills/skills/delivery-runner/SKILL.md

delivery-runner

Skill0 starsChanged 51 days agoLicence not identifiedView on GitHub

Autonomous phase-by-phase executor for a delivery-planner phased plan. Walks the plan to completion without manual handoff: it reads the plan index's current_dispatch_pointer, dispatches the next phase to a brand-new empty-context agent (exactly like a human opening a fresh chat per phase), waits for that agent to finish, verifies the result from the persisted plan artifacts (never from chat), then advances to the next phase and repeats until the plan is done, blocked, or needs a human decision. Use when a delivery-planner plan has two or more ready phases and the user wants them run end-to-end without babysitting each handoff. It dispatches fresh agents; it does NOT implement phases itself and does NOT load executor skills into its own context, so the depth-cap-of-two review bound stays intact inside each phase.

The file

Show its rules and text

We split this skill into the rules it gives an agent

33 rules. About 0 are common, 11 are distinctive, and 22 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 22

    Very specific

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

The licence could not be identified — 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 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.

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.