Workflow Status

Retrieves Workflow state from .org/.md files in plugin and legacy directories.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill workflow-status-zb-ss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Workflow Status
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/status
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill workflow-status-zb-ss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, glob, read.

What problem does it solve?

This Skill helps you quickly understand whether your Claude workflow runs are active, paused, or completed, and what step is currently in progress.

Core Features & Use Cases

  • List active and recent workflows across the plugin’s repo-scoped state and legacy flat layout files for backwards compatibility.
  • Inspect a specific workflow by ID, including type, mode, branch, start time, overall status, and per-step progress/iterations.
  • Review completed history (including last 5) and optionally show all active/light-style JSON plus recent completed records.

Quick Start

Ask for status by running /workflow:status <workflow_id> to see the full step-by-step progress and current iteration for that workflow.

Frequently Asked Questions about Workflow Status

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

FAQPage Schema
How do I check the status of an active workflow run?

To check active workflow status, use the /workflow:status <workflow_id> command to locate state files and summarize current step progress, modes, timestamps, and iterations.

What's the best way to list all active and recently completed workflows?

List active and recent workflows by requesting a status overview, which aggregates plugin repo-scoped state files and legacy flat layout files to display current and historical run metadata.

How does workflow state tracking parse step progress from files?

Workflow state tracking uses absolute-path globbing and file reads to parse .org and .md state formats, extracting metadata like step statuses, modes, start times, and current iteration counts.

Can I view the full history of completed workflow runs?

Yes, you can review completed history by requesting full aggregation, which displays all active light-style JSON records alongside recent completed workflow files from legacy directories.

Why does my workflow status show legacy directory files?

Legacy flat layout files are included for backwards compatibility, allowing the status retrieval process to locate and parse state formats across both plugin repo-scoped and older directory structures.

Do I need node and glob installed to inspect workflow state?

Yes, inspecting workflow state requires node, glob, and read dependencies to perform absolute-path globbing and parse .org and .md state files for step progress and metadata summarization.