Menu
Standard collaboration protocol for all squad agents
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | agent-collaboration |
| description | Standard collaboration protocol for all squad agents |
| domain | team-workflow |
| confidence | high |
| source | extracted from 11 agent charters during reskill optimization |
All squad agents follow the same collaboration protocol. This was previously duplicated in every charter (~650 bytes each). Now injected via spawn prompt; this skill documents the canonical protocol for reference.
git rev-parse --show-toplevel to find the repo root, or use the TEAM ROOT from the spawn prompt.squad/ paths resolve relative to the repo root — never assume CWD is root.squad/decisions.md for team decisions that affect you.squad/decisions/inbox/{agent}-{brief-slug}.mddecisions.md (agents don't edit decisions.md directly)git add specific files (never blanket git add .)git commit with a clear message describing what and whyCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> as a trailergit add . — be explicit about staged filesdecisions.md directly — use the inboxKeep prompt template behavior consistent across CLI and cron by reusing one resolver pipeline.
Prevent gateway projects from taking compile-time dependencies on extension assemblies.
Prevent refresh regressions by paging conversation history from newest entries
Fast session investigation using BotNexus Probe CLI (preferred) or Python helper scripts. Use when debugging session state, resuming issues, message routing, checking what sessions exist for an agent, reviewing gateway logs for errors, or correlating events across logs/sessions/traces.
Use when creating GitHub issues, opening worktrees, naming branches, or managing the full lifecycle of a work item on sytone/botnexus. Enforces consistent issue titles, label application, worktree creation, branch naming, PR linking, and cleanup. Triggers on: "create an issue", "open a worktree", "start work on", "file a bug", "add an issue for", "new feature issue", "track this as an issue".
Design spec lifecycle management — creating, reviewing, transitioning, and archiving specs in docs/planning/