Team Topologies
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies".
Use Edge to load the skill team-topologies from wondelai/skills for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
2 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
What it does
- Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies".
- Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or "reorg".
- Also trigger when reorganizing engineering teams, aligning team and service boundaries, splitting a monolith and deciding ownership, reducing cross-team handoffs, or designing an internal platform.
- Covers the four team types, three interaction modes, the inverse Conway maneuver, and fracture planes.
- For bounded contexts, see domain-driven-design.
- For dependency direction in code, see clean-architecture.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Team Topologies.
Related skills
Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corru
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a m
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hex
Design or review backend domain and dependency boundaries using DDD, Clean Architecture, and ports/adapters. Use for aggregate modeling, bounded contexts, use-case isolation, or architecture refactoring; not routine CRUD
Domain-Driven Design tactical patterns for .NET applications. Covers aggregates, aggregate roots, value objects, domain events, domain services, strongly-typed IDs, and repository patterns for aggregate persistence. Load
No evidence record yet
No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Static scans check the code, not how well the skill works.
State definitionsSelect the Files tab to load SKILL.md.
Skill details
Security scansReviewed
2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.
Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.
Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
- Edge static checks
- Pass · 0 counted findings · 2026-11-17
- Edge committed-secret checks
- Pass · 0 counted findings · 2026-11-17
Creator, source & licencewondelai
From the wondelai public repository. Edge did not write or edit this skill.
- Repository
- wondelai/skills
- Skill file
- View source at revision
- Revision
- c172996495bed0fcd26896a9416b2093fd7073f0
- Package hash
- sha256:aae67584a79144f3d9fc3f5ce97c3f65d0add258430f5af29f9fe553f8dac11f
- Licence
- MIT
- Description
- Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or "reorg". Also trigger when reorganizing engineering teams, aligning team and service boundaries, splitting a monolith and deciding ownership, reducing cross-team handoffs, or designing an internal platform. Covers the four team types, three interaction modes, the inverse Conway maneuver, and fracture planes. For bounded contexts, see domain-driven-design. For dependency direction in code, see clean-architecture.
Quoted from the skill’s own description
Read skill files6 files
6 files, 78.6 KB at revision c172996495be.
Questions about Team Topologies
What does Team Topologies do?
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Published by wondelai (wondelai/skills).
Is Team Topologies safe to use?
Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 17, 2026). The Evidence tab shows the scan.
How do I use Team Topologies in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.