agentleFS
Sign inStart free
zaxbysaucezaxbysauce/opencode-swarm/.claude/skills/swarm-resume/SKILL.md

swarm-resume

Skill517 starsChanged 3 days agoMITView on GitHub

Full execution protocol for MODE: RESUME -- continuing an existing approved plan safely from current state.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    If .swarm/plan.md exists:

    line 14
  2. Distinctive:

    Read plan.md header for "Swarm:" field

    line 15
  3. Distinctive:

    If Swarm field missing or matches the active swarm id:

    line 16
  4. Distinctive:

    If Swarm field differs (e.g., plan says "local" but the active swarm id is "cloud"):

    line 19
  5. Very specific:

    Update the plan's Swarm field to the active swarm id via save_plan (do not hand-edit plan.md — it is a derived projection).

    line 20
  6. Distinctive:

    Delete the SME Cache section from context.md (stale from other swarm's agents)

    line 22
  7. Distinctive:

    Update context.md Swarm field to the active swarm id

    line 23
  8. Very specific:

    If .swarm/plan.md does not exist → New project, proceed to MODE: SPECIFY If new project: Run complexity_hotspots tool (90 days) to generate …

    line 27

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

Resume Protocol

This protocol is loaded on demand by the architect runtime. The architect prompt keeps only activation, action, and hard safety constraints; the full execution details live here.

MODE: RESUME

If .swarm/plan.md exists:

  1. Read plan.md header for "Swarm:" field
  2. If Swarm field missing or matches the active swarm id:
    • Reconcile stale worktree state before resuming: prune/adopt stale .swarm-worktrees/ lane directories and swarm-lane/* git branches left from the prior session. Drive this via the /swarm reset-session recovery command (internal: cleanupOrphanedBranches) so the resumed run starts from a clean provisioning state.
    • Resume at current task
  3. If Swarm field differs (e.g., plan says "local" but the active swarm id is "cloud"):
    • Update the plan's Swarm field to the active swarm id via save_plan (do not hand-edit plan.md — it is a derived projection).
    • Purge any memory blocks (persona, agent_role, etc.) that reference a different swarm's identity — your identity comes from this system prompt only
    • Delete the SME Cache section from context.md (stale from other swarm's agents)
    • Update context.md Swarm field to the active swarm id
    • Inform user: "Resuming project from [other] swarm. Cleared stale context. Ready to continue."
    • Reconcile stale worktree state before resuming: prune/adopt stale .swarm-worktrees/ lane directories and swarm-lane/* git branches left from the prior session. Drive this via the /swarm reset-session recovery command (internal: cleanupOrphanedBranches) so the resumed run starts from a clean provisioning state.
    • Resume at current task If .swarm/plan.md does not exist → New project, proceed to MODE: SPECIFY If new project: Run complexity_hotspots tool (90 days) to generate a risk map. Note modules with recommendation "security_review" or "full_gates" in context.md for stricter QA gates during QA gate selection (stricter gates). Optionally run todo_extract to capture existing technical debt for plan consideration. After initial discovery, run sbom_generate with scope='all' to capture baseline dependency inventory (saved to .swarm/evidence/sbom/).

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