fnl-committee

Installation
SKILL.md

Committee

Two agents from different model families, fresh context, planning in parallel. Contrast is the point.

User's additional context: $ARGUMENTS

When to convene

A committee spends two model families' quota. Convene one after the fnl-coding-router checkpoint leaves the cause open, or when the user asks; it needs the user's yes even when they are away, so the work that depends on it waits. For a design or planning problem, convene one only when its difficulty is very hard; otherwise use fnl-advisor.

Composition

Two members from different model families, read-only: Claude (Claude Code), GPT (Codex) or Gemini (Antigravity Argon). The default pair is Claude and Codex. Each runs at a high reasoning setting on a frontier model for a stuck problem, and on a strong model for a medium planning problem. Add a third member only when the two still disagree after two rounds and the user agrees.

Whichever agent coordinates, the member from its own family runs as its own subagent, or as a session when the analysis needs longer than one turn; the other runs headless as fnl-delegate references/agents.md says. Members the user names win. When one member's agent is out of quota or unreachable, the third family takes its seat; with only one family left, say so and run a single advisor instead (fnl-advisor).

Load the fnl-delegate skill and the host config for the invocation commands. Requires the fnl-delegate skill installed beside this one. When it is missing, tell the user to add it (npx skills add finolabs/finolabs-vibecode --skill fnl-delegate, or install the whole plugin) and stop.

Rules

Installs
2
GitHub Stars
4
First Seen
Nov 3, 2026