Menú
Inspect live progress of long-running or multi-step work. WorkBuddy has a built-in status display; this skill explains how to read progress via the task list and memory. Trigger "show progress", "what's the status", "hud", "where are we".
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Run a regression-tests-first, smell-by-smell deslop/refactor workflow that preserves behavior and raises signal quality. Use when the user asks to "cleanup", "refactor", "deslop", or when follow-up code has duplicates, dead code, weak boundaries, or fallback-like slop.
Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says "analyze", "investigate", "why does", "what's causing", or needs grounded cross-file explanation before any changes are proposed.
Deprecated compatibility shim for Claude advisor requests. Use `ask` with the claude backend instead.
Deprecated compatibility shim for Gemini advisor requests. Use `ask` with the gemini backend instead.
Ask a locally installed external advisor CLI (Claude or Gemini) for focused questions, reviews, brainstorming, or second opinions, and capture a reusable artifact. Use when the user wants a Claude/Gemini second opinion, "ask claude", or "ask gemini".
Strict autonomous delivery loop that runs deep-interview, ralplan, ultragoal, code-review, and ultraqa in order with automatic re-planning when gates are not clean. Use on "autopilot", "autonomous", "build me", "create me", "make me", "full auto", "handle it all", or "I want a/an…".
| name | hud |
| category | display |
| status | active |
| description | Inspect live progress of long-running or multi-step work. WorkBuddy has a built-in status display; this skill explains how to read progress via the task list and memory. Trigger "show progress", "what's the status", "hud", "where are we". |
| agent_created | true |
| triggers | ["show progress","what's the status","hud","where are we"] |
Ported from oh-my-codex
hud. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
In OMX, the HUD was a TUI statusline plus an omx hud CLI that read .omx/state/*
files. WorkBuddy has a built-in status display — there is no separate HUD to
configure, and no .omx/ state to read. This skill is a short guide to inspecting
progress using WorkBuddy-native surfaces.
The task list is the canonical "HUD" for any multi-step or autonomous work.
pending / in_progress / completed / deleted) and owner.blockedBy), and any notes.in_progress or completed as work advances.This replaces OMX's "modes / turns / activity" HUD entirely — each workflow phase is a task row you can watch update live.
For state that must survive across sessions or be summarized for the user, append to:
.workbuddy/memory/YYYY-MM-DD.md
Use this for: last completed milestone, current phase, open decisions, and handoff
notes. It is the durable analogue of OMX's .omx/state/*.json.
WorkBuddy's own UI already shows model, current directory, and session context. No
configuration (no config.toml [tui] status_line, no .omx/hud-config.json) is
needed or available.
When summarizing progress for the user, reuse a simple traffic-light convention:
omx hud command (no such command exists in WorkBuddy)..omx/ state (that directory does not exist here).To inspect progress, simply read the task list and/or today's memory file.