npx claudepluginhub haabe/mycelium --plugin myceliumThis skill uses the workspace's default tool permissions.
Evaluate organizational design for fast flow. Source: Skelton & Pais (Team Topologies).
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.
Designs team topology using Team Topologies principles. Supports design, analyze, and evolve modes for organizational design, restructuring, or team evolution.
Maps stakeholder influence networks, designs team structures per Conway's Law, defines interface contracts (APIs, SLAs, decision rights), assesses maturity (DORA, CMMC). Useful for org design, restructures, stakeholder analysis.
Share bugs, ideas, or general feedback.
Evaluate organizational design for fast flow. Source: Skelton & Pais (Team Topologies).
For each team, classify:
For each team, assess:
Between each pair of collaborating teams:
Conway's Law (1968): "Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure." Note: it's communication structures, not org chart hierarchy — two teams in the same org with poor communication will still produce fragmented systems.
Inverse Conway Maneuver (James Lewis, popularized by Skelton & Pais): Deliberately design team communication structures to match the desired system architecture, rather than letting architecture drift to match existing teams.
When a team's cognitive load exceeds capacity, use fracture planes to identify the cleanest split point. The fracture plane that aligns with the most criteria wins:
| Fracture Plane | Description |
|---|---|
| Business domain | DDD bounded context boundary |
| Regulatory compliance | Different compliance requirements = different teams |
| Change cadence | Fast-moving vs stable components |
| Team location | Co-located vs distributed |
| Technology | Different tech stacks |
| User personas | Different user segments |
| Risk | High-risk vs low-risk components |
| Performance isolation | Components with different scaling/latency requirements |
Source: Skelton & Pais (Team Topologies, Chapter 6)
If the product has multiple domains or services:
When DORA metrics indicate capability gaps, use the DASA DevOps Competency Framework's 12 skill areas to identify which team skills need development (e.g., courage, teambuilding, continuous improvement, business value optimization).
Skelton's "Infrastructure for Agency" framing describes how organizations should provide boundaries that enable autonomy rather than control that restricts it. Mycelium implements bounded agency for AI agents using the same structural principles:
| Skelton concept | Mycelium mechanism |
|---|---|
| Boundaries that enable | Guardrails (BLOCK/REVIEW/NUDGE — constrain without micromanaging) |
| Shared state | Canvas (single source of truth all agents read/write) |
| Stable interfaces | Theory gates (predictable checkpoints with explicit pass/fail) |
| Aligned domains | Diamonds (scoped units of work with clear ownership) |
| Bounded workers | Fan-out agents (isolated worktrees, scoped mandate, report back) |
Agency without boundaries produces chaos; boundaries without agency produces bureaucracy. The target is the middle.
Source: Skelton (Infrastructure for Agency, 2025-2026)
.claude/canvas/team-shape.yml and .claude/canvas/bounded-contexts.yml with assessment results.### Team Shape Assessment entry to .claude/harness/decision-log.md with: team types identified, cognitive load findings, Conway alignment, recommendations. (MANDATORY per G-P4)