status

Inspects Arc workflow state and generates a status report with recommended next steps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cmtkdot/arc --skill status-cmtkdot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/cmtkdot/arc/tree/main/skills/status
Command: npx skills add https://github.com/cmtkdot/arc --skill status-cmtkdot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect and recover workflow state. Use this to check progress, find where a session left off, or resume interrupted execution.

Core Features & Use Cases

  • Restore state from Beads status, task lists, last known plan/spec references, and .arc/state.json
  • Reconcile live execution with saved state to provide consistent progress views
  • Generate a concise status report and recommended next steps for continuation

Quick Start

Check the current session progress by invoking the status command in your Arc workflow.

Frequently Asked Questions about status

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

FAQPage Schema
How do I check Arc session progress and find where a workflow left off?

To check Arc session progress, inspect Beads status, task lists, and the persisted .arc/state.json to reconcile live execution with saved state and generate a concise progress overview.

How do I resume an interrupted Arc workflow execution?

To resume an interrupted Arc workflow, restore state from Beads status, task lists, plan references, and .arc/state.json to reconcile the saved checkpoint and follow recommended next steps for continuation.

What workflow state sources are inspected to monitor an active Arc session?

Monitoring an active Arc session inspects Beads status, task list state, workspace plan references, and the persisted .arc/state.json file to present a consistent progress view and next-step guidance.

Can I debug Arc session interruptions by reading .arc/state.json?

Debugging Arc session interruptions involves reading .arc/state.json alongside Beads status and task lists to reconcile live execution with saved state and identify the exact checkpoint to resume.

Does this workflow status recovery approach require any external dependencies?

Workflow status recovery requires no external dependencies, relying entirely on internal Arc session state files like .arc/state.json, Beads status, and task list references to restore progress.

Why does my Arc workflow state show inconsistent progress after an interruption?

Inconsistent workflow progress after an interruption occurs when live execution diverges from saved state; reconciling Beads status, task lists, and .arc/state.json resolves the discrepancy and provides accurate next steps.