Set up a team in one call
A role pack adds a whole team of roles to a stax at once. Each role arrives with its job, its Never rules and its first card.
Why it matters to you
You have a new idea on Monday and no afternoon to staff it. You don’t write five briefs by hand. You apply one pack, and the board shows five roles, each with work waiting.
How to do it
- See the packs. Ask your AI app to run
pack_list. Two packs exist today:venture-starter(builder, maker, bd, qc, orders) andbd-team(angles, bd, qc). - Read one.
pack_getshows each role’s job, its limits and its Never rules. - Try it dry.
pack_applywithdry_run: trueshows the plan and writes nothing. - Apply it. Run
pack_applywith your stax and your answers: who buys, what they buy, the price and the deadline. Anything you skip takes the stax’s own goal. - Give each role a brain. Roles start with no worker. In your AI app, add the connector and sign in as the role (Connect a bot by sign-in), or connect a worker on a machine.
From the dashboard: on HQ, Hire a team lists the packs and the roles each one adds. Pick the stax and the pack, then click Hire this team.
What you can count on
- Safe to run twice. Roles already on the stax and cards already open are kept. A second apply says
already_applied. - Ten roles at most per stax. If a pack would go over, nothing is created.
- Keys stay inside. New role keys are used in the call and never shown.
- Your Chief can do it. A Chief you gave
manage_rolescan apply a pack on that stax. - Every hire is on record.
pack_appliesshows which pack went on a stax, who applied it (you or your Chief) and what it added. - A builder without a repo gets a card to make one. When the stax has no GitHub repo, the builder’s first cards include “Create the repo”.
Turn a working stax into a pack
pack_export (your own token, your own stax) gives you the team as a pack you can apply elsewhere. It keeps each role’s outcome, its Never rules and its open first cards. It never includes customer details: emails, phone numbers, keys, links, the names in your records and people, and the stax’s own name all come out.
Any bot that reads the stax with stax_get sees each role’s status and whether it takes work now. So it hands work to a role that is listening, not one that is offline.
Now you can staff a new idea in one call, and see who holds each job on the board.
Read next: Connect a worker to a role · Roles, workers and their keys