Menu
Coordination guidelines for leading a team of task-executing agents
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Restore claude/codex agents from a tmux-reboot snapshot after tmux-resurrect reopens their windows.
Snapshot running tmux claude/codex agents immediately before a reboot so their sessions can be restored afterward.
Commit changes, run git-test precommit checks, and fix failures. Use when asked to fix build, test, lint, typecheck, or precommit failures.
Running precommit checks and build validation. ALWAYS use after ANY code changes.
This skill should be used after completing any task, before returning control to the user. Always run this skill — it handles the case where there's nothing to do.
Workflow guidelines for team members executing tasks
| name | team-lead |
| description | Coordination guidelines for leading a team of task-executing agents |
Every task must result in exactly one commit. Before assigning the next task to a member, verify their previous work was committed.
Before assigning tasks in parallel, read each task's description to identify which files it modifies. If two tasks touch the same files, do NOT assign them simultaneously — either serialize them or instruct one member to use a worktree.
Use judgement on whether parallelism even makes sense. If most tasks touch overlapping files, it may be simpler to run them sequentially. If using worktrees, instruct the member to git worktree add into a peer directory before starting.
Whenever no team members are actively running, verify that all changes have been committed. There should be no uncommitted changes at rest.
