resume

Resume approved plans and update swarm references from current state.

Updated Jun 19, 2026

Search Tags:#memory management #project resumption #swarm management #plan continuity #state alignment

Ready to run

npx skills add https://github.com/refernandes/toktrim --skill resume-refernandes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resume
Source: https://github.com/refernandes/toktrim/tree/main/.opencode/.opencode/skills/resume
Command: npx skills add https://github.com/refernandes/toktrim --skill resume-refernandes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the issue of safely resuming existing approved plans from the current state, ensuring continuity and minimizing the risk of errors.

Core Features & Use Cases

Plan Resumption: Continues an existing plan without disruption, ensuring the workflow aligns with the latest state.
Swarm Identification: Matches and updates the active swarm ID to the one specified in the plan, ensuring consistency across different environments.
Memory Management: Clears stale context and memory blocks that reference different swarm identities, maintaining data integrity.
Use Case: When working on a distributed project, this Skill ensures seamless resumption of the plan after a session or environment change.

Quick Start

Activate the resume skill by running 'resume'.

Frequently Asked Questions about resume

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I resume an approved plan from the current state after a session change?▼

Plan resumption from the current state requires aligning the workflow with the latest environment and swarm ID. This Skill safely continues approved plans by updating swarm references and clearing stale memory blocks to maintain data integrity.

Why does my workflow lose continuity when resuming plans across different environments?▼

Plan continuity drops across environments because stale context and mismatched swarm IDs disrupt state alignment. Updating active swarm references and clearing outdated memory blocks restores consistency and safely resumes the approved workflow.

What is the best way to manage memory blocks when resuming a distributed project?▼

Memory management for distributed project resumption involves clearing stale context that references outdated swarm identities. This ensures state alignment and maintains data integrity before continuing the approved plan from the current state.

Do I need to manually update swarm IDs to maintain state alignment during plan resumption?▼

Manual swarm ID updates are not required for state alignment. The resumption process automatically matches and updates the active swarm ID to the one specified in the approved plan, ensuring consistency across environments.

Can I continue an existing plan without disruption after an environment change?▼

Continuing an existing plan without disruption after an environment change requires state alignment and memory management. This Skill safely resumes the approved plan from the current state by updating swarm references and clearing stale context.

When should I use an automated plan resumption tool for swarm management?▼

Automated plan resumption for swarm management is essential when working on distributed projects after a session or environment change. It ensures seamless workflow continuity by safely aligning the current state with the approved plan.