Show unified system status: backlog, recent activity, team health, and last session summary. Use when you want a full picture of where things stand in one view. Keywords: status, overview, dashboard, state, orientation.
You are generating a system status snapshot — a single-command overview of backlog, recent activity, team health, and last session state. This is a read-only, low-cost diagnostic.
Focus area (optional): $ARGUMENTS
Read known paths → Run bd + git commands → Format sections → Suggest actions
No agents dispatched. No files written. Pure read + format.
Gather all data before producing any output. Read from the known paths defined in rules/memory-layout.md.
Read memory/sessions/last.md. If it does not exist, note "No previous session data."
If .beads/ exists, run:
bd stats
bd ready
bd epic status
If .beads/ does not exist, note "Beads not configured."
Run:
git branch --show-current
git log --oneline -5
git status --short
If team.yaml exists, read it to get the team name and member list. Then for each member, check memory/agents/<name>/learnings.md:
If team.yaml does not exist, note "No team configured."
Prefer git-intel when available, fall back to git-pulse.sh:
If tools/git-intel/target/release/git-intel exists, run:
tools/git-intel/target/release/git-intel churn --repo . --limit 10
Parse the JSON output to extract files sorted by total_churn (additions + deletions).
Else if git-pulse.sh is available (check bin/git-pulse.sh), run:
bin/git-pulse.sh --since="7 days ago" 2>/dev/null
Extract the churn_N lines from the output. These show files with highest modification frequency.
If neither tool exists, skip this section.
Present all collected data in this structure. Do not add commentary or analysis beyond what is specified — keep it mechanical and cheap.
## System Status
**Branch**: [current branch]
**Date**: [today]
### Last Session
[Contents of memory/sessions/last.md — include verbatim, trimmed to first 20 lines if longer]
[Or: "No previous session data."]
### Backlog
[bd stats output, formatted]
[bd ready output — show task titles, max 5]
[Or: "Beads not configured."]
### Epic Progress
[bd epic status output — show each epic with completion %]
[Omit section if no epics exist or beads not configured]
### Recent Activity
[git log --oneline -5 output]
**Working tree**: [clean | N files modified/untracked]
[If dirty, show git status --short output]
### Hotspots
[If git-intel data collected:]
| File | Edits | +/- | Churn |
|------|-------|-----|-------|
| [path] | [commit_count] | +[additions]/-[deletions] | [total_churn] |
| [path] | [commit_count] | +[additions]/-[deletions] | [total_churn] |
...
Show top 5-10 files by total_churn.
[Else if git-pulse.sh data collected:]
| File | Edits (7d) |
|------|------------|
| [path] | [N] |
| [path] | [N] |
...
Show top 5-10 churning files from the `churn_N` lines.
[If no churn data available, omit this section entirely.]
### Team
[Team name and member table:]
| Member | Role | Learnings | Health |
|--------|------|-----------|--------|
| [name] | [role from team.yaml] | [N lines] | [see below] |
Health values (mechanical):
- **active**: learnings file exists, >0 lines
- **cold**: learnings file missing or empty
- **bloated**: learnings file >120 lines
[Or: "No team configured."]
### Suggested Actions
[Numbered list, derived mechanically from the data above]
Generate 1-5 suggestions based purely on observed state. Use these rules:
| Condition | Suggestion |
|---|---|
| Working tree is dirty | "Commit or stash uncommitted changes" |
| Ready tasks exist (beads) | "Work on: [top 3 ready task titles]" |
| Blocked tasks exist | "Unblock: [blocked task titles]" |
| Any team member is bloated (>120 lines) | "Run /retro to consolidate [member] learnings" |
| Any team member is cold | "Dispatch work to [member] to build learnings" |
| No last session file | "First session — review backlog and pick a starting task" |
| In-progress tasks exist | "Resume in-progress work: [task titles]" |
| Epics with all children complete | "Run bd epic close-eligible to auto-close completed epics" |
| Everything is clean and no ready tasks | "Backlog is clear — create new tasks or run /blossom to explore" |
| Any file has >3x the average churn count | "Review [file path] for stability — high churn may indicate design issues" |
Only include suggestions that match the current state. Do not invent conditions.
See also: /evolution (definition change tracking for deeper investigation of churn patterns). /standup (team-aware equivalent — use standup when a team is configured). /session-health (focused diagnostic when something feels off in the current session).