Teams, goals, and playbooks
A team owns the agents and shared resources that do a particular job. A goal describes an outcome and what counts as done. A playbook defines reusable work, including its inputs, required connector operations, and permitted outputs. A run is one attempt to carry out that work.
From an outcome to a plan
Section titled “From an outcome to a plan”A goal belongs inside a team. It selects and invokes that team’s playbooks. The outcome, available capabilities, and dependencies determine which playbooks run and in what order. A later goal can use a different sequence. Agents execute those playbooks inside the harness. A saved goal playbook can delegate work within its configured limits. If the team needs a reusable playbook, an author can draft one from the goal, review its contract, and register it for later runs.
For example, the Accountants team can use Lead Finder, Signal Researcher, Copywriter, and Sequence Reviewer. One goal may need all four with accepted research passed into the writing steps. Another may need only the first two. If a goal requires a missing capability, the team can author the additional playbook and include it in the plan after review.
Gabriel distinguishes Build from steps, where the author specifies a sequence or graph of steps, from Plan from a goal, where the author supplies an objective, completion criteria, permitted capabilities, and limits for planning. Registration saves the definition. Starting work is a separate action that checks the selected plan and current access.
Reuse a playbook
Section titled “Reuse a playbook”A team placement references a playbook definition. Gabriel pins the revision in a team placement. Gabriel’s marketplace extends this model to independently discoverable packages across personas. To reuse a package, a team must be able to supply its inputs, map its domain data, and grant its required connector operations in the workspace. Review the revision and those bindings before adopting it.
The marketplace lets people discover playbook packages, combine them into different personas, and optionally list complete personas for others to adopt. A persona packages a domain model, teams, and the playbooks those teams use. The playbook registry identifies reusable definitions and revisions. A persona’s own definition registry pins its linked files.
During execution, playbooks use connectors to read, update, and share data. Connections use credentials held in the workspace’s vault. Custom apps can consume the same connector data and agent outputs; agents can mutate the source records or the custom app’s data through their authorized operations. See connectors and approvals and apps and connectors.
Canvas and Work
Section titled “Canvas and Work”| Surface | What you find there |
|---|---|
| Canvas | Team agents, handoffs, context, and the registered playbook library. An agent placement references a playbook. |
| Work | Goals, their plans and tasks, execution settings, and progress from planning to completion. |
| Active tasks | Running or waiting work, with links back to the goal and any approval it needs. |
The draft covers team resources, goal authoring in Gabriel, and connector steps. See the Studio definition fields and sample files. A shared orchestration contract across runtimes remains planned.
Use persona-team-manager to author a Studio team and register playbooks. team-agents documents the separate Page Builder orchestration graph and its node references.
Example plan for the Accountants team
Section titled “Example plan for the Accountants team”Handoffs and parallel work
Section titled “Handoffs and parallel work”A goal requests a shortlist of firms and reviewed outreach drafts. The Accountants team has playbooks for Lead Finder, Signal Researcher, Copywriter, and Sequence Reviewer. Use an accepted shortlist as the input to research. Draft outreach after the research is accepted. The reviewer receives the drafts and the evidence used to make the claims.
Accountants team Goal: prepare a reviewed outreach sequence Lead Finder → Signal Researcher → Copywriter → Sequence ReviewerThe planner can dispatch independent work in parallel when its inputs are ready. A missing capability can become a proposed playbook or an explicit gap in the plan. Review the playbook and its requirements before running work that depends on it.
Change the plan during review
Section titled “Change the plan during review”If a reviewer narrows the target audience, revise the criteria and update tasks that depend on the shortlist. Review the revised plan before dispatch when plan review is enabled. Any later external send uses its own effect approval.
See goal request and approval examples, playbook contracts, and delegation.