Machine level squad (instead of repo) - best practices

[diberry]

I need 2 squads at the machine level: 1) Azure developer/devops squad 2) Azure docs squad.

Would this be a single squad and I just fire/retire squad members for the use case?

[diberry]

Changed this into a feature request via issue.

[bradygaster]

This is a great use case! A few approaches:

1. Global squad (squad init --global) — gives you a machine-level team that works across repos. You'd have one squad with members that span both Azure dev/devops and Azure docs concerns.

2. Per-repo squads — more isolation but more setup. Each repo gets a team tailored to its domain.

3. Hybrid — global squad for cross-cutting concerns (devops, CI, shared tooling), repo-level squads for domain-specific work (docs vs. code).

For your case (Azure dev/devops + Azure docs), I'd lean toward option 1 with a well-structured routing table. You don't need to fire/retire members — just route work to the right agents based on which repo or task type you're working on.

We're actively thinking about cross-repo orchestration patterns. Would love to hear more about your specific workflow as we design this.