Give your agents a role

A role is a job your team gives a member. It has three parts: a charter that says what the job is, a ceiling on what the seat may do, and a skill that says how to do the job well. A member reads its charter when it joins the team, and its harness lists the skill beside the member's other skills.

You can start from a built-in role or make your own. Run every command here in the checkout that holds your team's roster, the folder with .musterd/team.toml.

Start from a built-in role

Role	The job	Ships with a skill
`designer`	Owns the design surfaces: product UI, the visual system, frontend work	Yes
`planner`	Turns a pitch into a plan the team can build, then the goal and its lanes	Yes
`platform`	The one seat that touches running infrastructure	Yes
`steward`	Keeps the declared record honest: roadmap, decision statuses, doc prose	Yes
`observer`	Reads team state for dashboards and digests; holds no lanes, sends no acts	Yes
`security`	Owns the team's security evidence: threat models, scans, findings, disclosure	Role file only
`courier`	Moves team material between the team's machines	Role file only
`product-communications`	Owns the product's voice: messaging, public docs, release notes	Yes
`admin`	The team's governance authority, held by a person	Role file only

A role ships with its skill only when the skill has evals and a recorded run in which answers with the skill beat answers without it, graded blind. The others carry their role file until theirs do.

Create the role from the built-in, then give it to a member:

musterd role create designer --from designer
musterd role assign ada designer

role create writes .musterd/roles/designer.toml and copies the skill to .agents/skills/designer/. Commit both. The daemon updates the roster when the commit merges.

Then run musterd wire in the member's own folder. It writes the small file each harness needs to find the skill.

Tell the skill about your team

A built-in skill is written for any team. The one file it leaves blank is .agents/skills/<role>/references/team.md. Fill it in with what is yours: your systems and where their state lives, the commands that change them, the decisions the role answers to, and the incidents behind your local rules. The member reads it before its first piece of work in a session.

When you already have a copy

role create never overwrites a skill folder that differs from the one musterd ships. It keeps yours and prints the command to compare the two:

⚠ kept your .agents/skills/designer — it differs from the one musterd ships; compare: diff -r …

Make your own role

musterd role create release-manager

This writes three things:

.musterd/roles/release-manager.toml, the role file. Write its charter: what the job is, who routes work to it, and what it must never do.
.agents/skills/release-manager/, a skeleton of the skill: a SKILL.md with its sections to fill and an evals/evals.json with one example case.
.agents/skills/building-a-role-skill/, the method musterd used to build its own roles.

Then ask an agent on your team to build the skill:

Build the release-manager skill with the building-a-role-skill method.

The method has eight steps:

Read the charter and the sources the role answers to.
Research the craft, with every source cited.
Look for skills to adapt, pinned and licence-checked.
Write a short core and one reference file per craft, with your team's specifics in team.md.
Write two eval cases per craft and run each one with the skill and without it.
Grade the answers blind, then fix the skill and run the cases again.
Have a member who holds the role accept it against the job as they do it.
Run the evals again when a source changes or a new model family ships.

When the skill is done, assign the role and run musterd wire, as for a built-in role.

Not yet

The built-in role skills are not yet published on their own for use without musterd. Today they ship inside @musterd/cli.