agent-teams
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team…
Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".
$ npx -y skills add rohitg00/pro-workflow --skill session-handoff --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/session-handoffContext preview
The summary Claude sees to decide when to auto-load this skill.
Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".
name: session-handoff description: Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off". user-invocable: true
Different from wrap-up. Wrap-up is a checklist for *you*. Handoff is a document written for the *next session*.
Use when saying "handoff", "continue later", "pass to next session", "session transfer", or ending a session and wanting to resume smoothly.
1. Gather current state from git. 2. List completed, in-progress, and pending work. 3. Note key decisions made and their reasoning. 4. Capture any learnings from this session. 5. Generate a resume command for the next session.
git status git diff --stat git log --oneline -5 git branch --show-current
# Session Handoff — [date] [time] ## Status - **Branch**: feature/xyz - **Commits this session**: 3 - **Uncommitted changes**: 2 files modified - **Tests**: passing / failing / not run ## What's Done - [completed task 1] - [completed task 2] ## What's In Progress - [current task with context on where you stopped] - [file:line that needs attention next] ## What's Pending - [next task that hasn't been started] - [blocked items with reason] ## Key Decisions Made - [decision 1 and why] - [decision 2 and why] ## Learnings Captured - [Category] Rule (from this session) ## Files Touched - `path/to/file1.ts` — [what changed] - `path/to/file2.ts` — [what changed] ## Gotchas for Next Session - [thing that tripped you up] - [non-obvious behavior discovered] ## Resume Command > Continue working on [branch]. [1-2 sentence context]. Next step: [specific action].
Claude Code learns from your corrections: self-correcting memory that compounds over 50+ sessions. Context engineering, parallel worktrees, agent teams, and 17 battle-tested skills.
Repo: rohitg00/pro-workflow
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team…
Auto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change…
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never…
Smart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual…
Master the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to…