team-topologies
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or "reorg". Also trigger when reorganizing engineering teams, aligning team and service boundaries, splitting a monolith and deciding ownership, reducing cross-team handoffs, or designing an internal platform. Covers the four team types, three interaction modes, the inverse Conway maneuver, and fracture planes. For bounded contexts, see domain-driven-design. For dependency direction in code, see clean-architecture.
- Version
- 1.2.0
- License
- MIT
Pinned to revision 4f7124e6049e, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/team-topologies/SKILL.md
- skills/team-topologies/references/case-studies.md
- skills/team-topologies/references/cognitive-load.md
- skills/team-topologies/references/fracture-planes.md
- skills/team-topologies/references/interaction-modes.md
- skills/team-topologies/references/team-types.md
Every link opens the file at its source, pinned to the revision this page describes.