--- name: status description: 'Single-screen dashboard showing current work, recent validations, flywheel health, and suggested next action. Triggers: "status", "dashboard", "what am I working on", "where was I".' dependencies: [] --- # /status — AgentOps 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 1 — RPI + Ratchet 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 -o json 2>/dev/null || echo "RATCHET_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/knowledge/pending/ 2>/dev/null | wc -l | tr -d ' ')" # Flywheel health if command -v ao &>/dev/null; then ao flywheel status 2>/dev/null || echo "FLYWHEEL_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 ``` ### 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 `███░░░░` ``` ══════════════════════════════════════════════════ AgentOps Dashboard ══════════════════════════════════════════════════ RPI PROGRESS Phase: Gate: ───────────────────────────────── research ── plan ── implement ── validate ACTIVE EPIC Progress: / issues In Progress: READY TO WORK RECENT VALIDATIONS KNOWLEDGE FLYWHEEL Learnings: Patterns: Pending: Health: RECENT SESSIONS GIT STATE Branch: Recent: Changes: INBOX ────────────────────────────────────────────────── SUGGESTED NEXT ACTION ────────────────────────────────────────────────── 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 /vibe Validate code quality /post-mortem Extract learnings, close cycle ══════════════════════════════════════════════════ ``` ### Step 3: Suggest Next Action (State-Aware) Evaluate state top-to-bottom. Use the FIRST matching condition: | Priority | Condition | Suggestion | |----------|-----------|------------| | 1 | Inbox has unread messages | "Check messages: `/inbox`" | | 2 | No ratchet chain exists | "Start with `/quickstart` or `/research` to begin a workflow" | | 3 | Research done, no plan | "Run `/plan` to decompose research into actionable issues" | | 4 | Plan done, no pre-mortem | "Run `/pre-mortem` to validate the plan before coding" | | 5 | Issues in-progress | "Continue working: `/implement ` or `/crank` for autonomous execution" | | 6 | Ready issues available | "Pick up next issue: `/implement `" | | 7 | Uncommitted changes | "Review changes: `/vibe recent`" | | 8 | Implementation done, no vibe | "Run `/vibe` for final code validation" | | 9 | Recent WARN/FAIL verdict | "Address findings in ``, then re-run `/vibe`" | | 10 | Vibe passed, no post-mortem | "Run `/post-mortem` to extract learnings and complete the cycle" | | 11 | Pending knowledge items | "Promote learnings: `ao pool promote`" | | 12 | Clean state, nothing pending | "All clear. Start with `/research` or `/plan` to find new work" | ### Step 4: JSON Output (--json flag) If the user passed `--json`, output all dashboard data as structured JSON instead of the visual dashboard: ```json { "rpi": { "phase": "implement", "last_gate": "plan", "chain_entries": 3 }, "epic": { "id": "ag-042", "title": "Epic title", "progress": { "completed": 3, "total": 7, "in_progress": ["ag-042.2"] } }, "ready_issues": ["ag-042.4", "ag-042.5"], "validations": [ { "date": "2026-02-09", "verdict": "PASS", "target": "src/auth/" } ], "flywheel": { "learnings": 12, "patterns": 5, "pending": 2, "health": "healthy" }, "sessions": [ { "date": "2026-02-09", "file": "session-abc.md" } ], "git": { "branch": "main", "uncommitted_count": 3, "recent_commits": ["abc1234 fix: thing", "def5678 feat: other"] }, "inbox": { "count": 0 }, "suggestion": { "priority": 5, "message": "Continue working: /implement ag-042.2" } } ``` Render this with a single code block. No visual dashboard when `--json` is active. --- ## See Also - `skills/quickstart/SKILL.md` — First-time onboarding - `skills/inbox/SKILL.md` — Agent mail monitoring - `skills/knowledge/SKILL.md` — Query knowledge artifacts - `skills/ratchet/SKILL.md` — RPI progress gates