- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rohitg00/pro-workflow --skill sprint-status -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rohitg00/pro-workflow --skill sprint-status -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rohitg00/pro-workflow --skill sprint-status -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rohitg00/pro-workflow --skill sprint-status -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/rohitg00/pro-workflow/tree/HEAD/skills/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.
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.
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.
End every major step with exactly one status line. No ambiguity.
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.
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.
Cannot proceed without user input or an external dependency.
STATUS: BLOCKED
Blocker: Need database migration approved before writing the ORM layer
Waiting on: DBA approval for schema change in migrations/0042_add_tokens.sql
Can continue: Nothing else in this task until unblocked
Missing context to make a good decision. Asking before guessing.
STATUS: NEEDS_INFO
Question: Should refresh tokens expire after 7 days or 30 days?
Impact: Changes token cleanup job schedule and storage requirements
Default if no preference: 7 days (more secure, standard practice)
Always provide a sensible default so the user can say "go with the default" without context-switching into the decision.
Session 1: feat/auth → implementing JWT refresh
Session 2: feat/auth-tests → writing test suite for auth module
Both sessions work on the same feature but don't touch the same files. Session 2 can start writing tests against the interface before Session 1 finishes the implementation.
Session 1: feat/upload → file upload endpoint
Session 2: feat/billing → billing webhook handler
Session 3: fix/login-bug → login redirect fix
Completely independent. Merge order doesn't matter.
Session 1: feat/base-types → shared type definitions (must merge first)
Session 2: feat/api → API layer (depends on Session 1)
Session 3: feat/ui → UI layer (depends on Session 1)
Session 1 merges first. Sessions 2 and 3 rebase after. Flag the dependency in every status update.
When the user asks for status across sessions, compile a sprint view:
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 (works, needs perf review)
## Sprint Status
Every decision and plan starts with: SESSION: project | branch | task
End major steps with STATUS: COMPLETE | COMPLETE_WITH_NOTES | BLOCKED | NEEDS_INFO
NEEDS_INFO always includes a sensible default.
When parallel sessions are detected, always include session headers.
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.
---name: sprint-statusdescription: Track parallel work sessions and prevent confusion across multiple Claude Code instances. Every major step…---# skills/sprint-status/SKILL.mdFAQ
게시자에게서 skills/sprint-status/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/rohitg00/pro-workflow에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.