---
name: cycle-status
description: >
  Show current cycle health, board state, and recommended next action.
  Use when the user says /cycle-status, "what's the status", "where are we",
  "cycle health", or at the start of a session to orient.
invocable: true
---

# /cycle-status — Cycle Health Check

Run the PAPI health and build list tools to give the user a complete picture of where things stand.

## Steps

1. **Run `health`** — the PAPI MCP tool that returns cycle number, board state, strategy review cadence, Active Decisions summary, velocity, and estimation accuracy.

2. **Run `build_list`** — shows tasks with BUILD HANDOFFs ready for execution, prioritised by status (In Progress first, then Backlog).

3. **Summarise clearly:**
   - "You're on Cycle N. X tasks to build, Y builds pending review."
   - Or: "Cycle N is complete — ready for the next plan."
   - Flag any issues: stale In Progress tasks, strategy review due, orphaned branches.

4. **Suggest the next action:**
   - If tasks are In Review: "Run `review_submit` to accept/reject pending reviews."
   - If tasks are in Backlog: "Pick a task to build — use `/next-task` to start."
   - If all tasks are Done: "All tasks complete. Run `plan` to create the next cycle."
   - If strategy review is due: mention it before suggesting plan.

## Output format

Keep it concise. Lead with the status line, then a brief board summary, then the recommended next action.