state-manager

Manage subagent workflow state with atomic writes to .agents/tmp/state.json.

1|1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/kenkenmain/ken-cc-plugins --skill state-manager-kenkenmain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: state-manager
Source: https://github.com/kenkenmain/ken-cc-plugins/tree/main/plugins/subagents/skills/state-manager
Command: npx skills add https://github.com/kenkenmain/ken-cc-plugins --skill state-manager-kenkenmain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a robust, file-based state store to coordinate multi-phase subagent workflows, reducing inconsistency and drift across stages.

Core Features & Use Cases

  • Atomic writes to .agents/tmp/state.json to ensure safe state persistence.
  • Versioned state with a canonical schema and recovery procedures.
  • Gate-driven transitions and task tracking for reliable orchestration in complex pipelines.

Quick Start

Initialize the state store for a new workflow by creating the .agents/tmp directory and writing the initial state.

Frequently Asked Questions about state-manager

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

FAQPage Schema
How do I manage state across multiple subagents in a workflow?

You can manage subagent state using a file-based JSON store to coordinate phases and transitions. This approach tracks workflow state in a local file to ensure consistency across multi-phase AI agent pipelines.

What is the best way to recover subagent workflow state after a failure?

Recovering subagent workflow state relies on an atomic write protocol and versioned state schema. This enables rollback recovery by reading the last consistent state from the file-based JSON store.

How does gate validation work for multi-phase AI agent pipelines?

Gate validation controls phase transitions by enforcing defined criteria before moving to the next stage. The state manager tracks these gates within the JSON schema to orchestrate reliable workflow progression.

Do I need a specific database to track subagent workflow state?

No database is required to track subagent workflow state. The system persists data by writing atomically to a local JSON file, allowing file-based coordination without external database dependencies.

How does gate validation work for multi-phase AI agent pipelines?

Gate validation controls phase transitions by enforcing defined criteria before moving to the next stage. The state manager tracks these gates within the JSON schema to orchestrate reliable workflow progression.

Do I need a specific database to track subagent workflow state?

No database is required to track subagent workflow state. The system persists data by writing atomically to a local JSON file, allowing file-based coordination without external database dependencies.