sprint-status

# 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/ap...