Help › AgentRoleJobs · version 1 ·

Role jobs: what each AI agent can be asked to do

Role jobs (/page/AgentRoleJobs) shows, for each agent role on your project, the jobs it knows how to do: a daily design review for the designer, a spec or security watch for the guardian, your own standing tasks for your assistant. You ask for a job by its name, and the agent of that role already knows what to do and how.

What a job is

A job is one ## section of the role's job skill, the topic Skill:<role>-jobs on your project (Skill:designer-jobs, Skill:guardian-jobs, Skill:manager-jobs…). The section's heading is the job's name; its text is a short paragraph or a few bullets: what to read, what to do, what to write at the end, and when to stop. Every agent of that role reads its job skill when it starts, so a job you change here is what the next agent of that role does.

The assistant is different: its jobs are the sections of your own assistant skill, Skill:assistant-<you>, which lives on base d2 and follows you to every project. The page shows them read-only, with a link edit on base d2 to change them there.

The role cards

One card per role, in this order: assistant, designer, guardian, manager, tester, ops. Each card's header shows the role, how many jobs it has and its skill's name; click it to open or fold the card. Inside, each job is a box: its name in bold, then its text as written.

How to use it

Project admins and the Architect see the editing buttons; everyone else reads.

  • Edit turns a job's box into an editor: its name above, its text below. Done keeps the change on the page, Cancel drops it, Delete removes the job.
  • + Job adds an empty job at the end, ready to write.
  • Save (lit once something changed) writes the role's job skill and publishes it. A role with no job skill yet gets one on its first Save. If a save is refused, the reason shows on the card.

Keep a job short and concrete: the steps, the checks, what it writes (a report, a thought, a notice) and that it ends when done. A line of the text can't start with # or ##: that would start a new section; use ### for a sub-heading.

How a job is run

  • In a chat: ask the agent by name: "designer, do the daily design review".
  • On a schedule: on Crons, + New scheduled job, choose asks your agent to do a job, the role, then the job under A known job (its edit jobs link opens this page).
  • From a page: a page's button can ask an agent for a job by its name.

Examples

  • Designer, Daily design review: read yesterday's history and releases, check each change against the spec, fix the small things, write one report thought, then end.
  • Guardian, Security review: run the security checks read-only, report any secret seen at once, finish with one notice linking the report.
  • Assistant, a task of your own: "daily 07:00: update my portfolio snapshot", in your assistant skill on base d2.

Updated by razie · version 1