cx-team-topology

SKILLWorkflowcommunity
v0.0.0rulebase-coMITUpdated 1mo agoSource →

Use to decide how to split a growing support organisation — by product, segment, channel, or complexity — and when pods beat shared queues, accounting for coordination cost. Trigger for "team topology", "how should we split the team", "organise support by product or queue", "when to create pods", "s

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
1Repo stars
1Clients
1Formats
1mo agoLast update
Skill
Authorrulebase-co
Version0.0.0
LicenseMIT
CategoryWorkflow
Formatsskill.md
PromptNot published
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

Use to decide how to split a growing support organisation — by product, segment, channel, or complexity — and when pods beat shared queues, accounting for coordination cost. Trigger for "team topology", "how should we split the team", "organise support by product or queue", "when to create pods", "support team structure", growing headcount, or coordination overhead between sites.

Keywords
skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.