sparq:resume

Resume interrupted SparQ QA workflows from the exact interruption point.

27|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-resume
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparq:resume
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-resume
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resumes interrupted SparQ QA workflows from the exact interruption point to preserve progress and context.

Core Features & Use Cases

  • Recovery across mid-phase, mid-dispatch, and mid-merge scenarios using machine-readable state sources (.sparq/state) and legacy traces.
  • Deterministic re-dispatch and state reconstruction to continue work without starting over, with validation of artifacts and configuration.
  • Guided recovery wizard that surfaces plain-language options for continuing, starting fresh, or reviewing results.

Quick Start

Invoke the resume skill to pick up where the previous run left off.

Frequently Asked Questions about sparq:resume

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

FAQPage Schema
How do I resume an interrupted QA workflow from the exact point it stopped?

To resume an interrupted QA workflow, the skill reads machine-readable state files and journals to validate freshness, derive recovery actions, and re-dispatch the orchestrator exactly where the previous run paused.

Can workflow recovery handle mid-parallel-dispatch and mid-merge scenarios?

Yes, workflow recovery handles mid-phase, mid-parallel-dispatch, and mid-merge scenarios by reconstructing state from legacy traces and state files to continue execution without restarting completed phases.

What is QA orchestration state management for resuming paused tests?

QA orchestration state management preserves progress and context across interruption points using state files and journals, enabling deterministic re-dispatch of the orchestrator while validating existing configuration and artifacts.

Does workflow recovery preserve completed phases when re-dispatching the orchestrator?

Yes, workflow recovery preserves completed phases and configuration during state reconstruction, validating artifact freshness before continuing the paused execution from the exact interruption point.

What are the limitations of resuming a workflow from legacy state traces?

Resuming from legacy state traces requires validating artifact freshness and configuration consistency; if state files are corrupted or stale, the guided recovery wizard recommends starting fresh instead of continuing.

What's the best way to recover state after a SparQ workflow interruption?

The best way to recover state is invoking the resume skill, which analyzes state files and journals to surface plain-language options for continuing, starting fresh, or reviewing results from the interruption point.