fnl-coordinator-sessions

Installation
SKILL.md

Coordinator sessions

The session a spec starts in is its coordinator. It works at the level of spec and plan; each task runs in its own app session. Agent choice, briefs, budgets and acceptance follow fnl-delegate; this skill adds the session model around them. 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.

When to coordinate

Coordinate a feature that has three or more user stories, or ten or more tasks in total. A smaller one runs in a single session, because each extra session costs context and quota.

Ownership

  • The coordinator owns the Spec Kit artifacts (spec.md, plan.md, tasks.md, research and review records), task order, the review gate after each user story, and the PR. It writes no application code or tests, however small the edit, and commits the artifacts it changes.
  • Only the coordinator edits tasks.md, including the [X] marks. A task session runs speckit-implement limited to its assigned task IDs and leaves tasks.md untouched, even where the skill says to mark tasks done.
  • One session per task. Tasks of the current phase and story that edit the same files or must land in one commit go to one session together; grouping never crosses a story boundary.
  • Sessions own tasks. A task or review is always an app session the coordinator starts. A delegated job or subagent never stands in as its owner; a session may delegate to Codex or Antigravity internally, but it still verifies and commits.

Starting sessions

The app starts sessions only on a turn the user's own message began, never on one an automated event or another session began. So:

Installs
2
GitHub Stars
4
First Seen
Nov 3, 2026