home / skills / shotaiuchi / dotclaude / wf0-status

wf0-status skill

safe

This skill displays the current workflow status and summaries for a specified work or all works, helping you monitor progress and identify issues.

npx playbooks add skill shotaiuchi/dotclaude --skill wf0-status

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

983 B

---
name: wf0-status
description: 現在のワークフロー状態を表示
argument-hint: "[work-id | all]"
---

**Always respond in Japanese.**

# /wf0-status

Display current workflow status.

## Usage

```
/wf0-status [work-id | all]
```

## Arguments

- `work-id`: Specific work to display (optional)
- `all`: Display all works
- Omitted: Use `active_work` from state.json

## Processing

### Single Work Display

Show: work-id, branch, base, current/next phase, created_at, document existence check (00-05), phase progress with current marker, git status (current branch, uncommitted changes count).

If worktree enabled: show worktree path from `.wf/local.json`. If `local.json` missing, show worktree list and suggest `/wf0-restore`.

### All Works Display

Table: Work ID, Branch, Current, Next. Show active work indicator and total count.

## Notes

- Prompt initialization if state.json missing
- Show message if no active_work set
- Error if specified work-id not found

Overview

This skill displays the current workflow status for one or all works managed by the workflow tool. It provides concise, actionable information such as branch, phase, document checks, and Git status so you can quickly assess progress. It also handles missing state or local files with clear prompts and suggestions.

How this skill works

Invoke the command with an optional work-id or the keyword 'all'. When a single work is requested, the skill reads state.json and local metadata to show branch, base, current/next phase, creation time, document existence (00–05), phase progress, and Git status including uncommitted change count. When 'all' is used, it outputs a compact table of work IDs with branch, current and next phases, highlights the active work, and reports the total count. The skill detects missing or malformed state/local files and returns guidance or errors if a work-id is not found.

When to use it

You need a quick summary of the current state for a specific work.
You want an overview of all works to decide what to work on next.
You suspect Git changes or uncommitted files and need confirmation.
State or local metadata may be missing and you need guidance.
You want to verify whether required documents (00–05) exist for a work.

Best practices

Run without arguments to inspect the active_work stored in state.json.
Use a specific work-id to focus on a single work and avoid clutter.
Use 'all' to get a high-level inventory before planning or switching tasks.
Keep state.json and .wf/local.json committed or backed up to avoid prompt initialization.
Address uncommitted changes promptly; the report shows counts to prioritize commits.

Example use cases

wf0-status (no args) to confirm the active work and its current phase before starting a session.
wf0-status work-123 to inspect branch, next phase, and whether required documents exist for work-123.
wf0-status all to generate a quick table of every work and identify idle or blocked items.
Run after switching branches to confirm the Git status and count of uncommitted files.
Run when a worktree appears missing to get the list of available worktrees and a hint to restore.

FAQ

What happens if state.json is missing?

The skill prompts initialization and explains how to create or restore state.json so you can proceed.

What if I specify a work-id that doesn't exist?

The skill returns an explicit error indicating the work-id was not found and suggests listing all works with 'all' to verify available IDs.