---
title: "join-the-team"
description: "Team operating model for hybrid human+AI delivery: one shared, drift-checked contract for authority, risk tiers, evidence, review, and done, with cloud-expert guardrails (Google Cloud, AWS, Azure, Alibaba Cloud) and Goog"
canonical: https://agentpluginsdirectory.com/plugins/join-the-team
last-updated: 2026-09-22
---

# join-the-team
Team operating model for hybrid human+AI delivery: one shared, drift-checked contract for authority, risk tiers, evidence, review, and done, with cloud-expert guardrails (Google Cloud, AWS, Azure, Alibaba Cloud) and Google ADK/Antigravity skills built in, routing agent-craft work to companion skill plugins.
- Slug: join-the-team
- Publisher: Jaroslav Pantsjoha
- Repository: https://github.com/jpantsjoha/ai-native-developer-experience
- Manifest: plugin.json
- Version: 0.3.0
- License: Apache-2.0
- Category (editorial): productivity
- Skills: 22 (adk-expert, adversarial-gate, cloud-checkup, cloud-expert, cost-guardrail, delivery-orchestrator, domain-validator, frontend-performance-audit, get-it-done, github-manager, governance-guardrail, mcp-server-scaffold, operating-model-bootstrap, plugin-submission, pr-reviewer, release-manager, release-readiness, sitrep, spec-first-delivery, system-performance-guardrail, the-architect, using-the-harness)
- MCP servers: 0
- Stars: 11
- Repository created: 2026-02-03
- Repository last pushed: 2026-09-14
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/join-the-team
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What join-the-team does, in the publisher's words

> A team-project AI harness bootstrap that gives humans and agents a shared operating contract from day one, moving AI leverage from an individual "IC superhero" advantage to a repeatable team capability on an equal playing field.

> 📦 Now listed on Claude Plugin Hub, > install the harness as the join-the-team plugin for Claude Code, Codex, Kimi Code, > and Google Antigravity. Jump to install.

This repository has gone through three real phases, and the progression tracks something happening across the field.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/jpantsjoha/ai-native-developer-experience/HEAD/README.md

## Skills

- adk-expert: Google ADK (Agent Development Kit) orchestration patterns, boundaries, agent composition, and tool seams. Trigger when designing or reviewing multi-agent systems built on ADK. Authoritative source: adk.dev.
- adversarial-gate: JP's signature red-team pass: "how would I break this?" Argue against your own approach before proceeding. Trigger on any high-stakes decision, architecture choice, or before marking work complete.
- cloud-checkup
- cloud-expert
- cost-guardrail: LLM and cloud cost awareness: model tiering, token budgets, right-sizing, and when a cheaper model suffices. Trigger before finalising any architecture that calls LLMs, before scaling a workload, or when a cost estimate is needed.
- delivery-orchestrator: Decompose an epic into atomic parallelizable tasks and route each task to the right skill. Use this as a meta-router when you have more than one skill available and need to decide which applies. Trigger at the start of any multi-track epic or when the skill count in your harness exceeds ~12.
- domain-validator: Validate agent output against declared domain rules and ground truth before trusting it downstream. Trigger after any agent produces output that will be used in a decision, stored persistently, or passed to another agent.
- frontend-performance-audit
- get-it-done
- github-manager: Use when configuring or optimising GitHub repositories for cost-effective, consistent operations, CI triggers, Actions billing, issue tracking, labelling, branch protection, or release workflow.
- governance-guardrail: Check proposed stack, data flows, cloud choices, and delivery controls against declared enterprise policies, compliance frameworks, and security controls. Trigger at R2/R3 risk classification, before locking architecture decisions, or when the operating profile names a governance pointer.
- mcp-server-scaffold: Scaffold and govern an MCP server as a bounded tool seam. Defines which tools the agent may call, enforces the principle that agents call tools and tools call infrastructure. Trigger when adding or reviewing an MCP server in an agent system.
- operating-model-bootstrap
- plugin-submission
- pr-reviewer
- release-manager
- release-readiness
- sitrep
- spec-first-delivery
- system-performance-guardrail
- the-architect
- using-the-harness

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.