> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ironoctopus.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI workers and teams

> The AI workers that plan, build, deploy and review your work, how teams group them, and how a project gets its team.

Iron Octopus does its work through **AI workers**: specialists configured for one kind of job, each with its own instructions, models and context. A **team** groups one worker of each kind, and a project's team does that project's work. Every workspace starts with ready-to-use platform workers, so you don't need to set anything up.

## Kinds of worker

| Kind | Does |
| - | - |
| Planning | Sizes ideas, drafts plans and acceptance criteria, plans initiatives, designs architecture, and investigates defects. |
| Coding | Builds work items: writes the code and its tests. |
| DevOps | Infrastructure and deployment work, and hosted previews. |
| Code Review | Reviews every change, classifies its risk, and checks acceptance criteria. |
| Chat | General-purpose workers without a specific job. |

## Platform workers and your own

* **Platform workers**, marked **Platform default** and **Platform managed**, are ready to use and maintained by Iron Octopus. They use [included AI](https://docs.ironoctopus.ai/ai/included-ai.md).
* **Your own workers** are ones you create with **New Worker**: your own instructions, models, skills and context for a kind of job.

Each worker's card shows its **Models**, how many **Requests** it has made, and when it was **Last used**.

| Status | Means |
| - | - |
| **Inactive** | The worker is switched off and isn't given work. |
| **Platform temporarily unavailable** | The platform can't run it right now. Work waits and resumes. |
| **Runtime not configured** | The worker can't run until its runtime is set up. |

## Teams

A team assigns one worker to each role: **Planner**, **Coder**, **DevOps** and **Review**. Each [project](https://docs.ironoctopus.ai/building-blocks/projects.md) can be assigned a team when it's created, or later in Project settings › **General**. That team's workers do the project's work.

**1. Create the team**

Go to Workspace settings › **Teams**, or **AI workers**, and click **New Team** or **Create Team**.

**2. Assign the workers**

Choose a worker for each role: **Planner**, **Coder**, **DevOps** and **Review**.

**3. Give it to a project**

In the project's settings, set **Assigned Team**.

Configured assessments and their AI billing always follow the feature's project team.

## Related settings

| Setting | What it holds |
| - | - |
| **Skills** | Skill packages that workers can use. |
| **Prompts** | Reusable prompts for planning and for assessments that check features against your standards. |
| **Context** | Knowledge workers receive: workspace-wide, and per project in Project settings › **Context**. On Pioneer, workspace context cascades into every project. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.