From team-design
Designs team topology using Team Topologies principles. Supports design, analyze, and evolve modes for organizational design, restructuring, or team evolution.
npx claudepluginhub melodic-software/claude-code-plugins --plugin team-designThis skill is limited to using the following tools:
Design team topology for an organization using Team Topologies principles.
Guides organizational design using Team Topologies: four team types (stream-aligned, platform, enabling, complicated subsystem), interaction modes, cognitive load, Inverse Conway Maneuver. For aligning teams with architecture.
Guides team structure design using Team Topologies' four fundamental team types: stream-aligned, platform, enabling, and complicated subsystem teams.
Maps stakeholder influence networks, designs team structures via Conway's Law, defines interface contracts (APIs/SLAs/decision rights), assesses maturity (DORA/CMMC). For org design, restructures, stakeholder mapping.
Share bugs, ideas, or general feedback.
Design team topology for an organization using Team Topologies principles.
/team-structure "e-commerce platform"
/team-structure "data platform" teams=5
/team-structure "current org" mode=analyze
/team-structure "microservices migration" mode=evolve
| Argument | Required | Description |
|---|---|---|
context | Yes | Organization, product, or system to design teams for |
teams | No | Target number of teams (helps constrain design) |
mode | No | design (default), analyze, or evolve |
Create a new team structure from scratch:
Evaluate an existing team structure:
Plan evolution from current to target state:
Load required skills for team design guidance:
Skills to load:
- team-topologies (team type definitions)
- inverse-conway (architecture alignment)
- cognitive-load-assessment (load analysis)
- interaction-patterns (interaction modes)
- team-api-design (team interfaces)
Based on mode, gather relevant information:
For Design Mode:
For Analyze Mode:
For Evolve Mode:
Delegate to the team-architect agent for comprehensive analysis:
Task: Design team structure for {context}
Mode: {mode}
Constraints: {teams if specified}
Provide:
- Team type recommendations
- Bounded context mapping
- Interaction patterns
- Cognitive load assessment
- Evolution roadmap (if evolve mode)
Present the team structure design with:
# Team Structure: {context}
## Summary
{One paragraph overview of recommended structure}
## Team Structure Diagram
```text
{ASCII diagram showing teams and relationships}
| Team | Mission | Bounded Context |
|---|---|---|
| {Name} | {Mission} | {Context} |
| Team | Mission | Capabilities |
|---|---|---|
| {Name} | {Mission} | {What they provide} |
| Team | Focus | Current Engagements |
|---|---|---|
| {Name} | {Focus} | {Who they're helping} |
| Team | Specialist Area | Interface |
|---|---|---|
| {Name} | {Specialization} | {How others consume} |
{ASCII diagram showing interaction modes}
| From | To | Mode | Notes |
|---|---|---|---|
| {Team} | {Team} | {Mode} | {Details} |
| Team | Load Score | Status |
|---|---|---|
| {Team} | {X/75} | {🟢🟡🔴} |
| Risk | Impact | Mitigation |
|---|---|---|
| {Risk} | {Impact} | {Strategy} |
/team-structure "e-commerce platform"
Output highlights:
/team-structure "current org" mode=analyze
Output highlights:
/team-structure "monolith to microservices" mode=evolve
Output highlights:
/cognitive-load - Deep dive on cognitive load for a team/wardley-map - Strategic analysis for team positioningteam-topologies - Team type definitions and patternsinverse-conway - Architecture-team alignmentcognitive-load-assessment - Load measurement methodologyinteraction-patterns - Interaction mode guidanceLast Updated: 2025-12-26