<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/context/naming-decision-tool-vs-agent/">
  <id>https://docs.spec-kitty.ai/context/naming-decision-tool-vs-agent/</id>
  <title>Naming Decision: Tool vs Agent</title>
  <updated>2026-11-13T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/context/naming-decision-tool-vs-agent/"/>
  <summary>The canonical naming decision separating tool (the concrete execution product) from agent (the logical collaborator identity and role) across Spec Kitty.</summary>
  <content type="html">&lt;span id=&quot;naming-decision-tool-vs-agent&quot;&gt;&lt;/span&gt;
&lt;p&gt;&lt;strong&gt;Decision date&lt;/strong&gt;: 2026-02-15
&lt;strong&gt;Status&lt;/strong&gt;: Agreed and active&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Tool&lt;/strong&gt;: concrete execution product (Claude Code, Codex, opencode, etc.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agent&lt;/strong&gt;: logical collaborator identity/role in the workflow&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;why&quot;&gt;Why&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Avoids overloaded wording where one term means both product and role&lt;/li&gt;
&lt;li&gt;Makes event payloads and docs easier to interpret&lt;/li&gt;
&lt;li&gt;Improves cross-tool comparisons in workflow audits&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;usage-rule&quot;&gt;Usage Rule&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use “tool” for install/config/invocation concerns&lt;/li&gt;
&lt;li&gt;Use “agent” for assignment/handoff/role concerns&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;derived-terms&quot;&gt;Derived Terms&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Tool surface&lt;/strong&gt;: installable, verifiable, or packageable artifact/configuration exposed to a concrete tool (for example a slash command file, skill directory, hook config, MCP config, custom agent profile file, or plugin manifest)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agent profile&lt;/strong&gt;: logical collaborator identity/role guidance projected into a tool-native custom-agent/subagent format when supported&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;compatibility-note&quot;&gt;Compatibility Note&lt;/h2&gt;
&lt;p&gt;Some existing CLI commands and config keys still use historical names such as &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;agents.available&lt;/code&gt;. New architecture, docs, and schemas should treat those as compatibility aliases for configured tools, not as permission to use “agent” for install/config concepts.&lt;/p&gt;</content>
</entry>
