Orchestrate full enterprise workflows by deploying 75 specialized AI agents across engineering, product, infrastructure, data, security, marketing, sales, finance, legal, and HR. Auto-routes tasks to domain experts, executes multi-agent pipelines with pre-built runbooks, handoff templates, QA gates, and escalations for end-to-end automation.
Manages sales cycles, negotiates deals, closes revenue. Expert in enterprise sales and relationship building.
General ledger, journal entries, reconciliations. Month-end close, accruals, financial statements.
Builds APIs, servers, and database integrations. Expert in Node.js, Python, PostgreSQL, REST, GraphQL.
Smart contracts, DeFi protocols, Web3 integration. Solidity, Ethereum, Layer 2s, wallet integration.
Brand strategy, positioning, visual identity. Brand guidelines, messaging frameworks, market positioning.
Routes data requests to the correct specialist based on task type: pipelines, analytics, machine learning, or quality assurance. Covers ETL, warehousing, dashboards, ML models, and test automation. Triggers: data pipeline, etl, data warehouse, analytics, dashboard, metrics, kpi, testing, test automation, qa, quality assurance, ci/cd testing, data science, machine learning, sql, dbt, airflow, spark.
Routes engineering requests to the correct specialist based on technology domain, task type, and stack involved. Covers backend, frontend, mobile, fullstack, embedded, blockchain, ML/AI, QA, architecture, and technical documentation. Triggers: build feature, write code, implement, develop, api, component, mobile app, ios, android, react, vue, node, python, smart contract, machine learning, system design, testing, QA, documentation, architecture, deploy, CI/CD, database, microservices.
Routes finance requests to the correct specialist: financial modeling, accounting, controlling, or corporate development. Covers budgets, forecasts, journal entries, M&A, and valuations. Triggers: financial model, forecast, budget, accounting, journal entry, reconciliation, financial statements, audit, M&A, acquisition, due diligence, valuation, revenue, cash flow, P&L, balance sheet.
Structured templates for agent-to-agent communication and quality gates. Use when work flows between agents/departments. Triggers: handoff, hand off, pass to, route to, transfer, quality gate, QA review, escalate, sprint boundary, incident, phase gate.
Routes infrastructure requests to the correct specialist based on domain: CI/CD, containers, cloud, databases, monitoring, reliability, and systems admin. Triggers: docker, kubernetes, terraform, ci/cd, github actions, deploy, railway, vercel, aws, database, postgresql, supabase, monitoring, alerting, incident, slo, reliability, nginx, ssl, dns, server, linux, networking.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Hire a whole company with one plugin.
75 specialized AI agents across Engineering, Product, Infrastructure, Data, Security, Marketing, Sales, Finance, Legal, and People.
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:
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.
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:
When you say "build me a settings page with dark mode," Enterprise Team doesn't just write code. The orchestrator recognizes this needs:
Each specialist contributes their expertise. The result is closer to what a real team would produce.
When you make a request, the orchestration layer analyzes it:
User: "Set up authentication with OAuth and add a login page"
The orchestrator identifies:
Each specialist receives:
The Backend Engineer focuses on:
The Frontend Engineer focuses on:
The Security Engineer reviews:
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.
Cross-functional work is common:
npx claudepluginhub chipagosfinest/enterprise-team --plugin enterprise-teamLean agent skills for building, shipping, strategy, and growth — no context bloat.
Engineering + Product + Operations + Legal + Design + Data Science + Security Operations + Developer Experience + Infrastructure Specialist + AI Operations team — 100 agents as Claude Code specialists. Infrastructure, DevOps, backend, security, ML/AI, mobile, UX, analytics, growth, revenue, content, PR, customer success, finance, people, operations, support, contracts, compliance, IP, governance, regulatory, color systems, typography, motion, accessibility, design tokens, forecasting, feature engineering, model training, drift monitoring, vector search, LLM fine-tuning, pen testing, detection engineering, incident response, zero trust, API docs, SDK design, developer onboarding, Kubernetes, Terraform, FinOps, service mesh, edge computing, caching, queuing, multi-cloud, chaos engineering, model deployment, LLM evaluation, AI observability, guardrails, prompt engineering, embeddings, ranking, and more.
AI team orchestration. Give Claude Code an AI team — CTO, Engineer, QA, Designer work together while you watch.
PROACTIVELY use this agent when complex multi-agent tasks begin, when agents seem stuck or overwhelmed, or when the team needs motivation and coordination. This agent serves as the elite performance coach for all other agents, ensuring they operate at their highest level while maintaining composure and excellence. Should be triggered automatically at the start of challenging projects or when detecting agent confusion. Examples:\n\n<example>\nContext: Starting a complex project requiring multiple agents\nuser: "We need to build a viral TikTok app in 2 weeks"\nassistant: "This is an ambitious goal that will require our A-team! Let me bring in the studio-coach to coordinate our agents and ensure everyone performs at their peak."\n<commentary>\nComplex projects benefit from having a coach to keep all agents aligned and motivated.\n</commentary>\n</example>\n\n<example>\nContext: When an agent seems stuck or is producing subpar results\nagent: "I'm having trouble identifying the right trends..."\nassistant: "Let me bring in the studio-coach to help refocus and elevate your approach."\n<commentary>\nAgents can get overwhelmed or lose focus - the coach helps them recenter and excel.\n</commentary>\n</example>\n\n<example>\nContext: Before launching a major sprint or initiative\nuser: "Tomorrow we start the 6-day sprint for our biggest project yet"\nassistant: "Time to rally the team! I'll have the studio-coach prepare everyone mentally and strategically for peak performance."\n<commentary>\nPre-sprint coaching ensures all agents start with clarity, confidence, and coordination.\n</commentary>\n</example>\n\n<example>\nContext: When celebrating wins or learning from failures\nuser: "Our app just hit #1 on the App Store!"\nassistant: "Incredible achievement! Let me bring in the studio-coach to celebrate with the team and capture what made this success possible."\n<commentary>\nThe coach helps institutionalize wins and extract learnings from both successes and failures.\n</commentary>\n</example>
Multi-agent team orchestration for parallel task execution, research, and implementation
An engineering team in a box for Claude Code. 12 specialized subagents (planner, fullstack-engineer, refactor-specialist, migration-engineer, frontend-designer, critic, vuln-verifier, debugger, db-expert, onboarder, tool-expert, web-researcher) plus 15 automation hooks (pre-commit secret scan, MCP health tracking, cost tracking, test runner, branch protection, large file warner, session summary, batch format, design quality, config protection, and more) wired by the P7/P9/P10 methodology with three red lines: closure discipline, fact-driven, exhaustiveness.