enterprise-plugins

Enterprise Team

Hire a whole company with one plugin.
75 specialized AI agents across Engineering, Product, Infrastructure, Data, Security, Marketing, Sales, Finance, Legal, and People.

---

The Problem with Generalist Agents

When you ask Claude Code to "build me a dashboard," it does its best. But Claude is trying to be everything at once: frontend developer, backend engineer, database architect, and UI designer. The result? Competent but generic work.

The real issue is context switching at scale. A generalist agent:

• Has to hold patterns for dozens of domains simultaneously
• Can't go deep on any single specialty
• Applies the same approach whether the task needs a security mindset or a marketing mindset
• Doesn't know when to ask for help from a different discipline

You end up with code that works but doesn't reflect what a dedicated specialist would produce. The API design a backend-focused engineer would craft. The component architecture a frontend specialist would build. The security hardening an AppSec engineer would insist on.

Skills help, but they're manual. You have to know which skill to invoke, when to switch contexts, and how to coordinate handoffs between different specialties. That cognitive load is on you.

A Different Approach

What if Claude Code could operate like an actual company?

The key insight: departments exist for a reason. Real organizations don't have one person doing everything. They have specialists who go deep, orchestrated by managers who route work to the right people.

Enterprise Team replicates this structure:

1. Department Orchestrators understand what their specialists do and route work accordingly
2. Specialists go deep on their domain with focused system prompts, tools, and patterns
3. Cross-functional routing means a single request can flow through multiple departments seamlessly

When you say "build me a settings page with dark mode," Enterprise Team doesn't just write code. The orchestrator recognizes this needs:

• Frontend Engineer for component architecture
• UI Designer for the visual system
• Backend Engineer if settings need persistence
• Security Engineer if settings include sensitive data

Each specialist contributes their expertise. The result is closer to what a real team would produce.

---

How It Works

Phase 1: Request Analysis

When you make a request, the orchestration layer analyzes it:

User: "Set up authentication with OAuth and add a login page"

The orchestrator identifies:

• Primary domain: Engineering (auth system + UI)
• Specialists needed: Backend Engineer (OAuth flow), Frontend Engineer (login page), Security Engineer (token handling)
• Sequence: Security review of approach → Backend implementation → Frontend integration

Phase 2: Specialist Dispatch

Each specialist receives:

• The original request with relevant context
• Their domain-specific system prompt (security mindset, performance focus, etc.)
• Access to tools appropriate for their role
• Awareness of what other specialists are handling

The Backend Engineer focuses on:

• OAuth provider integration
• Token refresh logic
• Session management
• API endpoint design

The Frontend Engineer focuses on:

• Login form UX
• Error state handling
• Loading states
• Redirect flows

The Security Engineer reviews:

• Token storage (not localStorage!)
• CSRF protection
• Rate limiting needs
• Secure cookie configuration

Phase 3: Integration

Work products from specialists are integrated with awareness of each other. The frontend engineer knows what endpoints the backend engineer created. The security engineer's requirements are applied to both.

When Departments Hand Off

Cross-functional work is common: