fb-lane-coordination

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 concurrent Codex work needs board-aware FB lanes, locks, handoffs, and Product integration.

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.

Use when product unknowns need research, experiments, competitor evidence, opportunity evidence, or feasibility evidence before implementation is approved.

FB Business lane for Codex. Use for positioning, onboarding copy, pricing, marketing text, help content, FAQs, and audience/business decisions. Read-only on application code.

FB Design lane for Codex. Use for UI/UX questions, icons, styling plans, layout critique, typography, responsive behavior, visual QA plans, screenshots, and BFM execution context. Avoid backend logic.

FB Tech lane for Codex. Use for technical questions, backend/API/schema/auth/integration plans, test strategy, reliability review, and BFM execution context. Avoid UI styling and product copy.