Skip to main content
command CX Codex

sprint-status — Claude Code command: session overview

sprint-status is a Claude Code command that summarizes active sessions and branches. Run it to resume work or check parallel sessions.

MIT ★ 2,966 updated 2026-09-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow
Open on GitHub

What sprint-status does

The command checks for Claude Code processes, Git worktrees, and entries in the session directory. It reports the current project, branch, task, and status; when it finds several sessions, it assembles a sprint-wide view. Use it before changing terminal tabs or when you need to pick up where you left off.

Statuses show whether work is ready to commit or merge, has notes, is blocked, or needs more context. Session discovery uses pgrep, git worktree list, and a listing of $TMPDIR/pro-workflow/sessions/. A session that these checks do not find will not appear in the report.

What it helps with

  • check which Claude Code sessions are active
  • compare branches and tasks across parallel work
  • spot a blocked session or one waiting for context
  • recover your place after stepping away

Example prompts for the agent

  • Run /sprint-status and show me where I left off.
  • Use /sprint-status to list active sessions and their branch status.
  • Before I switch terminal tabs, run /sprint-status.

How to install sprint-status

1Plugin marketplace

/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow

2Manually: put the files in place

.claude/commands/sprint-status.md

Call it with /sprint-status. For all projects use ~/.claude/commands/

Questions about sprint-status

How do I install sprint-status in Claude Code?

Run /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow. Invoke the command with /sprint-status.

What does sprint-status do?

It checks for active Claude Code sessions and reports the current task status. When it detects multiple sessions, it creates a combined view across branches.

What do the sprint-status labels mean?

COMPLETE means work is ready to commit or merge; COMPLETE_WITH_NOTES marks finished work with observations. BLOCKED means progress depends on input or an external dependency, while NEEDS_INFO means context is missing.

Source text

sprint-status.md · MIT
---
description: Show status across active parallel sessions
---

# /sprint-status - Parallel Session Tracker

Report status across all active Claude Code sessions.

## Process

1. **Detect active sessions:**
   ```bash
   pgrep -af "claude" | grep -v "$$" | head -10
   git worktree list 2>/dev/null
   ls $TMPDIR/pro-workflow/sessions/ 2>/dev/null | tail -5
   ```

2. **Report current session:**
   ```text
   SESSION: <project> | branch: <branch> | task: <current task>
   STATUS: COMPLETE | COMPLETE_WITH_NOTES | BLOCKED | NEEDS_INFO
   ```

3. **Compile sprint view** (if multiple sessions detected):
   ```text
   SPRINT STATUS
     Session 1: feat/auth       STATUS: COMPLETE         (ready to merge)
     Session 2: feat/upload     STATUS: BLOCKED          (waiting on S3 creds)
     Session 3: fix/login-bug   STATUS: COMPLETE_WITH_NOTES (needs perf review)
   ```

## Status Definitions

| Status | Meaning |
|--------|---------|
| `COMPLETE` | Done, ready to commit or merge |
| `COMPLETE_WITH_NOTES` | Done, but flagging observations |
| `BLOCKED` | Cannot proceed, needs input or external dep |
| `NEEDS_INFO` | Missing context, asking before guessing |

## When to Use

- Before switching between terminal tabs/sessions
- At the end of a work phase
- When asking "where was I?"
- To orient after being away

---

**Trigger:** Use when running parallel sessions, resuming work, or wanting a quick snapshot of progress across branches.

© Rohit Ghumare · MIT · rohitg00/pro-workflow

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set83

The whole set →
list list displays stored patterns and rules from the pro-workflow database by recency, category, or project. CX Codex +1 ★ 2,966repo stars context-discipline The context-discipline rule sets limits for file reads, tool calls, and test-driven edits. It helps keep Claude Code from reopening unchanged files or polishing code after tests pass. CX Codex +1 ★ 2,966repo stars communication-style communication-style sets how Claude replies: short, no openers or praise, code before prose. Useful when agent answers drown in politeness. CX Codex +1 ★ 2,966repo stars search Runs full-text keyword searches across the pro-workflow learnings database. Helps recall previous mistakes and project rules while coding. CX Codex +1 ★ 2,966repo stars deslop The /deslop command cleans the current branch of unnecessary code added by AI: obvious comments, defensive try/catch blocks, one-off abstractions, and docstrings on unchanged functions. CX Codex +1 ★ 2,966repo stars learn-rule learn-rule extracts session mistakes into one-line rules and saves them to your project memory after explicit confirmation. CX Codex +1 ★ 2,966repo stars wrap-up The wrap-up skill audits code changes, runs quality checks, and records what to pick up next. Use it when you are about to end a coding session. CX Codex +1 ★ 2,966repo stars incremental-verify incremental-verify keeps the agent on one failing test at a time: the smallest change that passes it, then a commit, before the next behavior starts. CX Codex +1 ★ 2,966repo stars

Project sponsors

Companies that keep this analytics open