workflow-state

Persist multi-item workflow state across sessions in sdd files.

39|3|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/LiorCohen/sdd --skill workflow-state-liorcohen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-state
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/core/skills/workflow-state
Command: npx skills add https://github.com/LiorCohen/sdd --skill workflow-state-liorcohen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps track of long-running workflows across sessions by persisting state in sdd files rather than relying on memory, enabling safe context compaction and session resets.

Core Features & Use Cases

  • Zero-session workflow state persistence across drafts, changes, and archives.
  • Per-item four-field status tracking (spec, plan, impl, review) with phase gating.
  • Checkpointing and versioned history to support recovery and regression.
  • Support for moving items from drafts to changes and archiving regressions.

Quick Start

Create a new workflow and query its current state to verify progress.

Frequently Asked Questions about workflow-state

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

FAQPage Schema
How do I persist workflow state across sessions without relying on in-memory context?

Workflow state persistence across sessions is achieved by storing lifecycle data in sdd files, enabling safe context compaction and session resets without losing progress. This zero-state approach tracks drafts, changes, and archives.

What is phase gating and how does it work for multi-item workflow tracking?

Phase gating enforces sequential progression through spec, plan, impl, and review phases. Per-item four-field status tracking ensures each workflow item meets phase requirements before advancing, preventing skipped steps in solicitation and implementation workflows.

Can I recover workflow progress after a session reset using checkpointing?

Checkpointing with versioned history supports recovery and regression after session resets. Checkpoints capture workflow state at specific intervals, allowing you to restore progress and review previous versions of drafts and changes.

How do I move items from drafts to changes and archive regressions in a workflow lifecycle?

Moving items from drafts to changes and archiving regressions is supported through workflow lifecycle management. The system handles state transitions between solicitation, review, approval, and implementation phases within sdd/workflows.

Does zero-session state management work for long-running workflows with multiple items?

Zero-session state management handles long-running workflows with multiple items by persisting state in sdd files. Each item maintains independent four-field status tracking, supporting concurrent workflow items across extended sessions.

What are the limitations of file-based workflow state persistence compared to in-memory tracking?

File-based workflow state persistence requires sdd file access for state queries and updates. Unlike in-memory tracking, every state check reads from persisted files, which may impact performance for high-frequency status queries during active implementation phases.