Skip to content

Foreman kit · component

Kit: Loadout

“Deal a loadout” from the Crew Cards concept, as a widget. Props, CSS variables, events and commands are documented at the top of src/components/kit/Loadout.astro.

Defaults, on cream

Deal a loadout

Which crew should you send for the job?

Pick a job and Foreman’s dealer hands you a four-card team, with why each card fits. You are always the fourth card.

The job

Loadout for fix flaky tests

  1. DeveloperClaude CodeAgent · Anthropic

    Writes the fix. Flow steps that change code run on Claude Code, the one agent Foreman runs unattended.

  2. ReviewerCodexAgent · OpenAI

    Reads the diff read-only, inside its own sandbox. A flow’s review steps can run on Codex.

  3. Review personaqa-engineerFlow persona · reviewer

    What the reviewer wears: it finds what breaks, never fixes it, and ends with findings.

  4. At the gateYouThe foreman · one of one

    Quarantine the test, keep the fix, or send it back with a note. Nothing ships before you look.

Plays as the built-in flow flaky-test-triage. Flows are experimental and off by default: Settings → Experimental.

Run them side by side in Foreman, each in its own worktree.

Night theme, second instance, three jobs, starts on “Try one task three ways”

The dealer

Who goes out tonight?

Pick a job and Foreman’s dealer hands you a four-card team, with why each card fits. You are always the fourth card.

The job

Loadout for try one task three ways

  1. Workspace osakaClaude CodeAgent · Anthropic

    Takes the prompt in a worktree of its own, on its own branch.

  2. Workspace lisbonCodexAgent · OpenAI

    Same prompt, its own worktree and branch, so nothing collides.

  3. Workspace kyotoCursorAgent · Anysphere

    Same prompt again, as an interactive pair. Foreman reviews what it does.

  4. The judgeYouThe foreman · one of one

    Read the three diffs side by side in Tiles and keep the one you like. Nothing merges by itself.

No flow needed: three workspaces, one prompt.

Run them side by side in Foreman, each in its own worktree.

Compact

Deal a loadout

Deal a crew

The job

Loadout for security pass before a release

  1. DeveloperClaude CodeAgent · Anthropic

    Builds, then fixes until the checks pass, round after round, within the loop’s bounds.

  2. First reviewqa-engineerFlow persona · reviewer

    Reads the tree first: does the change do what was asked?

  3. Second reviewsecurity-reviewerFlow persona · reviewer

    Reads the same tree for injection, secrets and unsafe defaults. Any finding goes back.

  4. At the gateYouThe foreman · one of one

    Both reviews come back clean, then you look. Nothing leaves before that.

Plays as the built-in flow two-reviewers. Flows are experimental and off by default: Settings → Experimental.

Run them side by side in Foreman, each in its own worktree.

Events

Every fm:kit event, newest first.

Waiting for events…

Commands