Coordinating Multiple Team Members

[bigfoote-joinin]

Is there anything in this set of skills for team members to coordinate working on a shared git repository of issues? Obviously there is the assignee field or labels that could be used, but I didn't want to invent my own solution if there was already something here that I was missing. And is this just a special case of a single person dispatching multiple agents to work on issues in parallel, where they need to indicate having started work on something so another one doesn't duplicate the effort?

[hades200082]

Multi-developer orchestration is the biggest issue I have with AI development right now.

There's just no way for one AI session to know what others are doing on other machines.

Some thoughts I've had based on research into this...

1. Nothing is going to stop merge conflicts - you can have your team explicitly prompt the AI to use worktrees or separate branches, raise PRs, etc. but if you have multiple people using AI on the same repo you're going to get merge conflicts - and given the nature of the way AI writes code, they are going to be deep and complex conflicts.
2. For a single developer, a global orchestration agent that spins up separate sessions for each task (paperclip and hermes come to mind as close runners) where the orchestrator can manage the blockers, etc. and make sure things are done in order... this could work for a solo dev.
3. For a team, each team member would need to be running their own orchestrator so it's not so good.
4. If you use an orchestrator, there's little need for a team since the orchestrator could theoretically have rules on what to do. Auto-triage new issues... auto-implement any that are ready-for-agent, etc. This is something I'm researching further currently

Sorry for the jumble of thoughts - hopefully some of it's helpful