# Sprint Status

Track parallel work sessions and prevent confusion across multiple Claude Code instances.

- Repository: https://github.com/rohitg00/pro-workflow (2940 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-09-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rohitg00/pro-workflow --skill sprint-status -g -a claude-code -y`
Codex: `npx skills add rohitg00/pro-workflow --skill sprint-status -g -a codex -y`
Cursor: `npx skills add rohitg00/pro-workflow --skill sprint-status -g -a cursor -y`
Gemini CLI: `npx skills add rohitg00/pro-workflow --skill sprint-status -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rohitg00/pro-workflow`

## Description

Track parallel work sessions and prevent confusion across multiple Claude Code instances. Every major step ends with a status line. Every question re-states project, branch, and task.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Sprint Status

When running multiple Claude Code sessions in parallel, confusion is the enemy. This skill ensures every session identifies itself and every step reports its state.

## Session Identification

Every response that involves a decision, plan, or significant action starts with orientation:

```text
SESSION: my-app | branch: feat/auth | task: Add JWT refresh tokens
```

This takes one line. It costs almost nothing. It prevents the user from applying feedback to the wrong session.

### Detecting Parallel Sessions

Check for sibling Claude Code processes:

```bash
pgrep -af "claude" | grep -v "$$" | head -5
```

Or check for active worktrees:

```bash
git worktree list 2>/dev/null
```

Or look for session markers (written by session-start.js / session-end.js):

```bash
ls $TMPDIR/pro-workflow/sessions/ 2>/dev/null | tail -5
```

If multiple sessions are detected, always include the session identification header. If only one session is running, include it at task boundaries and before presenting options.

## Status Lines

End every major step with exactly one status line. No ambiguity.

### STATUS: COMPLETE

All work for the current step is done. Ready to commit, merge, or move to the next task.

```text
STATUS: COMPLETE
  Changed: src/auth/refresh.ts, src/auth/refresh.test.ts
  Tests: 14 pass, 0 fail
  Ready to commit.
```

### STATUS: COMPLETE_WITH_NOTES

Done, but flagging something the user should know about.

```text
STATUS: COMPLETE_WITH_NOTES
  Changed: src/api/upload.ts
  Tests: 8 pass, 0 fail
  Notes:
    - Upload size limit is hardcoded to 10MB, should be configurable
    - No rate limiting on this endpoint yet (separate task)
```

Notes are for things that work but could be better. Not blockers, observations.

### STATUS: BLOCKED

Cannot proceed without user input or an external dependency.

The rest: https://github.com/rohitg00/pro-workflow/blob/HEAD/skills/sprint-status/SKILL.md