team-topologies

Score engineering team structures against Team Topologies principles.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill team-topologies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-topologies
Source: https://github.com/fsolla/teqo/tree/main/.agents/skills/team-topologies
Command: npx skills add https://github.com/fsolla/teqo --skill team-topologies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses organizational friction, slow delivery, and architectural misalignment by applying the Team Topologies framework to structure engineering teams for fast, sustainable flow.

Core Features & Use Cases

  • Org Design Scoring: Evaluate existing team structures against Conway's Law and cognitive load heuristics.
  • Interaction Modeling: Define explicit interaction modes (Collaboration, X-as-a-Service, Facilitating) to eliminate coordination bottlenecks.
  • Fracture Plane Analysis: Identify natural seams in software to split monoliths into team-owned, manageable domains.
  • Use Case: Use this Skill to reorganize a struggling engineering department by identifying which teams are overloaded, defining clear team APIs, and establishing a platform-as-a-product strategy.

Quick Start

Analyze the current engineering team structure and provide a score based on the Team Topologies principles.

Frequently Asked Questions about team-topologies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce cognitive load and engineering bottlenecks during an organizational restructure?

Apply Team Topologies principles to structure high-performing engineering teams by identifying overloaded teams, managing cognitive load, and defining explicit interaction modes like Collaboration, X-as-a-Service, or Facilitating to eliminate coordination bottlenecks.

How to split a monolith into manageable domains using fracture plane analysis?

Split a monolith by applying fracture plane analysis to identify natural seams in the software, dividing the architecture into team-owned, manageable domains using domain-driven team allocation principles.

What are the best interaction modes for platform engineering teams to optimize software delivery flow?

Define explicit interaction modes including Collaboration, X-as-a-Service, and Facilitating to eliminate coordination bottlenecks and establish a platform-as-a-product strategy for fast, sustainable flow.

Does this approach to team organization design work for aligning engineering teams with system architecture?

Yes, this approach works by applying Conway's Law, evaluating team structures against cognitive load heuristics, and optimizing organizational communication paths to resolve architectural misalignment and slow delivery.

Why does my engineering department struggle with slow delivery and architectural misalignment despite having clear teams?

Slow delivery and architectural misalignment stem from team structures violating Conway's Law or exceeding cognitive load limits. Scoring the organization against Team Topologies principles reveals overloaded teams and unclear team APIs causing friction.

Can I evaluate my current engineering team structures and score them against Team Topologies principles?

Yes, you can analyze your current engineering team structure and receive a score based on Team Topologies principles, evaluating alignment with cognitive load management and Conway's Law heuristics.