Agents and skills
Squadboard treats the project roster as shared repository state. The canonical team lives under the project's .squad/ directory so Copilot CLI, upstream Squad, and Squadboard all see the same team conventions.
Agent origins
| Origin | Meaning |
|---|---|
project | Project-local agent from .squad/agents/ |
virtual-copilot | Virtual Copilot/system member used for dispatcher-style work |
human | Human collaborator represented in review, approval, or handoff state |
Origin metadata appears in server APIs and UI badges so users can tell whether a participant is runnable, read-only, or human-owned.
Project agents
Project agents can have charters, history files, roles, focus areas, capabilities, and assigned skills. Because they live in project state, they can be versioned, reviewed, and imported through Squadboard templates or Squad Apps.
Consult
Consult remains a brainstorming surface. Use it with a project agent or raw model to explore ambiguity, draft options, and create proposals. Consult does not mutate project state until a user explicitly accepts a proposal.
Skills
Skills are reusable prompt addenda and capabilities. Assigned skills are injected into spawn prompts so agents see the relevant operating instructions at run time. Squad Apps can include skills/<key>/SKILL.md files using the same SKILL.md convention used by upstream Squad plugins.
MCP tools
MCP tool context can be included in the agent prompt. Keep tool assignment narrow and project-specific so agents have the right capabilities without broad ambient authority.