Status

# Executable spec for the /status skill — work-status dashboard (driving-adapter).
# /status reports current AgentOps work state — its primary source is the bd tracker
# (ready/in-progress/epics) augmented with ratchet, flywheel, and git state — as a human
# dashboard or machine-readable JSON, degrading gracefully when a tool is missing. Hexagon:
# driving-adapter; consumes bd; produces stdout. (soc-qk4b)

Feature: Status shows the AgentOps work dashboard
  As an agent or operator orienting in a repo
  I want current work state surfaced from the tracker in one view
  So that I can see ready/in-progress work and project health at a glance

  Scenario: the dashboard reports work state from bd
    When /status runs
    Then it reports work state from bd (ready, in-progress, open epics)
    And it augments that with ratchet, flywheel, and git state

  Scenario: --json gives machine-readable output
    When /status --json runs
    Then it emits the same status as structured JSON

  Scenario: missing tools degrade gracefully
    When a data source (ratchet/flywheel) is unavailable
    Then /status marks that section unavailable and still renders the rest, without crashing


#!/usr/bin/env bash
set -euo pipefail
SKILL_DIR="$(cd "$(dirname "$0")/.." && pwd)"
PASS=0; FAIL=0

check() { if bash -c "$2"; then echo "PASS: $1"; PASS=$((PASS + 1)); else echo "FAIL: $1"; FAIL=$((FAIL + 1)); fi; }

check "SKILL.md exists" "[ -f '$SKILL_DIR/SKILL.md' ]"
check "SKILL.md has YAML frontmatter" "head -1 '$SKILL_DIR/SKILL.md' | grep -q '^---$'"
check "SKILL.md has name: status" "grep -q '^name: status' '$SKILL_DIR/SKILL.md'"
check "SKILL.md mentions dashboard" "grep -qi 'dashboard' '$SKILL_DIR/SKILL.md'"
check "SKILL.md mentions suggested next action" "grep -qi 'suggested next action\|suggest next action\|suggestion' '$SKILL_DIR/SKILL.md'"

echo ""; echo "Results: $PASS passed, $FAIL failed"
[ $FAIL -eq 0 ] && exit 0 || exit 1


---
name: status
description: Show AgentOps work status.
practices:
- dora-metrics
- sre
hexagonal_role: driving-adapter
consumes:
- bd
produces:
- stdout
context_rel: []
skill_api_version: 1
allowed-tools: Read, Grep, Glob, Bash
model: haiku
context:
  window: inherit
  intent:
    mode: none
  intel_scope: none
metadata:
  tier: session
  dependencies: []
output_contract: 'stdout: dashboard'
---
# /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