forge-resume

Reconstructs session context from GitHub issues, specs, plans, and branch status when resuming work.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When resuming work on a GitHub issue in a new session or handing off work between bots, context is lost. This Skill rebuilds the full working state from persistent GitHub artifacts so you can continue without re-reading everything manually. ## Core Features & Use Cases - Artifact Reconstruction: Reads the issue body, linked spec file, posted assessment, and implementation plan from GitHub comments. - Branch and PR Status Check: Detects existing branches, commits ahead of main, open PRs, and review comments. - Next-Action Suggestion: Applies decision logic to recommend the next step, such as running an assessment, writing a plan, continuing implementation, or merging a PR. - Use Case: A bot picks up issue #401 started by another bot. The Skill reads the spec, assessment, and plan from GitHub, checks the branch and PR state, and reports that reviews are pending so the bot knows to address review comments. ## Quick Start Ask the assistant to resume work on issue 401 using the forge-resume skill to see the current state and suggested next action.

Frequently Asked Questions about forge-resume

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

FAQPage Schema
How do I resume work on a GitHub issue in a new session?

Invoke the skill with the issue number, for example /forge-resume 401. It reads the issue, linked spec, assessment, plan, branch, and PR status from GitHub, then presents a summary and suggests the next action.

How to hand off work between bots on GitHub issues?

Post the assessment and plan as issue comments using the forge hooks, then have the receiving bot run the resume skill. Since all artifacts live on GitHub rather than the local filesystem, any bot container can reconstruct full context.

Does forge-resume require local files to reconstruct context?

No, all artifacts are read from GitHub, which serves as the shared store across isolated bot containers. The only local operations are git fetch and branch inspection against the remote.

What happens if no assessment or plan exists for an issue?

The skill notes that the artifact is not posted yet and adjusts its suggestion. For example, if a branch exists but no assessment, it recommends running /forge-assess before proceeding.

Which model should run the forge-resume skill?

The skill is designed to run on Sonnet because it only reads artifacts and classifies state without creative judgment. When spawning as a subagent, pass model="sonnet" with the resume prompt.