forge:resume

Resume a paused FORGE run by runId to restore steering context.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Chulf58/FORGE --skill forge-resume-chulf58
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge:resume
Source: https://github.com/Chulf58/FORGE/tree/main/skills/resume
Command: npx skills add https://github.com/Chulf58/FORGE --skill forge-resume-chulf58

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Re-enter a paused or in-progress FORGE run to restore steering context only, without advancing the pipeline autonomously.

Core Features & Use Cases

  • Restores steering context only — it does not progress the run autonomously.
  • Allows resuming by runId or listing resumable runs, with the next action left to the user or the LLM.
  • Maintains visibility into gate states, statuses, and the feature being resumed so you can decide next steps.

Quick Start

Prompt FORGE to resume a specific run by providing a runId, or leave it blank to list resumable runs.

Frequently Asked Questions about forge:resume

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

FAQPage Schema
How do I resume a paused FORGE run without advancing the pipeline automatically?

To resume a paused FORGE run without advancing the pipeline, provide a runId to restore its steering context. The system leaves the next action to the user or LLM on the next prompt.

How can I list all resumable FORGE runs in my project?

To list resumable FORGE runs, prompt the resume command without a runId. The backend checks terminal status, projectRoot binding, and valid worktree to return available resumable runs.

What happens when I restore steering context for an in-progress FORGE run?

Restoring steering context for an in-progress FORGE run maintains visibility into gate states, statuses, and the resumed feature so you can decide next steps without progressing autonomously.

Do I need the r- prefix when specifying a runId to resume a FORGE pipeline?

You do not need the r- prefix when specifying a runId to resume a FORGE pipeline. The command accepts an optional runId with or without the r- prefix before returning a structured success object.

Why does my FORGE resume command return an error instead of a success object?

A FORGE resume command returns an error if backend checks fail for terminal status, projectRoot binding, or a valid worktree. The system validates these conditions before returning a structured success object.