Resume Protocol
SkillDev toolsFull execution protocol for MODE: RESUME -- continuing an existing approved plan safely from current state.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Resume Protocol skill
What this skill tells your AI
The instructions your AI receives, as published by zaxbyhub/opencode-swarm in .claude/skills/swarm-resume/SKILL.md and read by ahel’s review.
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:
- Read plan.md header for "Swarm:" field
- If Swarm field missing or matches the active swarm id:
- Reconcile stale worktree state before resuming: prune/adopt stale
.swarm-worktrees/lane directories andswarm-lane/*git branches left from the prior session. Drive this via the/swarm reset-sessionrecovery command (internal:cleanupOrphanedBranches) so the resumed run starts from a clean provisioning state. - Resume at current task
- Reconcile stale worktree state before resuming: prune/adopt stale
- 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 andswarm-lane/*git branches left from the prior session. Drive this via the/swarm reset-sessionrecovery 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_hotspotstool (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 runtodo_extractto capture existing technical debt for plan consideration. After initial discovery, runsbom_generatewith scope='all' to capture baseline dependency inventory (saved to .swarm/evidence/sbom/).
- Update the plan's Swarm field to the active swarm id via
Signals
- GitHub stars
- 467
- Forks
- 51
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
swarm-resume- Source
- github.com/zaxbyhub/opencode-swarm