wf0-status_skill

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

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

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

  • SKILL.md983 B

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

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.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational