← ClaudeAtlas

provision-teamlisted

Provision a new agent team with identity, composition, governance, and orchestration protocol. Creates TEAM_IDENTITY.md, TEAM_COMPOSITION.md, TEAM_GOVERNANCE.md, and registers the team in the governance nucleus. Use when assembling multiple agents into a coordinated team for a shared purpose — code review squads, build teams, research panels, or any multi-agent workflow.
MyAiFreedomSystems/incredagents · ★ 0 · AI & Automation · score 66
Install: claude install-skill MyAiFreedomSystems/incredagents
# Provision a Team This skill creates a fully provisioned team folder that coordinates multiple agents toward a shared purpose. The team inherits governance from `$GOVERNANCE_HOME` and references existing orchestration infrastructure — it does not reinvent it. ## When to invoke Invoke when the user says any of: - "Provision a new team called X." - "Create team X for Y." - "Stand up team X." - "Scaffold a new team at `<path>/X`." - "Initialize X as a team." Do NOT invoke for: - A single agent (use `provision-agent` instead). - A plain project folder (use `provision-project` instead). - A team folder that already has `TEAM_IDENTITY.md` and `TEAM_COMPOSITION.md` — it's already provisioned. ## Prerequisites 1. `GOVERNANCE_HOME` must be set. 2. Each agent in the team composition must already be provisioned via `provision-agent`. ## Inputs 1. **Team name** — Preserve casing. Examples: `BuildTeam`, `ResearchSquad`, `GrowthTeam`. 2. **Purpose** — One paragraph: what this team collectively accomplishes. 3. **Agent composition** — List of agent names that form the team (each should already be provisioned). 4. **Orchestration protocol** — How agents hand work to each other. Default: sequential dispatch with convergence voting. Specify if custom. If any required input is missing, ask once. Do not provision with a guessed composition. ## The steps Execute completely and autonomously. ### Step 1 — Verify nothing is already provisioned ```bash TARGET="<TeamPath>" if [