Skip to content

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.

    Starts
    When you @Priya
    Access
    Writes project filesNo shellSlack · held
  • Ravi

    Staff software engineer

    Builds and fixes features, with tests, on its own branch.

    Starts
    When you askWhen assigned in Linear
    Access
    Write · atlasNo shellPush & PR · heldSlack & Linear · held
  • Uma

    Staff UX designer

    Reviews screens and flows, specifies what to build and draws it as mocks.

    Starts
    When you askWhen review is requested
    Access
    Write · atlasNo shellPush & PR · heldSlack & Linear · held
  • Quinn

    Staff QA engineer

    Reviews what others build and says what breaks.

    Starts
    When you askWhen review is requested
    Access
    Write · atlasNo shellPush & PR · heldSlack & Linear · held

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.

    Starts
    When you @Priya
    Access
    Writes project filesNo shellSlack · held
  • Mei

    Staff frontend engineer

    Builds screens and components and keeps them accessible.

    Starts
    When you askWhen review is requested
    Access
    Write · atlasNo shellPush & PR · heldSlack & Linear · held
  • Sam

    Staff SEO specialist

    Audits the site for search and suggests fixes.

    Starts
    When you askEvery Monday 09:00
    Access
    Write · atlasNo shellPush & PR · heldSlack & Linear · held
  • Quinn

    Staff QA engineer

    Reviews what others build and says what breaks.

    Green is Sam's hat, so Quinn wears orange.

    Starts
    When you askWhen review is requested
    Access
    Write · atlasNo shellPush & PR · heldSlack & Linear · held

acme Acme's channel · atlas

  1. You

    @Priya add passkey sign-in to atlas

  2. 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.

  3. You

    Keep both. Yes, Safari too.

  4. 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.

    1. 1Spec the passkey screens, two mock optionsMeispec.md
    2. 2Test plan for Chrome and SafariQuinntest-plan.md
    3. 3Build it, run the plan, pushMeibuild.md
  5. You approved plan v1 · Mei and Quinn start in order
  6. Mei

    Built passkey sign-in on passkey-sign-in from 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.

  7. Needs you · Push · Mei · just now

    Push passkey-sign-in to atlas

    3 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

acme-memory

git log --format='%h %an %s' -- memory/

  1. c41f9e2Quinnlearned the test DB must be reset before e2ememory/bots/e-9q4c/MEMORY.md
  2. 7d02b11Youkept Uma's proposal: every screen works at 390pxmemory/org/PROJECT.md · Foreman-Proposed-By: e-4ux8
  3. 19ad3f4Priyaplan 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.

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.

    Starts
    When you @Priya
    Access
    Writes project filesNo shellSlack · held
  • Ravi

    Staff software engineer

    Builds and fixes features, with tests, on its own branch.

    Starts
    When you askWhen assigned in Linear
    Access
    Write · atlasNo shellPush & PR · allowedSlack & Linear · held
  • Theo

    Staff technical writer

    Writes the docs and keeps them up to date.

    Starts
    When you askWhen a PR merges
    Access
    Write · atlasNo shellPush & PR · allowedSlack & Linear · held

acme Acme's channel · atlas

  1. You

    @Priya add passkey sign-in to atlas

  2. 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.

  3. You

    Keep both. Yes, Safari too.

  4. 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.

    1. 1Spec the passkey screens, two mock optionsUma proposedspec.md
    2. 2Test plan for Chrome and SafariQuinn proposedtest-plan.md
    3. 3Build it, run the plan, pushRavibuild.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.

  5. You approved plan v1 and Uma and Quinn · Uma, Quinn and Ravi start in order
  6. Ravi

    Built passkey sign-in on passkey-sign-in from 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.

  7. Decided for you · Ravi pushed passkey-sign-in (3 commits), allowed by Ravi's rule. It can't be undone.

acme-memory

git log --format='%h %an %s' -- memory/

  1. c41f9e2Quinnlearned the test DB must be reset before e2ememory/bots/e-9q4c/MEMORY.md
  2. 7d02b11Youkept Uma's proposal: every screen works at 390pxmemory/org/PROJECT.md · Foreman-Proposed-By: e-4ux8
  3. 19ad3f4Priyaplan 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.

Illustrative. In the app, Priya's plans, questions and held actions read the same way.

Commands and events

Waiting for fm:kit events…