Foreman kit · component 7 of 8
Kit: BlueprintDesk
“Draw the blueprint” as a widget: tap the sentence, watch the plan redraw, then run it to your gate. Every action prints below; the buttons drive the desks from outside.
Defaults <BlueprintDesk />
Sheet A-101 Try it here
Draw the blueprint
Say who does what. The plan redraws as you go: every step a room, every loop a dimension with its bound, your gate a door. Then press Run it and walk the crew through. Simulated here, step for step as a flow runs in Foreman.
The architect plans, the developer builds, the checks run until green, at most 4 rounds, the QA engineer reviews until clean, and I approve before a draft PR.
Tap any underlined part to change it.
Who plans?
Who builds?
How many rounds may the checks take?
Who reviews?
Where do you step in?
A flow of your own. Closest built-in: research-then-implement. Ask the assistant and it drafts this file for you.
Ready · 7 rooms · 3 loops · 1 gate
.foreman/flows/my-blueprint.tomlSimplified for this page# .foreman/flows/my-blueprint.toml · simplified for this page
name = "My blueprint"
description = "The architect plans, the developer builds, the checks run until green, at most 4 rounds, the QA engineer reviews until clean, and I approve before a draft PR."
[inputs]
task = "The issue to resolve: its link or its words"
[start]
step = "plan"
[steps.plan]
kind = "turn"
persona = "architect" # read-only: plans, never edits
prompt = "Research how to do this and write a plan. Don't change any files yet. {{task}}"
context = ["task", "tree"]
[steps.implement]
kind = "turn" # code steps run on Claude Code
persona = "developer"
loadout = 1
prompt = "Implement the plan."
context = ["plan.answer"]
[steps.checks]
kind = "checks" # the repo's approved check commands, never an agent
[steps.fix]
kind = "turn"
same_tab = "implement"
prompt = "Address what failed or what you were sent back for, and run the checks again."
context = ["checks.results"]
[steps.review]
kind = "review" # read-only: Claude Code or Codex
persona = "qa-engineer"
# its default loadout 3 is Codex
context = ["diff"]
[steps.address]
kind = "turn"
same_tab = "implement"
context = ["review.findings"]
[steps.pr-check]
kind = "gate" # you: Continue, Send back or Stop
show = ["diff", "checks.results", "review.findings"]
ask = "Open a draft PR?"
[steps.pr]
kind = "pr" # Foreman pushes and opens it, no agent
draft = true
body = "{{ledger}}"
[steps.ci]
kind = "wait"
on = "ci"
[steps.fix-ci]
kind = "turn"
same_tab = "implement"
prompt = "CI failed on the pull request. Fix it, commit and push."
[edges]
plan = "implement"
implement = "checks"
checks = { passed = "review", failed = "fix" }
fix = "checks"
review = { clean = "pr-check", findings = "address" }
address = "checks"
pr-check = { continued = "pr", sent-back = "address", stopped = "done" }
pr = { opened = "ci" }
ci = { green = "done", none = "done", failed = "fix-ci" }
fix-ci = "ci"
[loops.fix-until-green]
over = ["checks", "fix"]
at_most = { iterations = 4, minutes = 45 }
iteration = "same-tab" # or "compact-when-full" or "fresh-with-summary"
[loops.review-until-clean]
over = ["review", "address", "checks"]
at_most = { iterations = 2 }
[loops.ci-until-green]
over = ["ci", "fix-ci"]
at_most = { iterations = 2 }
[after]
workspace = "keep" # keep | archive | delete-unchanged- Project
- atlas
- Flow
my-blueprint- Drawn by
- the assistant
- Checked by
- you
- Revisions
- A first drawn
Scale: 1 step = 1 room · persona hats drawn for this page
Site log fix-login-redirect
- 00:08architect: a 3-step plan · the cookie is set after the redirect in src/auth/session.ts
- 00:45developer: moved the redirect after setSession() · +12 −3
- 01:22checks: ✕ auth/redirect.test.ts › keeps returnTo after sign-in
- 01:59developer (fix, same tab): kept returnTo on the refresh path · +4 −1
- 02:36checks: ✓ 214 tests · types · lint
- 03:13qa-engineer: clean, no findings
- 03:50pr-check: waiting for you · open a draft PR?
Illustrative run of the sentence above. In Foreman the Flow tab draws it live and the gate waits in Needs you. Flows are experimental: turn them on in Settings → Experimental → Flows.
Legend
- A room is a step: a turn, checks, a review, a gate or a PR
- A loop, with its bound and the fact that sends it round
- Sent back from your gate, with your note
- Your gate is a door: nothing passes until you open it
- The job, walking from room to room on a run
Night theme, from a built-in flow preset="two-reviewers" heading="…"
Sheet B-2 Night shift
Two reviewers, drawn
Say who does what. The plan redraws as you go: every step a room, every loop a dimension with its bound, your gate a door. Then press Run it and walk the crew through. Simulated here, step for step as a flow runs in Foreman.
Skip the plan, the developer builds, the checks run until green, at most 4 rounds, the QA engineer and the security reviewer review until both are clean, and I approve before it ships.
Tap any underlined part to change it.
Who plans?
Who builds?
How many rounds may the checks take?
Who reviews?
Where do you step in?
Matches the built-in flow two-reviewers.
Ready · 5 rooms · 2 loops · 1 gate
.foreman/flows/two-reviewers.tomlSimplified for this page# .foreman/flows/two-reviewers.toml · simplified for this page
name = "Two reviewers must agree"
description = "Skip the plan, the developer builds, the checks run until green, at most 4 rounds, the QA engineer and the security reviewer review until both are clean, and I approve before it ships."
[inputs]
task = "What to build or fix"
[start]
step = "implement"
[steps.implement]
kind = "turn" # code steps run on Claude Code
persona = "developer"
loadout = 1
prompt = "{{task}}"
[steps.checks]
kind = "checks" # the repo's approved check commands, never an agent
[steps.fix]
kind = "turn"
same_tab = "implement"
prompt = "Address what failed or what you were sent back for, and run the checks again."
context = ["checks.results"]
[steps.review-quality]
kind = "review" # read-only: Claude Code or Codex
persona = "qa-engineer"
# its default loadout 3 is Codex
context = ["diff"]
[steps.review-security]
kind = "review" # read-only: Claude Code or Codex
persona = "security-reviewer"
context = ["diff"]
[steps.address-quality]
kind = "turn"
same_tab = "implement"
context = ["review-quality.findings"]
[steps.address-security]
kind = "turn"
same_tab = "implement"
context = ["review-security.findings"]
[steps.ship-check]
kind = "gate" # you: Continue, Send back or Stop
show = ["diff", "checks.results", "review-quality.findings", "review-security.findings"]
ask = "Is this ready to ship?"
[edges]
implement = "checks"
checks = { passed = "review-quality", failed = "fix" }
fix = "checks"
review-quality = { clean = "review-security", findings = "address-quality" }
review-security = { clean = "ship-check", findings = "address-security" }
address-quality = "checks"
address-security = "checks"
ship-check = { continued = "done", sent-back = "address-quality", stopped = "done" }
[loops.fix-until-green]
over = ["checks", "fix"]
at_most = { iterations = 4, minutes = 45 }
iteration = "same-tab" # or "compact-when-full" or "fresh-with-summary"
[loops.until-both-agree]
over = ["review-quality", "review-security", "address-quality", "address-security", "checks"]
at_most = { iterations = 3 }
[after]
workspace = "keep" # keep | archive | delete-unchanged- Project
- atlas
- Flow
two-reviewers- Drawn by
- the assistant
- Checked by
- you
- Revisions
- A first drawn
Scale: 1 step = 1 room · persona hats drawn for this page
Site log fix-login-redirect
- 00:08developer: moved the redirect after setSession() · +12 −3
- 00:45checks: ✕ auth/redirect.test.ts › keeps returnTo after sign-in
- 01:22developer (fix, same tab): kept returnTo on the refresh path · +4 −1
- 01:59checks: ✓ 214 tests · types · lint
- 02:36qa-engineer: clean, no findings
- 03:13security-reviewer: clean, no findings
- 03:50ship-check: waiting for you · ready to ship?
Illustrative run of the sentence above. In Foreman the Flow tab draws it live and the gate waits in Needs you. Flows are experimental: turn them on in Settings → Experimental → Flows.
Legend
- A room is a step: a turn, checks, a review, a gate or a PR
- A loop, with its bound and the fact that sends it round
- Sent back from your gate, with your note
- Your gate is a door: nothing passes until you open it
- The job, walking from room to room on a run
Compact, in a narrow column compact preset="fix-until-green" heading={false}
Compact stacks the brief over the sheet at any width and drops the legend, the phone and the title block's extra cells. The site log stays, shorter.
Skip the plan, the developer builds, the checks run until green, at most 4 rounds, the QA engineer reviews until clean, and I approve before it ships.
Tap any underlined part to change it.
Who plans?
Who builds?
How many rounds may the checks take?
Who reviews?
Where do you step in?
Matches the built-in flow fix-until-green.
Ready · 4 rooms · 2 loops · 1 gate
.foreman/flows/fix-until-green.tomlSimplified for this page# .foreman/flows/fix-until-green.toml · simplified for this page
name = "Fix until green"
description = "Skip the plan, the developer builds, the checks run until green, at most 4 rounds, the QA engineer reviews until clean, and I approve before it ships."
[inputs]
task = "What to build or fix"
[start]
step = "implement"
[steps.implement]
kind = "turn" # code steps run on Claude Code
persona = "developer"
loadout = 1
prompt = "{{task}}"
[steps.checks]
kind = "checks" # the repo's approved check commands, never an agent
[steps.fix]
kind = "turn"
same_tab = "implement"
prompt = "Address what failed or what you were sent back for, and run the checks again."
context = ["checks.results"]
[steps.review]
kind = "review" # read-only: Claude Code or Codex
persona = "qa-engineer"
# its default loadout 3 is Codex
context = ["diff"]
[steps.address]
kind = "turn"
same_tab = "implement"
context = ["review.findings"]
[steps.ship-check]
kind = "gate" # you: Continue, Send back or Stop
show = ["diff", "checks.results", "review.findings"]
ask = "Is this ready to ship?"
[edges]
implement = "checks"
checks = { passed = "review", failed = "fix" }
fix = "checks"
review = { clean = "ship-check", findings = "address" }
address = "checks"
ship-check = { continued = "done", sent-back = "address", stopped = "done" }
[loops.fix-until-green]
over = ["checks", "fix"]
at_most = { iterations = 4, minutes = 45 }
iteration = "same-tab" # or "compact-when-full" or "fresh-with-summary"
[loops.review-until-clean]
over = ["review", "address", "checks"]
at_most = { iterations = 2 }
[after]
workspace = "keep" # keep | archive | delete-unchanged- Project
- atlas
- Flow
fix-until-green- Drawn by
- the assistant
- Checked by
- you
- Revisions
- A first drawn
Scale: 1 step = 1 room · persona hats drawn for this page
Site log fix-login-redirect
- 00:08developer: moved the redirect after setSession() · +12 −3
- 00:45checks: ✕ auth/redirect.test.ts › keeps returnTo after sign-in
- 01:22developer (fix, same tab): kept returnTo on the refresh path · +4 −1
- 01:59checks: ✓ 214 tests · types · lint
- 02:36qa-engineer: clean, no findings
- 03:13ship-check: waiting for you · ready to ship?
Illustrative run of the sentence above. In Foreman the Flow tab draws it live and the gate waits in Needs you. Flows are experimental: turn them on in Settings → Experimental → Flows.
Legend
- A room is a step: a turn, checks, a review, a gate or a PR
- A loop, with its bound and the fact that sends it round
- Sent back from your gate, with your note
- Your gate is a door: nothing passes until you open it
- The job, walking from room to room on a run
Events and commands
Events appear here.