status
Show AgentOps work status.
What this skill does
# /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" |
| 4 | Issues in-progress | "Continue working: `/implement <issue-id>` or `/crank` for autonomous execution" |
| 5 | Ready issues available | "Pick up next issue: `/implement <first-ready-id>`" |
| 6 | Uncommitted changes | "Review recent work: `/validate`" |
| 7 | Implementation done, no vibe | "Run `/validate` for final close-out" |
| 8 | Recent WARN/FAIL verdict | "Address findings in `<report-path>`, then re-run `/validate`" |
| 10 | Vibe passed, no post-mortem | "Run `/validate` to complete closeout and extract learnings" |
| 11 | Pending knowledge items | "Promote learnings: `ao pool list --status pending --json`, then `ao pool stage <id>` and `ao pool promote <id>`" |
| 12 | Clean state, nothing pending | "All clear. Start with `/research` or `/plan` to find new work" |
If Call 0 is unavailable, skip Priority 0 and continue evaluating the remaining conditions.
### Step 4: JSON Output (--json flag)
If the user passed `--json`, output all dashboard data as structured JSON instead of the visual dashboard:
```json
{
"reconciliation": {
"overall_status": "green",
"high_findings": []
},
"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 },
"session_quality_signals": [
{ "timestamp": "2026-03-31T14:22:00Z", "signal": "drift", "detail": "3 corrections in 5min", "session": "abc123" }
],
"suggestion": {
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.