skills.rest
djimit
djimitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

resume

Resume projects by loading plan.md and updating swarm context.

1|Updated May 17, 2026
Search Tags:#project resumption#project continuation#execution management#swarm management#context adjustment
One-click install
npx skills add https://github.com/djimit/djimitflo --skill resume-djimit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resume
Source: https://github.com/djimit/djimitflo/tree/main/.opencode/skills/resume
Command: npx skills add https://github.com/djimit/djimitflo --skill resume-djimit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows for the seamless continuation of existing projects, ensuring that progress is not lost and work can be resumed safely from the current state.

Core Features & Use Cases

  • Project Continuation: Resume approved plans from the last known state.
  • Swarm Identification: Handles projects across different execution environments by updating and matching swarm IDs.
  • Stale Context Purging: Removes outdated context from previous swarms to maintain current project integrity.
  • Quick Restart: Provides immediate project continuation with user notification.

Quick Start

To resume the project from the current state, run the resume skill.

Frequently Asked Questions about resume

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

FAQPage Schema
How do I resume a project from its current state without losing execution progress?▼

This skill manages project continuation by loading execution details from plan.md and adjusting context based on the active swarm ID. It ensures progress is not lost and work resumes safely from the last known state.

How does swarm management handle project continuation across different execution environments?▼

Swarm management handles different execution environments by updating and matching the active swarm ID. This mechanism ensures the correct execution context is loaded regardless of where the project is running.

What is the best way to purge stale context when resuming an execution plan?▼

The best way to purge stale context is to use the project continuation skill, which removes outdated context from previous swarms. This maintains current project integrity by ensuring only relevant execution details are loaded.

Do I need a plan.md file to restart my project from the last known state?▼

Yes, you need a plan.md file within your project directory because the skill reads execution details from it to resume the project. It also requires modifying files in the project directory to adjust the current context.

What happens to outdated context from previous swarms during project resumption?▼

During project resumption, outdated context from previous swarms is purged to maintain current project integrity. The skill identifies the active swarm ID and removes stale data before providing a user notification.

Related Skills

Explore More Software Engineering Skills→
X-School-AcademyX-School-Academy
19

vibe-coding-project-implement

Translate a plan.md file into executable code within a defined project boundary.

Official
Intermediate
levnikolaevichlevnikolaevich
534

ln-410-story-executor

Orchestrate end-to-end Story execution with task delegation and quality gates.

Community
Advanced
refernandesrefernandes

resume

Resume approved plans and update swarm references from current state.

Community
Advanced
ZaxbyHubZaxbyHub
437

resume

Resume interrupted OpenCode Swarm sessions from an approved plan.md.

Official
Advanced