forge-resume

Load the last saved state and resume interrupted workflows with user confirmation.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/whatwecando/tombola --skill forge-resume
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-resume
Source: https://github.com/whatwecando/tombola/tree/main/.claude/skills/forge-resume
Command: npx skills add https://github.com/whatwecando/tombola --skill forge-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resume execution from the last saved state to continue interrupted workflows.

Core Features & Use Cases

  • Detects the last saved state from the planning directory and loads it.
  • Identifies in-progress tasks in the current wave and resumes them deterministically.
  • Displays a status summary and delegates execution to /forge-execute with a single confirmation step.

Quick Start

Instruct the system to load the last saved state and resume from the current wave.

Frequently Asked Questions about forge-resume

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

FAQPage Schema
How do I resume an interrupted workflow from a saved state?

To resume an interrupted workflow, the system detects and loads the last saved state from the planning directory, identifies in-progress tasks, and resumes execution deterministically after user confirmation.

What is deterministic workflow resumption for paused tasks?

Deterministic workflow resumption reloads existing planning data from the .planning directory, identifies current in-progress wave items, and delegates execution to continue processing without losing context.

How do I reload planning data to continue execution?

You reload planning data by instructing the system to load the last saved state from the .planning directory, which displays a status summary and triggers execution with a single confirmation step.

When do I need to resume execution from a saved state?

You need to resume execution from a saved state when tasks were started and paused, requiring you to reload planning data and identify in-progress items to continue the workflow.

Does workflow resumption require manual selection of in-progress tasks?

No, workflow resumption automatically identifies in-progress tasks in the current wave from the loaded state, requiring only a single user confirmation before delegating to execution.

Why does resuming an interrupted workflow require a .planning directory?

Resuming an interrupted workflow requires a .planning directory because it stores the saved state and planning data needed to deterministically load and identify in-progress tasks for resumption.