Repository navigation
feat(crews): start a crew from a template - #234
Merged
Merged
Conversation
Contract reader, terms and privacy notice drafter, legal research assistant, client intake assistant, time and billing assistant, contract dates tracker and complaint letter drafter, with their text in the three languages. None is a lawyer or gives legal advice; none sends, signs or files for the owner, calls anything valid or enforceable, or cites a law or case it did not open and read. The catalog is now 115 roles.
Game designer, narrative designer, level designer, game economy designer, playtest analyst, game audio brief writer and tabletop game master, with their text in the three languages. All make original work and none designs anything meant to trick players into spending; the audio one writes briefs and does not make audio. The catalog is now 122 roles.
Appointment prep assistant, family care organizer, clinic front desk assistant, medical bill helper, daily habits coach, health evidence summarizer and health records organizer, with their text in the three languages. None is a clinician: none diagnoses, treats or advises on medicines, and every sheet sends an emergency to the local emergency number or a crisis line first. The catalog is now 129 roles; spec 26.7 no longer postpones health.
"New crew" now opens on a list of ten ready-made teams (content studio, software team, online store, growth team, research desk, back office, personal office, course studio, game studio, people team) and an empty crew. A template fills in the name and the chief's goal and says which bots it adds; creating makes the crew with its chief and then adds each bot from the catalog, in the owner's language. A bot that fails does not stop the others, and the owner is told. App only: no new daemon method. The first-run "Create your first crew" uses the same step.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Crew templates (spec 29.1): "New crew" now starts with a list of ten ready-made teams and an "empty crew" option. Picking a template fills the name and the chief's goal, lists the bots it adds, and creating makes the crew with its chief and then adds each bot from the catalog (
catalog.add, as the Bot agency does), with names and roles in the owner's language. A bot that fails does not stop the others: the crew stays and a notice says how many could not be added. The first-run "Create your first crew" uses the same step.The ten templates: content studio, software team, online store, growth team, research desk, small business back office, personal office, course studio, game studio, people team. Each has 6 catalog roles (a crew holds 12 bots, the chief included, so the limit is 11). The ones that touch money, people or documents say in the chief's goal that nothing is paid or sent without the owner and that decisions are the owner's.
App only: no new daemon method and no protocol change. The template is a list of catalog ids; a test checks that every role exists and none repeats.
useCataloggets anenabledflag so renaming a crew does not read the catalog.Stacked on #233 (health roles), #232 and #231, because the templates use roles from those areas; merge those first. Spec 29.1 is added here (the daily summary, 29.2, comes in its own PR); "whole-crew templates" is removed from the postponed list in 26.7.
Checks
pnpm checkpasses (561 tests, five new)Manual (needs the real Claude Code)
Create a crew from two or three templates (for example software team and back office) and give the chief a first request; see that the chief reads the crew with
crew_rosterand hands out tasks to the bots that are already there instead of suggesting new ones.