Menu
Use when concurrent Codex work needs board-aware FB lanes, locks, handoffs, and Product integration.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when Product/Captain must sequence, execute, reconcile, or close approved FB handoffs.
Coordinates board-aware FB tasks, handoffs, staging submissions, and Product/BFM integration.
Use when Product must scope, prioritize, reconcile lane handoffs, approve a build brief, or own release gates.
Use when bootstrapping an FB-coordinated project with board, handoff, workstream, and harness routes.
Use when a new project needs the smallest practical introduction to FB coordination.
Use when a suspected defect needs reproduction, severity, affected-user impact, or regression evidence before Product prioritizes a fix.
| name | fb-lane |
| description | Use when concurrent Codex work needs board-aware FB lanes, locks, handoffs, and Product integration. |
Read the FB harness, then the project board, handoff index, linked handoff, and relevant workstream card. Publicly, start in whichever workstream matches the question; FB selects any internal routing without asking the user to choose a mode.
The one loop has six planning/evidence workstreams: Product/User (technical slug
product), Business, Design, Tech, Discovery, and Bugs. Each relevant
workstream runs a mini-loop and records a ready or blocked
docs/handoffs/<TASK-ID>.md. Product/User is used only for user/product
questions, not universal intake. After ready handoffs, $bfm activates Product
reconciliation and approved execution. Inactive workstreams receive None relevant only in a required six-workstream scan/report. BFM stops at Ready to ship. Only
Push Live authorizes merge or deployment.
For approval waits or genuine stops, use the canonical beginner pause card in
guardrails.md; keep internal evidence in durable records unless the user must
judge it.
PROJECT_BOARD.md is truth; docs/handoffs/index.md is routing; detailed
handoffs are detail. Ordinary lanes plan only. Use node tools/fb-lane.cjs status to inspect current coordination state; claims and source changes occur
only in an approved Product-launched BFM run.
Selected evals never self-promote and never replace Product or user judgment.
