Back to Details

status

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/status — Workflow Dashboard

/status — 工作流仪表盘

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.
用途： 单屏概览你的当前状态：我正在做什么？最近发生了什么？下一步应该做什么？
你必须执行此工作流，而不只是描述它。
CLI依赖： bd、ao、gt — 均为可选依赖。会展示可用的内容，跳过不可用的部分。

Quick Start

快速开始

bash
/status              # Full dashboard
/status --json       # Machine-readable JSON output
bash
/status              # 完整仪表盘
/status --json       # 机器可读的JSON输出

Execution Steps

执行步骤

Step 1: Gather State (Parallel)

步骤1：收集状态（并行执行）

Run ALL of the following in parallel bash calls for speed:
Call 1 — RPI + Ratchet State:
bash
undefined
为提升速度，并行运行以下所有bash命令：
调用1 — RPI + Ratchet状态：
bash
undefined

Current ratchet phase

当前ratchet阶段

if [ -f .agents/ao/chain.jsonl ]; then tail -1 .agents/ao/chain.jsonl 2>/dev/null else echo "NO_CHAIN" fi
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

通过CLI查看Ratchet状态

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
undefined
if command -v ao &>/dev/null; then ao ratchet status -o json 2>/dev/null || echo "RATCHET_UNAVAILABLE" fi

**调用2 — Beads / Epic状态：**
```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
调用3 — 知识飞轮：
bash
undefined

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 ' ')"
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
if command -v ao &>/dev/null; then ao flywheel status 2>/dev/null || echo "FLYWHEEL_UNAVAILABLE" fi

**调用4 — 近期活动 + 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
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
ls -lt .agents/council/ 2>/dev/null | head -4

Git state

Git状态

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
echo "=== GIT ===" git branch --show-current 2>/dev/null git log --oneline -3 2>/dev/null git status --short 2>/dev/null | head -5

**调用5 — 收件箱：**
```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

步骤2：渲染仪表盘

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
══════════════════════════════════════════════════

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">

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">

──────────────────────────────────────────────────
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
  /vibe         Validate code quality
  /post-mortem  Extract learnings, close cycle
══════════════════════════════════════════════════
将收集到的数据整理为以下格式，使用Unicode标识提升视觉清晰度：
  • 通过/健康：
    [PASS]
  • 警告/部分完成：
    [WARN]
  • 失败/缺失：
    [FAIL]
  • 进度：
    [3/7]
    搭配进度条 
    ███░░░░
══════════════════════════════════════════════════
  工作流仪表盘
══════════════════════════════════════════════════

RPI 进度
  阶段：<从chain.jsonl获取的当前阶段：research | plan | implement | validate | idle>
  关卡：<最后完成的关卡或“无”>
  ─────────────────────────────────
  research ── plan ── implement ── validate
     <用箭头或高亮标记当前位置>

活跃EPIC
  <EPIC标题和ID，或“无活跃EPIC”>
  进度：<已完成>/<总数量> 事项  <进度条>
  进行中：<进行中事项列表，最多3个>

可开始工作
  <从bd ready获取的前3个未阻塞事项>
  <或“无可开始工作事项 — 使用/plan创建工作内容”>

近期验证
  <最近3份评审报告及结果>
  <格式：日期  结果  目标>
  <或“无近期验证记录”>

知识飞轮
  经验总结：<数量>  模式：<数量>  待处理：<数量>
  健康状态：<飞轮状态或“ao未安装”>

近期会话
  <最近3个会话摘要及日期>
  <或“无会话历史”>

Git状态
  分支：<当前分支>
  近期提交：<最近3条单行提交记录>
  变更：<未提交文件数量或“干净”>

收件箱
  <消息数量或“无消息”或“gt未安装”>

──────────────────────────────────────────────────
建议下一步操作
  <基于状态的建议 — 见步骤3>
──────────────────────────────────────────────────

快捷命令
  /research     深度代码库探索
  /plan         将EPIC分解为可执行事项
  /pre-mortem   编码前验证计划
  /implement    执行单个事项
  /crank        自动执行EPIC
  /vibe         验证代码质量
  /post-mortem  提取经验总结，结束周期
══════════════════════════════════════════════════

Step 3: Suggest Next Action (State-Aware)

步骤3：建议下一步操作（状态感知）

Evaluate state top-to-bottom. Use the FIRST matching condition:
PriorityConditionSuggestion
1Inbox has unread messages"Check messages: 
/inbox
"
2No ratchet chain exists"Start with 
/quickstart
or 
/research
to begin a workflow"
3Research done, no plan"Run 
/plan
to decompose research into actionable issues"
4Plan done, no pre-mortem"Run 
/pre-mortem
to validate the plan before coding"
5Issues in-progress"Continue working: 
/implement <issue-id>
or 
/crank
for autonomous execution"
6Ready issues available"Pick up next issue: 
/implement <first-ready-id>
"
7Uncommitted changes"Review changes: 
/vibe recent
"
8Implementation done, no vibe"Run 
/vibe
for final code validation"
9Recent WARN/FAIL verdict"Address findings in 
<report-path>
, then re-run 
/vibe
"
10Vibe passed, no post-mortem"Run 
/post-mortem
to extract learnings and complete the cycle"
11Pending knowledge items"Promote learnings: 
ao pool promote
"
12Clean state, nothing pending"All clear. Start with 
/research
or 
/plan
to find new work"
从上到下评估状态，使用第一个匹配的条件：
优先级条件建议
1收件箱有未读消息"查看消息：
/inbox
"
2无ratchet链存在"从
/quickstart
或
/research
开始，启动工作流"
3已完成调研，无计划"运行
/plan
将调研内容分解为可执行事项"
4已有计划，未执行预评审"运行
/pre-mortem
在编码前验证计划"
5有事项正在进行中"继续工作：
/implement <事项ID>
或 
/crank
自动执行"
6有可开始工作的事项"开始下一个事项：
/implement <首个可执行事项ID>
"
7有未提交的变更"查看变更：
/vibe recent
"
8已完成开发，未执行/vibe"运行
/vibe
进行最终代码验证"
9近期有WARN/FAIL结果"处理
<报告路径>
中的问题，然后重新运行
/vibe
"
10/vibe已通过，未执行事后总结"运行
/post-mortem
提取经验总结，完成周期"
11有待处理的知识项"推广经验总结：
ao pool promote
"
12状态干净，无待处理事项"一切就绪。使用
/research
或
/plan
开始新工作"

Step 4: JSON Output (--json flag)

步骤4：JSON输出（--json参数）

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.
如果用户传入
--json
参数，将所有仪表盘数据以结构化JSON格式输出，而非可视化仪表盘：
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"
  }
}
使用单个代码块渲染该内容。当
--json
参数生效时，不展示可视化仪表盘。

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
  • skills/quickstart/SKILL.md
    — 首次使用引导
  • skills/inbox/SKILL.md
    — Agent邮件监控
  • skills/knowledge/SKILL.md
    — 查询知识工件
  • skills/ratchet/SKILL.md
    — RPI进度关卡