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.

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.

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.

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.