workflow-state-manager

Maintain event-sourced execution state with deterministic pause, resume, and checkpoint transitions.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill workflow-state-manager-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-state-manager
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/workflow-state-manager
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill workflow-state-manager-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running automated workflows lose track of where they are when interrupted, and ad-hoc state tracking leads to inconsistent or unrecoverable execution. This Skill keeps an authoritative, event-sourced record of workflow execution so state can be paused, resumed, checkpointed, and audited deterministically. ## Core Features & Use Cases - Event-Sourced State Management: Appends immutable execution events to an append-only log and derives materialized state snapshots that are reproducible from event history. - Deterministic Transitions: Validates every proposed state change against allowed state machine rules, rejecting invalid transitions with deterministic rule identifiers. - Pause, Resume, and Approval-Wait: Emits checkpoints at deterministic boundaries and holds workflows in approval-wait until explicit approval gates are satisfied. - Use Case: A multi-step deployment workflow is interrupted mid-run. Replay the event log from the last checkpoint to restore exact execution state, then resume from the approval-wait step without re-executing completed work. ## Quick Start Ask the agent to load the current execution state and advance the workflow to the next valid step, writing the updated snapshot to reports/current-execution-state.json.

Frequently Asked Questions about workflow-state-manager

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

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

Replay the append-only event log from the last emitted checkpoint to rebuild the materialized state snapshot, then continue applying valid transitions. Because state is derived from immutable events, the restored state is deterministic and reproducible.

What is event-sourced workflow state management?

Event sourcing stores every state change as an immutable, ordered event rather than overwriting current state. The current execution state is derived by replaying events, which guarantees an auditable history and reproducible snapshots.

How are invalid workflow state transitions handled?

Each proposed transition is validated against allowed state machine rules before being applied. Invalid transitions are rejected with deterministic rule identifiers, and the workflow never advances on partial or ambiguous evidence.

When does a workflow reach a terminal state?

Terminal states are reconciled only when all required step outcomes are final and reached through valid completion paths. Forced terminal transitions or manual state overrides require explicit approval before being applied.

What happens if the event log integrity cannot be verified?

The skill fails closed: it preserves the last valid snapshot, emits blocked transition diagnostics, and refuses to advance workflow state until event history integrity is restored.