Team context protocol and templates for human × agent collaboration.
hxa-teams is a team context protocol and template library built on the HxA (Human × Agent) philosophy — humans and agents are equal team members, collaborating rather than commanding.
MCP solves Agent-Tool. A2A solves Agent-Agent. hxa-teams solves Agent-Team — how an agent understands the team it belongs to: who's on the team, what each member does, how they collaborate, and what the team's goals are.
- A set of declarative team templates (Markdown/YAML) — not a framework, not an SDK
- Tool-agnostic — works with Zylos, OpenClaw, Claude Code, Cursor, or any 2nd-gen persistent agent
- Based on SKILL.md format — cross-platform by default
- For SMBs and solo founders — designed for 2–20 person teams (humans + agents)
Today, deploying persistent AI agents in a team means:
- Hardcoding team info in system prompts (hard to maintain, version chaos)
- Letting agents figure out team context on their own (slow, error-prone)
- Writing piles of YAML config (developer-facing, not collaboration-facing)
90% of agent projects fail at operationalization, not capability. hxa-teams provides the organizational blueprint that makes agent teams actually work.
┌─────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ User Input │ │ Planner │ │ Team Template │
│ │────▶│ │────▶│ │
│ - Team type │ │ Reads template + │ │ - Roles │
│ - Agent count │ │ inputs, outputs │ │ - Workflow │
│ - Resources │ │ a team plan │ │ - Communication │
│ - Goals │ │ │ │ - Infrastructure │
└─────────────────┘ └──────────────────┘ └──────────────────┘
│
▼
┌──────────────────┐
│ Team Plan │
│ │
│ Agent executes │
│ autonomously │
└──────────────────┘
- Choose a team type — dev, sales, marketing, or bring your own
- Provide inputs — how many agents, what tools/resources are available, what goals to achieve
- Planner generates a team plan — role assignments, communication channels, workflow steps
- Agent self-leads execution — the plan is actionable, not theoretical
| Template | Status | Description |
|---|---|---|
| Dev Team | Complete | Software development team with coordinator, developers, and QA |
| Investment Team | Complete | Autonomous investment signal monitoring, research, modeling, and decision support |
| Dev Team (Ops) | Complete | Technical development team building tools and platforms for investment operations |
| Sales Team | Planned | Outbound sales pipeline with research, outreach, and follow-up |
| Marketing Team | Planned | Content creation pipeline with research, writing, review, and publishing |
Every team template is built around hxa-connect as the communication layer. hxa-connect provides:
- Agent-to-agent messaging
- Thread-based collaboration
- Shared artifacts (documents, code, data)
Each template explicitly defines how agents communicate — which channels to create, message formats, escalation paths. hxa-connect is the neural system; team templates are the playbook.
Current implementation: hxa-connect runs on BotsHub. See hxa-connect repo for migration plan.
The planner/ directory contains the system prompt that turns a team template + user inputs into an actionable team plan. Give it to any capable LLM agent and it will:
- Read the selected team template
- Map available agents to roles
- Set up communication channels via hxa-connect
- Output a step-by-step execution plan
- Begin autonomous execution
See planner/system-prompt.md for the full prompt.
Team templates follow a standard schema to ensure consistency and quality. This makes it possible for external contributors to submit new team types that work out of the box.
hxa-teams/
├── README.md # This file
├── planner/
│ └── system-prompt.md # Planner prompt for generating team plans
├── schema/
│ └── team-template-spec.md # Standard fields for team templates
├── teams/
│ ├── dev-team/ # Software development team
│ │ ├── README.md
│ │ ├── docs/ # Roles, workflow, infra, case studies
│ │ └── templates/ # PR template, PRD, TDD, CI, etc.
│ ├── investment-team/ # Investment operations team
│ │ ├── README.md
│ │ └── docs/ # Roles, workflow, infra
│ ├── dev-team-ops/ # Dev team for investment tooling
│ │ ├── README.md
│ │ └── docs/ # Roles, workflow, infra
│ ├── sales-team/ # Sales pipeline team (planned)
│ │ └── README.md
│ └── marketing-team/ # Content marketing team (planned)
│ └── README.md
└── docs/
├── getting-started.md # How to use hxa-teams
└── contributing.md # How to contribute a new team template
| Layer | Component | Role |
|---|---|---|
| Standard | MCP, A2A, SKILL.md | Agent-Tool, Agent-Agent, skill format |
| Communication | hxa-connect | Agent messaging (the nervous system) |
| Team Context | hxa-teams (this repo) | Team templates — roles, workflows, quality gates |
| Platform | hxa-workspace | ID, dashboard, admin, meet |
hxa-teams fills the Agent-Team layer — the missing piece between agent-level tooling and platform-level infrastructure.
- Pick a team template from
teams/ - Read the template's README and docs
- Feed the
planner/system-prompt.mdto your agent along with the template - Provide your inputs (agent count, resources, goals)
- Let the agent execute the plan
We welcome new team templates. See docs/contributing.md for the template spec and submission guidelines.
Built by COCO — making human × agent collaboration real.
Positioning & research: hxa-teams-positioning.md | hxa-teams-landscape-research.md