2. Cast and review the team

Your project needs a small, project-specific team — not a generic pool of assistants. In this tutorial, you will review who is on the roster, fill any role gaps with Cast Team, and use Consult to think out loud before you commit anything to the board.

This tutorial assumes you completed Tutorial 1 and have your project open.

Why this matters

When you move a card to Ready (next tutorial), Squadboard's coordinator decides who picks it up. That decision uses agent role + charter + skills + labels on the card, not the agent's name. A roster with thin or missing roles produces bad assignments — so give it five minutes here before queuing work.

1. Open the roster

Open Agents. Your project from Tutorial 1 should have at least a launch lead and an integration owner already present (either from the template or from your existing .squad/).

For each agent, confirm:

1. Name is stable and easy to reference in cards and labels.
2. Role describes an outcome (Launch lead, Integration engineer), not just a technology.
3. Expertise covers the recurring decisions your project will make.

If any agent is missing a role or charter, fix it now. Charters live under .squad/ and are shared with upstream Squad and Copilot CLI — edits here are durable.

2. Fill role gaps with Cast Team

If your project is missing a role you know it needs — say a reviewer or a docs lead — click Cast Team. Cast Team turns "what team should this project have?" into a reviewable proposal you can edit before accepting.

Accept only the roles you actually need. A small team with sharp charters routes better than a big team with vague ones.

3. Use Consult when the work is still ambiguous

Before queuing a card, you often want to think it through with an agent or with a raw model. That is what Consult is for. It is exploration; nothing it produces changes your project until you create a card or accept a proposal.

Open Consult → New consult, pick Model (or a specific agent), and ask a narrow question. For example:

Write a guide that explains Squadboard's relationship to upstream Squad.
What are the three main topics to cover, and what tone should it use?

Rules of thumb:

• Use Consult when the right answer depends on judgment, tone, or incomplete information.
• Use a board card when the answer needs durable execution, audit trail, and a run history.
• When Consult produces something good, promote it: copy the wording into a new board card so the work becomes trackable.

What you should have now

• A project roster where every agent has a name, role, and charter.
• A casting decision recorded (either "current roster is fine" or "added X via Cast Team").
• A Consult conversation that helped you sharpen the next card — or a confirmed plan to skip Consult and go straight to the board.

Continue with 3. Run a workflow → to capture work, move it into Ready, watch automatic pickup, and inspect what the agent produced.