What problem does it solve? Engineering organizations suffer from slow delivery caused by poorly drawn team boundaries, unclear team charters, and cross-team dependencies that turn every feature into a multi-team project. This Skill applies Skelton and Pais's Team Topologies framework to design team structures that align with Conway's law, respect cognitive load limits, and optimize for fast flow of change. ## Core Features & Use Cases - Four Team Types Classification: Categorize every team as stream-aligned, enabling, complicated-subsystem, or platform, with conversion procedures for component, ops, QA, and architecture teams. - Three Interaction Modes: Declare collaboration, X-as-a-Service, or facilitating modes per team pair, with time-boxing rules, interaction contracts, and evolution triggers. - Cognitive Load Management: Assess team load with surveys and domain-counting heuristics, and publish team APIs so other teams can interact without meetings. - Fracture Planes for Monolith Splits: Split software along business domain, regulatory, cadence, and other seams so each piece fits one team's ownership. - Use Case: A scale-up where every feature touches five teams uses this Skill to map streams of change, form cross-functional stream-aligned teams, convert the ops ticket queue into a platform-as-product team, and cut lead time from nine weeks to under three. ## Quick Start Ask the AI to assess your current engineering org structure using Team Topologies and recommend a target team design with declared interaction modes.
