Slash Command

/status

Agent execution dashboard. Show current cycle state and agent activity.

Install

Run in your terminal

npx claudepluginhub guygrigsby/claude-plugins --plugin wu

Command Content

Other plugins with /status

/status

Display Conductor project status including overall progress, active tracks summary, and next actions. Optional [track-id] [--detailed] for per-track task details and blockers.

conductor

32.9k

/status

Displays compact planning status from task_plan.md: current phase and progress, phase list with icons, error count, and planning file checks.

planning-with-files

18.1k

/status

Shows active and recent Codex jobs for this repository in a compact Markdown table, including review-gate status. Pass job ID for full details; supports --wait, --timeout-ms, --all.

Bash(node:*)

codex

11.4k

/status

commands/

Displays current design system state from .interface-design/system.md including direction, foundation, depth, tokens, patterns, and last updated time. Suggests setup options if no system found.

interface-design

4.4k

/status

Displays status of tasks in the orchestration system, including summaries, distributions, detailed views, timelines, and velocity reports with filters for date, status, agent, priority, and type.

Write

all-commands

2.7k

/status

Displays status of tasks in the orchestration system, including summaries, distributions, detailed views, timelines, and velocity reports with filters for date, status, agent, priority, and type.

Write

commands-workflow-orchestration

2.7k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 31, 2026

Actions

View Source View Plugin View on GitHub View README

What to do

Read cycle state. Load .wu/state.json. If it does not exist, tell the user: "No active wu cycle. Run /wu:new to start one." and stop.

Show current cycle info:

Cycle slug
Description
Current phase
Status (active, paused, completed, failed)
Created timestamp

Show phase history. Read .wu/phases/ directory. For each phase record:

Phase name
Status: completed, pending, skipped, failed, overridden
Duration (if completed)
Display as a table with checkmarks for completed, dashes for pending, X for failed.

Show agent activity. Read .wu/audit.jsonl (or .wu/audit.log). Show the most recent 10 dispatches:

Agent alias and display name
Phase dispatched in
Status (success, failure, timeout)
Duration
Tokens used (if recorded)
Display as a table sorted by most recent first.

Show budget summary. Read .wu/config.json for budget_threshold. Compute total tokens used from audit log.

Tokens used vs threshold
Percentage consumed
If over 80%, warn: "Budget approaching limit."
If over 100%, warn: "Budget exceeded."

Show active conflicts. Check phase records and cipher round results for unresolved conflicts.

If any exist, list them with: source agents, severity, description.
If none, show: "No active conflicts."

You are running the status dashboard for wu.

What to do

Read cycle state. Load .wu/state.json. If it does not exist, tell the user: "No active wu cycle. Run /wu:new to start one." and stop.
Show current cycle info:
- Cycle slug
- Description
- Current phase
- Status (active, paused, completed, failed)
- Created timestamp
Show phase history. Read .wu/phases/ directory. For each phase record:
- Phase name
- Status: completed, pending, skipped, failed, overridden
- Duration (if completed)
- Display as a table with checkmarks for completed, dashes for pending, X for failed.
Show agent activity. Read .wu/audit.jsonl (or .wu/audit.log). Show the most recent 10 dispatches:
- Agent alias and display name
- Phase dispatched in
- Status (success, failure, timeout)
- Duration
- Tokens used (if recorded)
- Display as a table sorted by most recent first.
Show budget summary. Read .wu/config.json for budget_threshold. Compute total tokens used from audit log.
- Tokens used vs threshold
- Percentage consumed
- If over 80%, warn: "Budget approaching limit."
- If over 100%, warn: "Budget exceeded."
Show active conflicts. Check phase records and cipher round results for unresolved conflicts.
- If any exist, list them with: source agents, severity, description.
- If none, show: "No active conflicts."

Output format

Use tables for readability. Group sections with headers. Keep output concise — this is a dashboard, not a report.

Notes

This command is read-only. It does not modify any state.
If audit log is empty, show "No agent activity recorded."
If config is missing, skip budget section and note it.