Team structure and organization design using Team Topologies and related methodologies.
| Skill | Purpose |
|---|---|
team-topologies |
Four fundamental team types and interaction modes |
cognitive-load-assessment |
Measure and manage team cognitive load |
inverse-conway |
Align architecture and team structure |
team-api-design |
Define team interfaces and contracts |
interaction-patterns |
Team interaction modes and evolution |
| Agent | Purpose |
|---|---|
team-architect |
Design team structures aligned with architecture |
team-health-assessor |
Evaluate team effectiveness and cognitive load |
| Skill | Purpose |
|---|---|
/team-structure |
Design team topology for an organization |
/cognitive-load |
Assess and optimize team cognitive load |
/plugin install team-design@claude-code-plugins/team-structure "e-commerce platform"
/team-structure "data platform" teams=5
/cognitive-load "payments team"
/cognitive-load depth=detailed
Invoke the team-architect agent to:
- Map current team structure
- Identify team type mismatches
- Plan team evolution
- Design interaction patterns
Four fundamental team types:
- Stream-aligned: Aligned to flow of work, end-to-end ownership
- Platform: Provide self-service internal products
- Enabling: Help teams overcome obstacles
- Complicated-subsystem: Handle complex technical domains
Based on cognitive load theory:
- Intrinsic: Inherent complexity of the domain
- Extraneous: Unnecessary complexity
- Germane: Learning new skills
Deliberately evolve team structure to achieve desired architecture:
- Architecture follows communication
- Change teams to change architecture
- Bounded contexts to team boundaries
Three core interaction modes:
- Collaboration: Working together closely
- X-as-a-Service: Consuming via API
- Facilitating: Helping other teams improve
enterprise-architecture- Architecture and bounded contextssystems-design- Platform engineering and architecturebusiness-analysis- Capability mapping
Based on "Team Topologies" by Matthew Skelton and Manuel Pais.