save-workflow-state

Save workflow state by persisting conductor workflow progress to a JSON file (.claude/state/conductor.json). This captures issue metadata, current phase, branch information, and context, enabling you to resume exactly where you left off after interruptions.

Workflow state persistence tracks issue number and title, current and completed phases, branch name, files changed, commit count, PR number, architecture plan, and implementation notes. All data is stored as JSON for validation and recovery.

Yes, state persistence applies across all six phases—Issue Discovery, Branch Setup, Implementation, Quality Assurance, PR Creation, and Final Report. Save state after completing each phase to enable smart resumption and prevent duplicate work.

When interrupted, your saved workflow state allows recovery without redundant work. The state file stores complete context so the workflow can pick up exactly where it stopped, maintaining continuity across restarts.

No special setup required—the Skill creates the state directory (.claude/state) and manages JSON storage automatically. It uses only standard tools (jq for JSON processing, date for timestamps) already available in most environments.

Automated workflow state persistence captures comprehensive context—phases, branch details, audit scores, and implementation notes—in a standardized JSON format. This enables deterministic resumption and prevents the gaps that manual checkpointing leaves.