factory-resume

Resume a paused Spec-to-Code Factory pipeline from its last phase.

10|5|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory-resume
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-resume
Source: https://github.com/SylvainChabaud/spec-to-code-factory/tree/main/.claude/skills/factory-resume
Command: npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill orchestrates resuming a paused Spec-to-Code Factory pipeline from the last known phase or task, loading the current state and guiding the user to continue execution.

Core Features & Use Cases

  • Detects the current pipeline state using factory-state.js and determines the correct resume point.
  • Reinvokes the appropriate phase skill (factory-intake, factory-spec, factory-plan, factory-build, or factory-qa) to continue execution from where it stopped.
  • Provides a concise recovery report and next steps to ensure safe and traceable resumption.
  • Supports resuming after idle, completed, or failed runs, and gracefully prompts for manual interventions when needed.

Quick Start

Run /factory-resume to automatically analyze the current state and resume execution from the appropriate phase.

Frequently Asked Questions about factory-resume

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

FAQPage Schema
How do I resume a paused pipeline after an interruption?

To resume a paused pipeline, the system reads the current state from factory-state.js, determines the exact resume point, and orchestrates reentry by invoking the corresponding phase Skill to continue execution safely.

What is the best way to recover a failed build pipeline orchestration?

Recovering a failed build pipeline involves loading the current state, determining the last known phase, and reinvoking the appropriate phase Skill to provide a concise recovery report and next steps for resumption.

How does pipeline state orchestration determine which phase to reenter?

Pipeline state orchestration determines the reentry phase by reading the status saved in factory-state.js, identifying whether the pipeline stopped during BREAK, MODEL, PLAN, BUILD, or DEBRIEF, and triggering the matching Skill.

Can I restart a pipeline orchestration from a specific task without losing progress?

Restarting pipeline orchestration from a specific task is possible by loading the last known phase from the state file, which allows the system to update the pipeline status and continue execution without losing prior progress.

Do I need to manually configure the resume point for an interrupted workflow?

Manual configuration of the resume point is generally not needed; the system automatically analyzes the interrupted workflow, detects the current state, and gracefully prompts for manual interventions only when required.

Why does my pipeline fail to resume after an idle run?

A pipeline may fail to resume after an idle run if the state file is corrupted or missing; the system relies on reading the current state to determine the resume point and orchestrate reentry into the correct phase.