When should I use Collaboration mode instead of X-as-a-Service?

Collaboration is best for discovery, innovation, or complex integration phases where high-bandwidth communication is needed. It should be time-boxed and eventually evolve into a more sustainable X-as-a-Service model.

Can this skill help with platform engineering initiatives?

Yes, it specifically outlines how Platform teams should provide capabilities as a service to Stream-aligned teams, emphasizing self-service documentation and minimal back-channel coordination.

How does this skill help identify team anti-patterns?

The skill provides specific criteria to detect issues like 'permanent collaboration,' where teams never become independent, or 'facilitation without exit,' where an enabling team becomes a permanent dependency.

What are the three core interaction modes supported?

This skill focuses on the three official Team Topologies modes: Collaboration (working closely on shared goals), X-as-a-Service (consuming capabilities via API), and Facilitating (helping another team improve).

Team Topologies Interaction Patterns

Name: Team Topologies Interaction Patterns
Author: melodic-software

bymelodic-software

•

コラボレーションツール

Defines and evolves team interaction modes using Team Topologies principles to optimize organizational flow and communication.

The Team Interaction Patterns skill brings structured organizational design into your development environment by implementing the core interaction modes from Skelton and Pais's Team Topologies. It guides teams through selecting and transitioning between Collaboration, X-as-a-Service, and Facilitating modes, ensuring that team boundaries are respected and dependencies are managed effectively. By using a documentation-first approach and a clear selection matrix, this skill helps prevent common organizational anti-patterns like permanent collaboration or unsustainable dependencies, fostering a more scalable and efficient engineering culture.

主な機能

01Standardized definitions for Collaboration, X-as-a-Service, and Facilitating modes

02Guided interaction evolution patterns for maturing team relationships

03Anti-pattern detection to identify hidden bottlenecks and lack of self-service

04Interaction mode selection matrix based on project phase and team type

05Documentation-first workflow integrated with Team Topologies concepts

065 GitHub stars

ユースケース

01Structuring the relationship between a new Platform team and existing Stream-aligned teams

02Setting clear exit criteria for an Enabling team during a technology rollout

03Evolving a complex integration from high-bandwidth collaboration to a stable API-driven service

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add melodic-software/claude-code-plugins interaction-patterns

For use in Claude.ai and ChatGPT

Download Skill