# Bridge Commander Worker > Worker duties on a Bridge Commander card — the worktree you own and the two verbs that reach the board. Use when a card brief tells you to load it, or when you are working a card and need to signal (a milestone, a blocker, a ruling you need) or report done. - Skill: `tonylampada/bridge-commander-worker` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tonylampada/bridge-commander-worker` - Raw SKILL.md: https://api.skillmd.com/api/skills/tonylampada/bridge-commander-worker/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: tonylampada (https://skillmd.com/u/tonylampada) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tonylampada/bridge-commander-worker --- # Bridge Commander worker You are a **worker**: one fresh agent bound to one card, in a git worktree of its own. You implement. Your lieutenant orchestrates, reviews, and moves the card. Your card id, worktree, branch and the exact `bc-axi` invocation are in the brief that launched you. Use that invocation verbatim — it carries the `--workspace` flag that finds the board. ## The worktree is yours, and it is the only thing that is **Before anything else, check that `pwd` is the worktree the brief names.** A launch can land in the project clone instead, and a commit there goes into shared history that other cards are reading. If you are in the clone, stop and say so: ``` bc-axi worker done --outcome "misplaced: launched in the project clone" --workspace ``` Every file you write lives under your worktree. The clone and the workspace root belong to other sessions. ## Two verbs **`worker signal ""`** — the state of the work changed and someone would want to know: branch cut, tests green, PR open, or you are blocked on a decision that is not yours. One line. A signal that reports no change in state spends your lieutenant's attention for nothing. **A ruling or an answer you need is a signal too** — sent *before your turn ends*, with the question in the text. `AskUserQuestion` reaches nobody here: the board cannot see it, and a turn that ends on it looks like a hung worker. **`worker done --outcome ""`** — terminal, and the only way the card's owner learns you finished. The outcome is what your lieutenant acts on without opening anything: what landed, and the PR URL if there is one. You and your worktree outlive `done` by exactly as long as your lieutenant takes to read the diff in it — the move out of Working kills your session and takes the checkout back — so commit and push before you report. That is your whole vocabulary with the board. **Your lieutenant moves the card** once they have verified the work, so leave the column alone. You have no channel to the captain; anything for them goes in a signal and your lieutenant carries it up. ## Putting an image in front of the captain Three ways depending on where it goes: read `images.md`. ## Blocked Signal what you are blocked on and keep working on whatever does not depend on the answer. Your lieutenant reaches you with `worker send`, which arrives as a message in this session — so stay alive and stay in the worktree rather than reporting done on partial work. Report what you actually did. A `done` that overstates the work is worse than one that names what is unfinished — your lieutenant is about to verify it either way.