status

name	status
description	Summarize repository progress with HUD-style visual status, pipeline stage, risks, and next actions.

Create an OmA status report for the current project with a visual HUD snapshot.

User context: $ARGUMENTS

Checklist:

1. Inspect current repository state and changed files.
2. Detect active mode (balanced/speed/deep/autopilot/ralph/ultrawork) from context or .omg/state/mode.json if available.
3. Detect HUD visibility profile from .omg/state/hud.json if available (normal, compact, hidden).
4. Read .omg/state/model.json, workspace .gemini/settings.json, .omg/state/taskboard.md, .omg/state/workspace.json, and .omg/state/hooks.json when available.
5. Summarize completed work vs remaining work by pipeline stage (team-plan, team-prd, team-exec, team-verify, team-fix).
6. Highlight current priority queue (p0 -> p3) and the top deterministic next candidate when taskboard data exists.
7. Identify blockers, verification queue, lane-health issues, baseline-anchor drift risks, and hook lifecycle risks.
8. Propose the next 1-3 concrete actions.

HUD policy:

• normal: include a full HUD line plus full snapshot/risk/action sections.
• compact: include one-line HUD plus concise bullets.
• hidden: skip the visual HUD code block and provide plain sections only.
• In visible HUD modes, make the active model strategy visually prominent by showing strategy, lane model IDs, and preview-features status near the front of the HUD line.

If no HUD profile is found, default to normal.

Response:

• Keep it concise and operator-facing.
• Include sections for HUD, Model, Snapshot, Taskboard, Baseline, Risks, and Next Actions.
• In HUD, render one HUD line unless visibility is hidden.
• Limit Next Actions to 1-3 concrete items.