skills.rest
porcupine-md
porcupine-mdOFFICIAL
Explore all skills by this author →
GitHub

persisting-progress-across-sessions

Resume interrupted orchestration runs from MANIFEST.yaml without re-running completed phases.

11|2|Updated Apr 7, 2026
Search Tags:#workflow#orchestration#resume#manifest#sessions#context-recovery#phase-outputs
One-click install
npx skills add https://github.com/porcupine-md/jonggrang --skill persisting-progress-across-sessions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: persisting-progress-across-sessions
Source: https://github.com/porcupine-md/jonggrang/tree/main/skills/core/persisting-progress-across-sessions
Command: npx skills add https://github.com/porcupine-md/jonggrang --skill persisting-progress-across-sessions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps resume an orchestration run that was interrupted due to context compaction, manual restart, or a crash by reusing previously produced phase outputs and the MANIFEST.yaml to avoid redoing completed work.

Core Features & Use Cases

  • Detect incomplete MANIFEST.yaml entries and identify the next actionable phase.
  • Reconstruct context from phase outputs without re-running completed phases.
  • Identify the correct resumption point and continue the orchestration with preserved state.

Quick Start

Run the resume flow by providing the feature_id and invoking orchestrating-feature with resume set to true.

Frequently Asked Questions about persisting-progress-across-sessions

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

FAQPage Schema
How do I resume an interrupted orchestration run without redoing completed work?▼

You can resume an interrupted orchestration by detecting incomplete MANIFEST.yaml entries and reconstructing context from previously produced phase outputs, which prevents re-running completed work and ensures safe state recovery.

What is context recovery for mid-flight workflow sessions?▼

Context recovery for mid-flight sessions is the process of reconstructing execution state from per-phase artifacts and a MANIFEST.yaml file, enabling safe resumption of orchestration runs that were interrupted by context compaction, manual restarts, or crashes.

How do I find the correct resumption point in a multi-phase workflow?▼

Find the correct resumption point by detecting incomplete MANIFEST.yaml entries to identify the next actionable phase. The skill reconstructs context from existing phase outputs to continue the orchestration with preserved state.

Does this approach to session recovery work with orchestration backends outside of Claude Code?▼

Yes, the context recovery approach applies to mid-flight executions across Claude Code sessions and other backends that store per-phase artifacts, as long as a MANIFEST.yaml and phase outputs are available to reconstruct state.

What guardrails exist against phase duplication when restoring workflow state?▼

Guardrails against duplication are built into the state recovery process by reusing previously produced phase outputs and the MANIFEST.yaml, ensuring non-destructive continuation that skips completed work and safely resumes from the next actionable phase.

Related Skills

Explore More Software Engineering Skills→
MINT-IAMINT-IA

gsd-validate-phase

Audit Nyquist validation coverage and generate missing validation artifacts.

Official
Advanced
skaisserskaisser
4

resume

Resume interrupted plans by detecting completed phases and continuing from the last checkpoint.

Community
Advanced
suriyelsuriyel
178

using-long-task

Orchestrates multi-session software development workflows by routing to phase-specific skills.

Community
Advanced
aslaiiaslaii

gsd-resume-work

Restore project state and route to the next command from checkpoints.

Community
Advanced