← ClaudeAtlas

team-topologieslisted

Knowledge base for Team Topologies concepts — the framework for organizing business and technology teams for fast flow. Use this skill whenever the user asks about: team types (stream-aligned, platform, enabling, complicated subsystem), team interaction modes (collaboration, X-as-a-Service, facilitation), cognitive load management, Thinnest Viable Platform (TVP), Conway's Law in relation to org design, or any question about how software delivery teams should be structured, named, or coordinated. Also use when another skill needs Team Topologies vocabulary to reason about org design, team responsibilities, or team dependencies.
azborgonovo/ai-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill azborgonovo/ai-skills
# Team Topologies Knowledge Base Team Topologies is an approach to designing team-of-teams organizations for fast flow of value. It provides a shared vocabulary and practical patterns for how to structure, name, and evolve software delivery teams at scale. The central insight: organizational design is not a one-time event. Teams and their interactions must evolve continuously as products, architectures, and business needs change. ## Four Fundamental Team Types Every team in the organization should map to exactly one of these types. Hybrids create confusion and slow delivery. ### 1. Stream-aligned team The primary team type. Delivers direct, continuous value to customers aligned to a business domain or value stream. Owns outcomes end-to-end — no handoffs to other teams to complete delivery. - Long-lived, stable membership - Full responsibility for the product/service lifecycle - Should be the most common team type in the organization - All other team types exist to serve or support stream-aligned teams ### 2. Platform team Creates and operates an internal platform — a curated set of services, tools, and APIs — that reduces cognitive load on stream-aligned teams. The platform is treated as a product with its own roadmap and customers (the stream-aligned teams). - Exposes capabilities via APIs and self-service interfaces - Avoids building bespoke solutions for individual consumers - Success metric: stream-aligned teams move faster because of the platform, not in spite