LIFEAI/rdc:status

⚠️ OUTPUT CONTRACT (READ FIRST): guides/output-contract.md Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps. One checklist upfront, updated in place, shown again at end with a 1-line verdict.

If dispatching subagents or running as a subagent: read {PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md first (fallback: {PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md).

rdc:status — Project Dashboard

When to Use

• Start of any session
• Project lead asks "what's the status", "where are we", "what's open"
• Before deciding what to work on next

Procedure

1. Open epics:

   SELECT get_open_epics();
   

2. Work item counts by status:

   SELECT status, count(*) FROM work_items 
   WHERE status != 'archived' 
   GROUP BY status ORDER BY status;
   

3. Items by label/project (top 10 labels):

   SELECT unnest(labels) as label, count(*), 
          count(*) FILTER (WHERE status = 'done') as done,
          count(*) FILTER (WHERE status = 'todo') as todo,
          count(*) FILTER (WHERE status = 'in_progress') as wip
   FROM work_items 
   GROUP BY label ORDER BY count DESC LIMIT 10;
   

4. Recent activity (last 48 hours):

   SELECT title, status, updated_at 
   FROM work_items 
   WHERE updated_at > now() - interval '48 hours'
   ORDER BY updated_at DESC LIMIT 15;
   

5. Git status:

   git log --oneline -10
   git status
   git branch -v
   

6. Dev server health (PM2): SSH into the Coolify server and check PM2 process state:

   # Note: clauth key name for the SSH key may vary by project. Common names: ssh-key-path, vultr-ssh-key, dev-ssh-key.
   # Check available keys with: curl -s http://127.0.0.1:52437/list-services
   SSH_KEY=$(curl -s http://127.0.0.1:52437/v/ssh-key-path)
   ssh -i "$SSH_KEY" -o StrictHostKeyChecking=no [email protected] "pm2 jlist 2>/dev/null"
   

   Parse the JSON array — for each process note name, pm2_env.status (online/stopped/errored), and pm2_env.pm_uptime. If SSH fails or PM2 returns nothing, note "PM2 unreachable" and continue.

7. Infrastructure health (if MCP available):

   • Get infrastructure overview or diagnose issues
   • Report any apps with failed builds or down containers

8. Present as a compact dashboard:

   ## Open Epics (N)
   <table>
   
   ## Work Items: X done | Y todo | Z in_progress
   
   ## Recent (48h)
   <list>
   
   ## Dev Servers (PM2)
   online: studio canvas lifeai ...   stopped: issho-invest
   
   ## Deployments
   <green/red/yellow status>
   
   ## Recommended Next
   <highest priority unstarted epic>
   

Rules

• Keep output concise — this is a glance, not a deep dive
• Always end with a recommendation for what to work on next
• After the Recommended Next section, suggest which guide file from .rdc/guides/ (fallback: .rdc/guides/) the recommended work would need
• Use database MCP for queries (not raw curl)
• If infrastructure MCP is unavailable, skip deployment status and note it