status
The /status command provides a real-time dashboard of AgentOps workflow state, displaying current work items, recent activity, task progress, and knowledge metrics. Use this to quickly assess what you're working on, review recent sessions and decisions, check git status, and understand overall system health across ratchet phases, epic progress, and learning metrics.
git clone --depth 1 https://github.com/boshu2/agentops /tmp/status && cp -r /tmp/status/images/gemini/skills/status ~/.claude/skills/statusSKILL.md
# /status — Workflow Dashboard
> **Purpose:** Single-screen overview of your current state. What am I working on? What happened recently? What should I do next?
**YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.**
**CLI dependencies:** bd, ao, gt — all optional. Shows what's available, skips what isn't.
---
## Quick Start
```bash
/status # Full dashboard
/status --json # Machine-readable JSON output
```
---
## Execution Steps
### Step 1: Gather State (Parallel)
Run ALL of the following in parallel bash calls for speed:
**Call 0 - Reconciliation Snapshot:**
```bash
if command -v ao &>/dev/null; then
ao reconcile --json 2>/dev/null || echo "RECONCILE_UNAVAILABLE"
else
echo "AO_UNAVAILABLE"
fi
```
**Call 1 — RPI + Ratchet + Task State:**
```bash
# Current ratchet phase
if [ -f .agents/ao/chain.jsonl ]; then
tail -1 .agents/ao/chain.jsonl 2>/dev/null
else
echo "NO_CHAIN"
fi
# Ratchet status via CLI
if command -v ao &>/dev/null; then
ao ratchet status --json 2>/dev/null || echo "RATCHET_UNAVAILABLE"
ao task-status --json 2>/dev/null || echo "TASK_STATUS_UNAVAILABLE"
fi
```
**Call 2 — Beads / Epic State:**
```bash
if command -v bd &>/dev/null; then
echo "=== EPIC ==="
bd list --type epic --status open 2>/dev/null | head -5
echo "=== IN_PROGRESS ==="
bd list --status in_progress 2>/dev/null | head -5
echo "=== READY ==="
bd ready 2>/dev/null | head -5
echo "=== TOTAL ==="
bd list 2>/dev/null | wc -l
else
echo "BD_UNAVAILABLE"
fi
```
**Call 3 — Knowledge Flywheel:**
```bash
# Learnings count
echo "LEARNINGS=$(ls .agents/learnings/ 2>/dev/null | wc -l | tr -d ' ')"
echo "PATTERNS=$(ls .agents/patterns/ 2>/dev/null | wc -l | tr -d ' ')"
echo "PENDING=$(ls .agents/forge/ 2>/dev/null | wc -l | tr -d ' ')"
# Flywheel health + badge
if command -v ao &>/dev/null; then
ao metrics flywheel status 2>/dev/null || echo "FLYWHEEL_UNAVAILABLE"
ao badge 2>/dev/null || echo "BADGE_UNAVAILABLE"
fi
```
**Call 4 — Recent Activity + Git:**
```bash
# Recent sessions
if [ -d .agents/ao/sessions ]; then
ls -t .agents/ao/sessions/*.md 2>/dev/null | head -3
else
echo "NO_SESSIONS"
fi
# Recent council verdicts
ls -lt .agents/council/ 2>/dev/null | head -4
# Git state
echo "=== GIT ==="
git branch --show-current 2>/dev/null
git log --oneline -3 2>/dev/null
git status --short 2>/dev/null | head -5
```
**Call 5 — Inbox:**
```bash
if command -v gt &>/dev/null; then
gt mail inbox 2>/dev/null | head -5
else
echo "GT_UNAVAILABLE"
fi
```
**Call 6 — Session Quality Signals:**
```bash
if [ -f .agents/signals/session-quality.jsonl ]; then
tail -10 .agents/signals/session-quality.jsonl
else
echo "NO_SIGNALS"
fi
```
### Step 2: Render Dashboard
Assemble gathered data into this format. Use Unicode indicators for visual clarity:
- Pass/healthy: `[PASS]`
- Warning/partial: `[WARN]`
- Fail/missing: `[FAIL]`
- Progress: `[3/7]` with bar `███░░░░`
```
══════════════════════════════════════════════════
Workflow Dashboard
══════════════════════════════════════════════════
RECONCILIATION
Overall: <ao reconcile overall_status, or "unavailable">
High: <top high-severity findings, max 3, or "none">
Next: <first high finding next_action, or "none">
RPI PROGRESS
Phase: <current phase from chain.jsonl: research | plan | implement | validate | idle>
Gate: <last completed gate or "none">
─────────────────────────────────
research ── plan ── implement ── validate
<mark current position with arrow or highlight>
ACTIVE EPIC
<epic title and ID, or "No active epic">
Progress: <completed>/<total> issues <progress bar>
In Progress: <list in-progress issues, max 3>
READY TO WORK
<top 3 unblocked issues from bd ready>
<or "No ready issues — create work with /plan">
RECENT VALIDATIONS
<last 3 council reports with verdict>
<format: date verdict target>
<or "No recent validations">
KNOWLEDGE FLYWHEEL
Learnings: <count> Patterns: <count> Pending: <count>
Health: <flywheel status or "ao not installed">
Badge: <ao badge output or omit if unavailable>
TASK MATURITY
<ao task-status summary: active tasks with CASS maturity levels, or omit if unavailable>
RECENT SESSIONS
<last 3 session summaries with dates>
<or "No session history">
GIT STATE
Branch: <current branch>
Recent: <last 3 commits, one-line>
Changes: <uncommitted file count or "clean">
INBOX
<message count or "No messages" or "gt not installed">
SESSION QUALITY SIGNALS
<last 10 entries from .agents/signals/session-quality.jsonl as table>
| Timestamp | Signal | Detail | Session |
|-----------|--------|--------|---------|
<parsed from JSON lines: .timestamp, .signal, .detail, .session>
<or "No quality signals recorded." if file missing or empty>
──────────────────────────────────────────────────
SUGGESTED NEXT ACTION
<state-aware suggestion — see Step 3>
──────────────────────────────────────────────────
QUICK COMMANDS
/research Deep codebase exploration
/plan Decompose epic into issues
/pre-mortem Validate plan before coding
/implement Execute a single issue
/crank Autonomous epic execution
/validate Full close-out and learnings
/vibe Targeted code review
ao reconcile --json Joined git/CI/release/beads/.agents truth
══════════════════════════════════════════════════
```
### Step 3: Suggest Next Action (State-Aware)
Evaluate state top-to-bottom. Use the FIRST matching condition:
| Priority | Condition | Suggestion |
|----------|-----------|------------|
| 0 | `ao reconcile` reports a high-severity finding | "Resolve reconciliation blockers from `ao reconcile --json` before picking backlog work" |
| 1 | No ratchet chain exists | "Start with `/quickstart` or `/research` to begin a workflow" |
| 2 | Research done, no plan | "Run `/plan` to decompose research into actionable issues" |
| 3 | Plan done, no pre-mortem | "Run `/pre-mortem` to validate the plan before coding" |
| 4Use Agent Mail from Codex for file leases, notifications, inboxes, and conflict prevention.
>-
>-
Use when converting markdown plans into br beads with dependencies for implementation or swarm execution.
Use when switching AI coding CLI accounts quickly to recover from subscription rate limits or OAuth friction.
>-
Use when starting non-trivial work, mining lessons, or preventing repeated mistakes with cm procedural memory.
Mine past agent sessions for working prompts, decisions, and patterns. Use when "what did I ask?", "find that prompt", session archaeology, or agent history.