workflow-state

Update workflow_state.md atomically across ks-conductor phases from INTAKE to CLOSE.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill workflow-state-kscius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-state
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/workflow-state
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill workflow-state-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill maintains a single, durable workflow_state file that tracks the current ks-conductor run across all phases, surviving context compaction and long autonomous runs to enable seamless resume after interruptions.

Core Features & Use Cases

  • Atomic updates: Writes the entire workflow_state.md atomically at phase boundaries to prevent partial writes.
  • Phase-aware tracking: Tracks transitions from INTAKE to SCOUT, PLAN, BUILD, VERIFY, and CLOSE for STANDARD and COMPLEX tasks.
  • Reference templates: Uses the templates in references/workflow-state-template.md as guidance for per-phase updates and structure.

Quick Start

Run a ks-conductor workflow and ensure the workflow_state.md is updated atomically at each phase boundary.

Frequently Asked Questions about workflow-state

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

FAQPage Schema
How do I track workflow state and resume long-running tasks after context loss?

You can track workflow state by maintaining a durable workflow_state.md file that records phase transitions from INTAKE to CLOSE, surviving context compaction to enable seamless resume after interruptions. Atomic writes at phase boundaries prevent partial updates.

What is atomic write phase tracking and how does it work for workflow state files?

Atomic write phase tracking updates the entire workflow_state.md file atomically at phase boundaries to prevent partial writes. It monitors transitions across STANDARD and COMPLEX task phases, referencing templates for structure guidance.

Can I use workflow state checkpointing for both STANDARD and COMPLEX ks-conductor tasks?

Yes, workflow state checkpointing applies to both STANDARD and COMPLEX ks-conductor tasks. It tracks phase transitions from INTAKE through SCOUT, PLAN, BUILD, VERIFY, and CLOSE, writing atomic updates to the workflow_state.md file.

How do I set up workflow state resume using checkpoint files in a ks-conductor run?

To set up workflow state resume, run a ks-conductor workflow and ensure the workflow_state.md file is updated atomically at each phase boundary. The Skill writes updates to .cursor/plans/workflow_state.md based on per-phase transitions.

What are the limitations of using markdown files for durable workflow state tracking?

Using markdown files for workflow state tracking relies on atomic writes at phase boundaries to prevent data corruption. It requires referencing templates for structure and is specifically designed for ks-conductor runs surviving context compaction.