What are the four team types supported by this skill?

The skill supports the design of Stream-aligned teams, Platform teams, Enabling teams, and Complicated Subsystem teams.

What is the primary goal of the Team Topologies skill?

The primary goal is to help you design an organization that optimizes for the 'fast flow' of change while keeping the cognitive load on individual teams manageable.

Can this skill help identify if a team is overloaded?

Yes, it includes a cognitive load assessment framework that looks at domain complexity, technical friction, and coordination overhead to determine if a team's scope is too broad.

How does this skill address Conway's Law?

It provides strategies for the 'Inverse Conway Maneuver,' which involves intentionally designing your team structure to mirror the software architecture you want to achieve.

Team Topology Design

Name: Team Topology Design
Author: melodic-software

bymelodic-software

•

コラボレーションツール

Optimizes organizational design and team structures to align with software architecture using the Team Topologies framework.

The Team Topology Design skill provides specialized guidance for structuring engineering organizations to achieve fast flow and manage cognitive load. Based on the industry-standard methodology, it helps users implement the four fundamental team types and three interaction modes while applying the Inverse Conway Maneuver. This skill is essential for architects and leaders who need to align their team boundaries with their technical boundaries, ensuring that organizational communication patterns support rather than hinder the target software architecture.

主な機能

01Implementation guidance for Stream-aligned, Platform, Enabling, and Complicated Subsystem teams

02Cognitive load assessment tools to evaluate and balance team responsibilities

03Frameworks for defining Collaboration, X-as-a-Service, and Facilitating interaction modes

04Inverse Conway Maneuver strategies to drive architectural change through org design

05Heuristics for team sizing and evolutionary patterns for organizational growth

0612 GitHub stars

ユースケース

01Defining clear boundaries and 'Team APIs' during microservices migrations

02Reorganizing engineering departments to improve deployment frequency and lead time

03Scaling a startup from a single team to a multi-team department while maintaining flow

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add melodic-software/claude-code-plugins team-topology-design

For use in Claude.ai and ChatGPT

Download Skill