Sprint Status

If you're running multiple Claude Code sessions at once, this keeps you from losing your mind. Every response that involves a decision starts with a session header (project, branch, task). Every major step ends with a status line: COMPLETE, COMPLETE_WITH_NOTES, BLOCKED, or NEEDS_INFO. The NEEDS_INFO status always includes a sensible default so you can say "go with it" without switching context. It's not glamorous, but it prevents the very real problem of giving feedback to the wrong session or forgetting which branch is blocked on what. Especially useful when you're stacking features or running tests in parallel with implementation.

skills.sh installs: 159
GitHub stars: 2.9K
last updated: Jun 8, 2026

View on GitHub

Install

$ npx -y skills add rohitg00/pro-workflow --skill sprint-status --agent claude-code

Installs into .claude/skills of the current project.

Files

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:

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:

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

Or check for active worktrees:

git worktree list 2>/dev/null

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

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.