<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/development/agent-fleet/">
  <id>https://docs.spec-kitty.ai/development/agent-fleet/</id>
  <title>The SkyKitty Agent Fleet</title>
  <updated>2026-10-19T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/development/agent-fleet/"/>
  <summary>SkyKitty, the Spec Kitty company agent fleet: its roles and the ready-for-squad handshake that hands a PR from the implementer to the review squad and CI.</summary>
  <content type="html">&lt;span id=&quot;the-skykitty-agent-fleet&quot;&gt;&lt;/span&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Status (2026-10-19): the fleet is switched off.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;CI Fleet Verdict&lt;/code&gt; workflow
(&lt;code dir=&quot;auto&quot;&gt;.github/workflows/ci-fleet-verdict.yml&lt;/code&gt;) is disabled; its last run was 2026-09-26.
The PR-lane labels (&lt;code dir=&quot;auto&quot;&gt;squad:*&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;needs:implementer&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ci:green&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;ci:red&lt;/code&gt;) were deleted
from the tracker. &lt;code dir=&quot;auto&quot;&gt;ready-for-squad&lt;/code&gt;, the issue-side &lt;code dir=&quot;auto&quot;&gt;status:*&lt;/code&gt; labels and
&lt;code dir=&quot;auto&quot;&gt;taken-by-human&lt;/code&gt; remain, as human workflow state (see
&lt;a href=&quot;/development/how-to/manage-issue-tracker/#issue-workflow-state-labels&quot;&gt;Managing the Issue Tracker → Issue workflow-state labels&lt;/a&gt;).
This page describes the fleet as it worked while active.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;SkyKitty&lt;/strong&gt; is the proper name of the Spec Kitty &lt;strong&gt;company agent fleet&lt;/strong&gt; — the set of
governed AI agents that execute missions on this repository under an &lt;strong&gt;operator&lt;/strong&gt; who
stays human-in-command. The charter’s Collaboration Strategy already governs how the
operator and the fleet divide the work (see the &lt;a href=&quot;/context/charter-overview/&quot;&gt;charter overview&lt;/a&gt;);
this page names the fleet, enumerates the roles inside it, and documents the tracker
signals — chiefly the &lt;code dir=&quot;auto&quot;&gt;ready-for-squad&lt;/code&gt; label — through which those roles hand work to one
another.&lt;/p&gt;
&lt;h2 id=&quot;skykitty-is-the-fleet-spec-kitty-is-the-toolkit&quot;&gt;SkyKitty is the fleet; Spec Kitty is the toolkit&lt;/h2&gt;
&lt;p&gt;Keep the two terms distinct:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Spec Kitty&lt;/strong&gt; is the toolkit — the CLI, the templates, the doctrine, the runtime that
drives the specify → plan → tasks → implement → review → merge loop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SkyKitty&lt;/strong&gt; is the &lt;strong&gt;fleet of agents that operate &lt;em&gt;with&lt;/em&gt; Spec Kitty&lt;/strong&gt; — the crew the
operator dispatches to run those missions. The charter’s shorthand for the same thing is
“the fleet” / “fleet agents”; &lt;strong&gt;SkyKitty&lt;/strong&gt; is that fleet’s proper name.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Team Kitty&lt;/strong&gt; is a third, unrelated Kitty-branded noun: the &lt;strong&gt;hosted SaaS product&lt;/strong&gt;
(CLI → Zeitgeist relay → Team Kitty Pulse projection). It is neither the toolkit nor the
fleet — see &lt;a href=&quot;/context/team-kitty/&quot;&gt;Team Kitty and Zeitgeist&lt;/a&gt;. The tool-vs-agent split
behind these names is the &lt;a href=&quot;/context/naming-decision-tool-vs-agent/&quot;&gt;tool-vs-agent naming decision&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The operator is not part of the fleet. SkyKitty executes; the operator commands, sets
scope, and performs the mainline merge (see &lt;a href=&quot;#roles-in-the-fleet&quot;&gt;Roles&lt;/a&gt;).&lt;/p&gt;
&lt;h2 id=&quot;roles-in-the-fleet&quot;&gt;Roles in the fleet&lt;/h2&gt;
&lt;p&gt;A mission is run by several governed profiles, each &lt;strong&gt;profile-LOADED&lt;/strong&gt; (its doctrine
context resolved and injected), never merely a persona name. One agent may wear more than
one role across a mission, but the roles stay distinct and, where independence is required,
are held by different agents.&lt;/p&gt;















































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Role&lt;/th&gt;&lt;th&gt;Who&lt;/th&gt;&lt;th&gt;What they own&lt;/th&gt;&lt;th&gt;What they must not do&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Operator&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Human-in-command&lt;/td&gt;&lt;td&gt;Delegates the mission, sets and approves scope, performs the &lt;strong&gt;mainline merge&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Orchestrator&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Governed profile (e.g. &lt;code dir=&quot;auto&quot;&gt;planner-priti&lt;/code&gt; for planning/tracker work)&lt;/td&gt;&lt;td&gt;Claims the mission’s tickets, plans (spec → plan → tasks with an adversarial squad at each planning point-cut), runs the implement → review loop&lt;/td&gt;&lt;td&gt;Merge to mainline&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Implementer&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Governed profile, in an isolated worktree&lt;/td&gt;&lt;td&gt;Builds the work package, runs the required tests + self-review, labels the PR &lt;code dir=&quot;auto&quot;&gt;ready-for-squad&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Merge; review its own work&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Review / adversarial squad&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Independent profile-loaded lenses (reviewer ≠ implementer)&lt;/td&gt;&lt;td&gt;Squad review of the aggregate diff&lt;/td&gt;&lt;td&gt;Implement the change it reviews&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;CI / fleet agents&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Fleet&lt;/td&gt;&lt;td&gt;Continuous integration; CI is the authoritative release gate&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Merge agent&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Fleet profile&lt;/td&gt;&lt;td&gt;Local lane consolidation and the fleet-side integration mechanics&lt;/td&gt;&lt;td&gt;Publish to origin/&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; without the operator&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Two invariants bind every role:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Implementers never merge — agent consolidates, operator publishes.&lt;/strong&gt; The overloaded
term &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; has three senses (see the
&lt;a href=&quot;/context/orchestration/#lane-consolidation&quot;&gt;orchestration glossary&lt;/a&gt;); keep them
apart here. The fleet owns CI, squad review, and the merge &lt;em&gt;mechanics&lt;/em&gt; — the merge agent
runs &lt;strong&gt;lane consolidation&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; → &lt;strong&gt;local&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; only, never origin).
The &lt;strong&gt;operator, not an agent, performs the mainline merge&lt;/strong&gt; — in the glossary’s terms the
&lt;strong&gt;publish to origin/&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;&lt;/strong&gt; (directive &lt;code dir=&quot;auto&quot;&gt;045-prs-only-and-read-intent&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reviewer ≠ implementer.&lt;/strong&gt; Squad review is independent of the agent that wrote the code.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the mechanics of how a governed profile is dispatched, its doctrine context injected,
and its work tracked as an Op, see
&lt;a href=&quot;/architecture/governed-profile-invocation/&quot;&gt;Understanding Governed Profile Invocation&lt;/a&gt;
and &lt;a href=&quot;/architecture/multi-agent-orchestration/&quot;&gt;Multi-Agent Orchestration&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;the-ready-for-squad-handshake&quot;&gt;The &lt;code dir=&quot;auto&quot;&gt;ready-for-squad&lt;/code&gt; handshake&lt;/h2&gt;
&lt;p&gt;The fleet coordinates through the tracker, not through side channels. The load-bearing
signal is the &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;ready-for-squad&lt;/code&gt;&lt;/strong&gt; label, which hands a pull request from the implementer
to the review squad and CI:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Issue branch first.&lt;/strong&gt; Completed mission work is opened from an &lt;code dir=&quot;auto&quot;&gt;issue-&amp;#x3C;n&gt;-&amp;#x3C;slug&gt;&lt;/code&gt;
branch as a pull request targeting &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, with compact, logically-sliced history.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ready only when complete.&lt;/strong&gt; The implementer runs the required tests and a self-review,
then labels the PR &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;ready-for-squad&lt;/code&gt;&lt;/strong&gt;. The label means &lt;em&gt;this PR is finished and
independently testable&lt;/em&gt; — not &lt;em&gt;please start looking&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The fleet takes over.&lt;/strong&gt; Once the PR carries &lt;code dir=&quot;auto&quot;&gt;ready-for-squad&lt;/code&gt;, &lt;strong&gt;fleet agents own CI
and squad review&lt;/strong&gt;. The adversarial review squad is the recommended mechanism for the
independent review the charter requires (recommended, never a mandated gate).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The operator merges.&lt;/strong&gt; Implementers never merge; after CI and squad review are
satisfied, the operator performs the mainline merge.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Do not apply &lt;code dir=&quot;auto&quot;&gt;ready-for-squad&lt;/code&gt; to a PR that is still a draft of its intended scope, that
has not had its tests run, or that has not been self-reviewed — the label is the fleet’s
contract that the work is ready to be owned downstream.&lt;/p&gt;
&lt;h3 id=&quot;related-pr-workflow-labels&quot;&gt;Related PR-workflow labels&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;ready-for-squad&lt;/code&gt; is one of the fleet-coordination labels on pull requests. It travels with
the &lt;code dir=&quot;auto&quot;&gt;pr:*&lt;/code&gt; family (&lt;code dir=&quot;auto&quot;&gt;pr:needs-refresh&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pr:needs-revision&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pr:kept-for-reference&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;pr:deferred&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pr:skip-ci&lt;/code&gt;). All of them, together with the
issue-side taxonomy, are documented in
&lt;a href=&quot;/development/how-to/manage-issue-tracker/#label-taxonomy&quot;&gt;Managing the Issue Tracker → Label taxonomy&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;see-also&quot;&gt;See also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/development/how-to/manage-issue-tracker/&quot;&gt;Managing the Issue Tracker&lt;/a&gt; — the full label taxonomy,
including the fleet-coordination labels.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/development/how-to/pr-landing/&quot;&gt;Landing contributor PRs&lt;/a&gt; — the maintainer runbook the fleet and
operator follow to bring a PR onto &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/governed-profile-invocation/&quot;&gt;Understanding Governed Profile Invocation&lt;/a&gt;
— how a fleet agent is dispatched under governance.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/multi-agent-orchestration/&quot;&gt;Multi-Agent Orchestration&lt;/a&gt; — the
host/provider coordination model beneath the fleet.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/context/charter-overview/&quot;&gt;Charter overview&lt;/a&gt; — where the Collaboration Strategy and
Agent Operating Discipline that bind the fleet live.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
