state-management

Name: state-management
Availability: InStock
Author: ai-sand-castles

Persist workflow state to .claude/.test-loop-state.md for cross-session test resumption.

Updated Aug 23, 2026

Search Tags:#workflow #resume #persistence #state-management #orchestrator #cross-language #test-loop

Ready to run

npx skills add https://github.com/ai-sand-castles/local-marketplace --skill state-management-ai-sand-castles

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: state-management
Source: https://github.com/ai-sand-castles/local-marketplace/tree/main/test-automation-plugin/skills/state-management
Command: npx skills add https://github.com/ai-sand-castles/local-marketplace --skill state-management-ai-sand-castles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

State management for automated test workflows ensures that you can reliably save progress and resume operations after interruptions, reducing wasted time and debugging effort.

Core Features & Use Cases

Persistent storage of workflow state to enable cross-session resumption.
Debug visibility and historical context for failed or paused workflows.
Language-agnostic patterns and project-scoped state files to support multi-language teams.

Quick Start

Configure the orchestrator to persist and load the workflow state from the project root under the .claude directory.

Frequently Asked Questions about state-management

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

FAQPage Schema

How do I resume an automated test workflow after an interruption?▼

Persistent workflow state saves progress to a project-scoped `.test-loop-state.md` file, reducing wasted time and debugging effort by allowing interrupted automated tests to resume from their last known position.

How do I persist workflow state for cross-language test automation?▼

You persist workflow state for cross-language test automation by configuring the orchestrator to write state files using language-agnostic patterns to the project root, enabling multi-language teams to load and resume sessions.

Does workflow state persistence work without external dependencies?▼

Yes, workflow state persistence works without external dependencies by writing state directly to a local markdown file within the project's `.claude` directory, requiring only a project root parameter from the orchestrator.

What is the best way to debug failed automated test loops across sessions?▼

The best way to debug failed automated test loops across sessions is to use persistent state storage, which provides historical context and debug visibility for paused or failed workflows within the project root directory.

Where is the workflow state file stored for project-scoped test loops?▼

The workflow state file for project-scoped test loops is stored at `{project_root}/.claude/.test-loop-state.md`, allowing the resume command to load historical context and continue interrupted operations.