<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/guides/how-to/harnesses/pi-tui/">
  <id>https://docs.spec-kitty.ai/guides/how-to/harnesses/pi-tui/</id>
  <title>Use Spec Kitty in Pi TUI</title>
  <updated>2026-10-21T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/guides/how-to/harnesses/pi-tui/"/>
  <summary>How to use Spec Kitty in Pi TUI (partial tier): command-skill packages install in 3.2, but real-session smoke evidence is not yet recorded.</summary>
  <content type="html">&lt;span id=&quot;use-spec-kitty-in-pi-tui&quot;&gt;&lt;/span&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Tier:&lt;/strong&gt; &lt;strong&gt;partial&lt;/strong&gt; — Spec Kitty installs Pi command-skill packages in 3.2, but real-session smoke evidence is not yet recorded.
&lt;strong&gt;Citation (accessed 2026-05-21):&lt;/strong&gt; &lt;a href=&quot;https://pi.dev/docs/latest/skills&quot;&gt;https://pi.dev/docs/latest/skills&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;partial-tier-note&quot;&gt;Partial-tier note&lt;/h2&gt;
&lt;p&gt;Pi TUI is classified &lt;code dir=&quot;auto&quot;&gt;partial&lt;/code&gt; in the 3.2 &lt;a href=&quot;/api/supported-harnesses/&quot;&gt;support matrix&lt;/a&gt; because:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The Spec Kitty installer produces command-skill packages under &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty-*/SKILL.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Pi’s current skills documentation says project &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; directories are discovered, and that skills register as &lt;code dir=&quot;auto&quot;&gt;/skill:&amp;#x3C;name&gt;&lt;/code&gt; commands.&lt;/li&gt;
&lt;li&gt;A real-session smoke test for the complete Spec Kitty command set has not yet been recorded, so the row remains &lt;code dir=&quot;auto&quot;&gt;partial&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;supported&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Promotion to &lt;code dir=&quot;auto&quot;&gt;supported&lt;/code&gt; requires at least one documented smoke test against a real Pi session; the full rule is maintained in &lt;code dir=&quot;auto&quot;&gt;docs/development/3-2-harness-research-method.md&lt;/code&gt; §6.&lt;/p&gt;
&lt;h2 id=&quot;prerequisites&quot;&gt;Prerequisites&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Spec Kitty CLI installed.&lt;/strong&gt; See &lt;a href=&quot;/guides/how-to/installation/install-spec-kitty/&quot;&gt;Install Spec Kitty&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project initialized for this harness:&lt;/strong&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;init&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--ai&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;pi&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Pi installed.&lt;/strong&gt; Follow the Pi documentation at &lt;a href=&quot;https://pi.dev/docs/latest&quot;&gt;https://pi.dev/docs/latest&lt;/a&gt; for the current install path and authentication flow.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;where-spec-kitty-installs-files&quot;&gt;Where Spec Kitty installs files&lt;/h2&gt;
&lt;p&gt;Per the &lt;a href=&quot;/api/supported-harnesses/&quot;&gt;supported-harnesses matrix&lt;/a&gt;, Pi consumes Spec Kitty as agent skills. Spec Kitty installs:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Directory:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty-&amp;#x3C;command&gt;/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Files:&lt;/strong&gt; one &lt;code dir=&quot;auto&quot;&gt;SKILL.md&lt;/code&gt; per command (&lt;code dir=&quot;auto&quot;&gt;spec-kitty-specify/SKILL.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-plan/SKILL.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-tasks/SKILL.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-implement/SKILL.md&lt;/code&gt;, etc.).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Manifest:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.kittify/command-skills-manifest.json&lt;/code&gt; records that Pi references each command-skill package.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Runtime ignore entry:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.pi/&lt;/code&gt; is added to &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; when Pi is configured.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The shared &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; tree can be co-owned by Codex, Vibe, Pi, Letta, and Antigravity. Do not copy or edit the generated &lt;code dir=&quot;auto&quot;&gt;SKILL.md&lt;/code&gt; files manually; use &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config sync&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to refresh them.&lt;/p&gt;
&lt;p&gt;Before the 4.0.0rc8 release these folders were named &lt;code dir=&quot;auto&quot;&gt;spec-kitty.&amp;#x3C;command&gt;&lt;/code&gt;. The Agent Skills specification does not allow a dot in a skill name, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; renames them; see &lt;a href=&quot;/migrations/command-skill-hyphen-names/&quot;&gt;Command skills renamed for the Agent Skills specification&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;canonical-invocation&quot;&gt;Canonical invocation&lt;/h2&gt;
&lt;p&gt;Pi’s skills documentation says skills register as &lt;code dir=&quot;auto&quot;&gt;/skill:&amp;#x3C;name&gt;&lt;/code&gt; commands. For Spec Kitty command-skill packages, use that form:&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;text&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;/skill:spec-kitty-specify &quot;&amp;#x3C;one-line mission description&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;/skill:spec-kitty-plan&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;/skill:spec-kitty-tasks&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;/skill:spec-kitty-implement WP01&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;h2 id=&quot;worked-example&quot;&gt;Worked example&lt;/h2&gt;
&lt;p&gt;Until full smoke evidence lands, treat Pi TUI as a &lt;strong&gt;partial-tier&lt;/strong&gt; host and verify command behavior on a low-risk mission first:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;From your project root, run Pi.&lt;/li&gt;
&lt;li&gt;At the prompt, type:
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;text&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;/skill:spec-kitty-specify &quot;a hello world page&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;Answer the Spec Kitty interview prompts inline.&lt;/li&gt;
&lt;li&gt;When asked for a kebab-case slug, supply something short, e.g. &lt;code dir=&quot;auto&quot;&gt;hello-world-page&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The mission spec lands at &lt;code dir=&quot;auto&quot;&gt;kitty-specs/hello-world-page-&amp;#x3C;mid8&gt;/spec.md&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If Pi does not expose the command in your installed version, the artifacts remain harness-agnostic:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Drive the mission lifecycle through another configured harness (for example, Claude Code: &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify &quot;a hello world page&quot;&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;The mission spec lands at &lt;code dir=&quot;auto&quot;&gt;kitty-specs/hello-world-page-&amp;#x3C;mid8&gt;/spec.md&lt;/code&gt; on disk.&lt;/li&gt;
&lt;li&gt;Open Pi TUI against the same project directory and inspect the &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; tree as plain files.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;troubleshooting&quot;&gt;Troubleshooting&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;No &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.*&lt;/code&gt; commands inside Pi TUI.&lt;/strong&gt;
Expected — Pi is a skill host, not a slash-command host for Spec Kitty. Use &lt;code dir=&quot;auto&quot;&gt;/skill:spec-kitty-&amp;#x3C;command&gt;&lt;/code&gt; and confirm &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty-*/SKILL.md&lt;/code&gt; exists.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Profile not loading.&lt;/strong&gt;
The &lt;code dir=&quot;auto&quot;&gt;/spk-charter-profile-load&lt;/code&gt; workflow assumes a slash-command host. If your Pi build does not expose equivalent profile loading, use the helper from your other configured harness and reuse the same &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/&lt;/code&gt; tree.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;where-to-learn-more-about-pi-tui&quot;&gt;Where to learn more about Pi TUI&lt;/h2&gt;
&lt;p&gt;Authoritative documentation: &lt;a href=&quot;https://pi.dev/docs/latest/skills&quot;&gt;https://pi.dev/docs/latest/skills&lt;/a&gt; (accessed 2026-05-21). The matrix row in &lt;a href=&quot;/api/supported-harnesses/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/api/supported-harnesses.md&lt;/code&gt;&lt;/a&gt; remains the promotion tracker.&lt;/p&gt;</content>
</entry>
