Foreman kit · src/components/kit/TeamBuilder.astro
Kit: TeamBuilder
"Build your team" from Hire the Crew as a widget: Open roles, Your team, the hold switch and the hat rule, with the Priya channel as an optional part (channel). Three instances share one script.
Defaults <TeamBuilder id="tb-default" />
Try it here
Build your team
Hire from the fifteen job templates Foreman ships. Each one arrives approved, with its job's own prompt, a free hat colour and the same access.
Open roles 15
Engineering
Design
Product
Data
Writing
Marketing
Customers
Hat rule A hat says who, never state. If a job's colour is taken, the new hire wears the least-worn colour instead.
Slack posts and Linear changes start held for you. Since v1.2.4 an employee pushes and opens draft pull requests on its own; this switch is the one-line rule that holds those too.
Your team 5
You
The person · one of the team
Approve each plan and each hire, and anything you've asked the team to hold.
Priya Lead
Program manager
Plans every project, proposes who it needs, reviews each part and accepts the result.
Ravi
Staff software engineer
Builds and fixes features, with tests, on its own branch.
Uma
Staff UX designer
Reviews screens and flows, specifies what to build and draws it as mocks.
Quinn
Staff QA engineer
Reviews what others build and says what breaks.
Mei
Staff frontend engineer
Builds screens and components and keeps them accessible.
Omar
Staff security engineer
Reviews changes and dependencies for security risks.
Sofia
Staff site reliability engineer
Keeps builds, deploys and services healthy.
Kenji
Staff software architect
Shapes the system and reviews big changes before they start.
Leo
Staff web designer
Designs and builds marketing and content sites.
Nia
Staff product manager
Recommends what to build next and writes the requirements.
Dara
Staff data analyst
Answers questions with data and specifies dashboards.
Theo
Staff technical writer
Writes the docs and keeps them up to date.
Ines
Staff copywriter
Writes release notes, launch posts and site copy.
Sam
Staff SEO specialist
Audits the site for search and suggests fixes.
Ana
Staff marketing manager
Plans launches and the messages around them.
Jonah
Staff support engineer
Triages issues and traces what users report in the code.
Night theme, with the channel channel · hires: Mei, Sam, Quinn
Night crew
Staff the night shift
Hire from the fifteen job templates Foreman ships. Each one arrives approved, with its job's own prompt, a free hat colour and the same access. Then ask Priya for something and watch the work come back to you.
Open roles 15
Engineering
Design
Product
Data
Writing
Marketing
Customers
Hat rule A hat says who, never state. If a job's colour is taken, the new hire wears the least-worn colour instead.
Slack posts and Linear changes start held for you. Since v1.2.4 an employee pushes and opens draft pull requests on its own; this switch is the one-line rule that holds those too.
Your team 5
You
The person · one of the team
Approve each plan and each hire, and anything you've asked the team to hold.
Priya Lead
Program manager
Plans every project, proposes who it needs, reviews each part and accepts the result.
Mei
Staff frontend engineer
Builds screens and components and keeps them accessible.
Sam
Staff SEO specialist
Audits the site for search and suggests fixes.
Quinn
Staff QA engineer
Reviews what others build and says what breaks.
Green is Sam's hat, so Quinn wears orange.
Ravi
Staff software engineer
Builds and fixes features, with tests, on its own branch.
Omar
Staff security engineer
Reviews changes and dependencies for security risks.
Sofia
Staff site reliability engineer
Keeps builds, deploys and services healthy.
Kenji
Staff software architect
Shapes the system and reviews big changes before they start.
Uma
Staff UX designer
Reviews screens and flows, specifies what to build and draws it as mocks.
Leo
Staff web designer
Designs and builds marketing and content sites.
Nia
Staff product manager
Recommends what to build next and writes the requirements.
Dara
Staff data analyst
Answers questions with data and specifies dashboards.
Theo
Staff technical writer
Writes the docs and keeps them up to date.
Ines
Staff copywriter
Writes release notes, launch posts and site copy.
Ana
Staff marketing manager
Plans launches and the messages around them.
Jonah
Staff support engineer
Triages issues and traces what users report in the code.
You
@Priya add passkey sign-in to atlas
Priya
I read atlas first: sign-in lives in
src/auth/. Two questions before I plan.1. Keep passwords as a fallback? Why: decides whether existing accounts move.
2. Must Safari work on day one? Why: Safari's passkey sheet needs its own test.
You
Keep both. Yes, Safari too.
Priya
Plan v1 · small · 3 parts
Done when you can sign in to atlas with a passkey in Chrome and Safari, and passwords still work.
- 1Spec the passkey screens, two mock optionsMei
spec.md - 2Test plan for Chrome and SafariQuinn
test-plan.md - 3Build it, run the plan, pushMei
build.md
- 1Spec the passkey screens, two mock optionsMei
- You approved plan v1 · Mei and Quinn start in order
Mei
Built passkey sign-in on
passkey-sign-infrom Mei's option B. Ran Quinn's plan: 18 of 18 cases pass in Chrome; Safari needs you to try the sheet by hand. Asked to push.Push
passkey-sign-into atlas3 commits ahead of main · 6 files · origin github.com/acme/atlas
Push branch sends 3 commits to origin. It leaves this computer and can't be undone.
Don't pushPush branch
git log --format='%h %an %s' -- memory/
c41f9e2Quinnlearned the test DB must be reset before e2ememory/bots/e-9q4c/MEMORY.md7d02b11Youkept Uma's proposal: every screen works at 390pxmemory/org/PROJECT.md · Foreman-Proposed-By: e-4ux819ad3f4Priyaplan v2 for checkout-redesignmemory/org/projects/checkout-redesign/plan.md
Each run's notes land as one commit in the organization's private memory repository.
Start a project with @Priya, or ask one person with @Name. Try one:
Illustrative. In the app, Priya's plans, questions and held actions read the same way.
Compact, channel on, hold off compact · channel · hold=false · sticky=false
Open roles 15
Engineering
Design
Product
Data
Writing
Marketing
Customers
Hat rule A hat says who, never state. If a job's colour is taken, the new hire wears the least-worn colour instead.
Slack posts and Linear changes start held for you. Since v1.2.4 an employee pushes and opens draft pull requests on its own; this switch is the one-line rule that holds those too.
Your team 4
You
The person · one of the team
Approve each plan and each hire, and anything you've asked the team to hold.
Priya Lead
Program manager
Plans every project, proposes who it needs, reviews each part and accepts the result.
Ravi
Staff software engineer
Builds and fixes features, with tests, on its own branch.
Theo
Staff technical writer
Writes the docs and keeps them up to date.
Mei
Staff frontend engineer
Builds screens and components and keeps them accessible.
Quinn
Staff QA engineer
Reviews what others build and says what breaks.
Omar
Staff security engineer
Reviews changes and dependencies for security risks.
Sofia
Staff site reliability engineer
Keeps builds, deploys and services healthy.
Kenji
Staff software architect
Shapes the system and reviews big changes before they start.
Uma
Staff UX designer
Reviews screens and flows, specifies what to build and draws it as mocks.
Leo
Staff web designer
Designs and builds marketing and content sites.
Nia
Staff product manager
Recommends what to build next and writes the requirements.
Dara
Staff data analyst
Answers questions with data and specifies dashboards.
Ines
Staff copywriter
Writes release notes, launch posts and site copy.
Sam
Staff SEO specialist
Audits the site for search and suggests fixes.
Ana
Staff marketing manager
Plans launches and the messages around them.
Jonah
Staff support engineer
Triages issues and traces what users report in the code.
You
@Priya add passkey sign-in to atlas
Priya
I read atlas first: sign-in lives in
src/auth/. Two questions before I plan.1. Keep passwords as a fallback? Why: decides whether existing accounts move.
2. Must Safari work on day one? Why: Safari's passkey sheet needs its own test.
You
Keep both. Yes, Safari too.
Priya
Plan v1 · small · 3 parts
Done when you can sign in to atlas with a passkey in Chrome and Safari, and passwords still work.
- 1Spec the passkey screens, two mock optionsUma proposed
spec.md - 2Test plan for Chrome and SafariQuinn proposed
test-plan.md - 3Build it, run the plan, pushRavi
build.md
Nobody on the team fits these parts, so I'm proposing a Staff UX designer, Uma; a Staff QA engineer, Quinn. Review before you approve.
- 1Spec the passkey screens, two mock optionsUma proposed
- You approved plan v1 and Uma and Quinn · Uma, Quinn and Ravi start in order
Ravi
Built passkey sign-in on
passkey-sign-infrom Uma's option B. Ran Quinn's plan: 18 of 18 cases pass in Chrome; Safari needs you to try the sheet by hand. Pushed it.- Decided for you · Ravi pushed
passkey-sign-in(3 commits), allowed by Ravi's rule. It can't be undone.
git log --format='%h %an %s' -- memory/
c41f9e2Quinnlearned the test DB must be reset before e2ememory/bots/e-9q4c/MEMORY.md7d02b11Youkept Uma's proposal: every screen works at 390pxmemory/org/PROJECT.md · Foreman-Proposed-By: e-4ux819ad3f4Priyaplan v2 for checkout-redesignmemory/org/projects/checkout-redesign/plan.md
Each run's notes land as one commit in the organization's private memory repository.
Start a project with @Priya, or ask one person with @Name. Try one:
Illustrative. In the app, Priya's plans, questions and held actions read the same way.
Commands and events
Waiting for fm:kit events…