Team Topology
@webframp/team-topologyv2026.07.18.1
01README
Agent-guided team topology and value stream mapping model. Captures teams (type, cognitive load, domains), interactions (modes, health), system ownership, and value stream flows as versioned snapshots. Designed for incremental discovery through structured conversations — the agent interviews, the model persists.
Draws on Team Topologies (Skelton & Pais), Conway's Law, Westrum organizational typology, GROWS method tracer bullets, and Ruth Malan's evolutionary architecture thinking.
02Release Notes
2026.07.18.1
Added: An upgrades array entry (no-op) to mod.ts for proper typeVersion tracking on existing instances. No schema or behavior changes.
03Models
@webframp/team-topologyv2026.07.18.1team-topology/mod.ts
Global Arguments
| Argument | Type | Description |
|---|---|---|
| organizationContext | string | Brief description of the organization, its size, and primary business |
| scope | string | Scope of this topology instance: 'full' org, a division name, or a product area |
fn discover_topology(teams: array, interactions: array, systemDependencies: array, notes?: string)
Discover and record team topology through structured conversation.
AGENT GUIDANCE:
You are mapping an organization's team structure using Team Topologies
concepts. Guide the conversation through these phases:
1. TEAM INVENTORY
Ask: "What teams exist in this area? For each team, what is their
primary responsibility?" List them out. Don't worry about classification
yet — just get names and purposes.
2. TEAM TYPE CLASSIFICATION
For each team, determine its fundamental type:
- str
| Argument | Type | Description |
|---|---|---|
| teams | array | Teams discovered through conversation |
| interactions | array | Interactions between teams |
| systemDependencies | array | System-level dependencies that cross team boundaries |
| notes? | string | Context about this discovery session |
fn map_flow(streams: array)
Map value streams through structured conversation.
AGENT GUIDANCE:
You are mapping how work flows through the organization end-to-end.
Use a tracer-bullet approach: pick ONE flow first, map it completely,
then add more.
1. STREAM IDENTIFICATION
Ask: "What are the main flows of work in this area? Think about it
from trigger to customer outcome. Examples:
- Feature request → shipped feature
- Incident → resolution
- New hire → productive engineer
- Security finding → remediate
| Argument | Type | Description |
|---|---|---|
| streams | array | Value streams mapped through conversation |
fn record_assessment(findings: array, summary: string)
Record an assessment of the current topology and flows.
AGENT GUIDANCE:
You have read the topology and flows resources. Now analyze them for
problems and opportunities. Look for these categories of findings:
1. COGNITIVE LOAD
- Teams where intrinsic + extraneous exceeds capacity
- Teams owning too many domains or systems
- Platform teams that are actually doing stream-aligned work
2. CONWAY'S LAW MISMATCHES
- System dependencies that don't match team interaction patterns
- Tea
| Argument | Type | Description |
|---|---|---|
| findings | array | Findings from analyzing the topology and flows |
| summary | string | Brief narrative summary of the assessment |
Resources
topology(infinite)— Snapshot of team structure, interactions, and system ownership
flows(infinite)— Value stream maps with step-level metrics
assessment(infinite)— Agent-produced findings about the topology (load, mismatches, friction)
04Previous Versions
2026.06.29.1
05Stats
A
100 / 100
Downloads
2
Archive size
17.2 KB
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License declared1/1earned
- Verified public repository2/2earned
06Platforms
07Labels