<?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/kiro/">
  <id>https://docs.spec-kitty.ai/guides/how-to/harnesses/kiro/</id>
  <title>Use Spec Kitty in Kiro</title>
  <updated>2026-06-03T00: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/kiro/"/>
  <summary>How to use Spec Kitty in Kiro (partial tier): a bootstrap-only surface in 3.2, to be promoted once the full /spec-kitty.* command set is verified end-to-end.</summary>
  <content type="html">&lt;span id=&quot;use-spec-kitty-in-kiro&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; — bootstrap-only surface in 3.2. Promote to &lt;code dir=&quot;auto&quot;&gt;supported&lt;/code&gt; once the full &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.*&lt;/code&gt; set is verified end-to-end.
&lt;strong&gt;Citation (accessed 2026-06-03):&lt;/strong&gt; &lt;a href=&quot;https://kiro.dev/docs&quot;&gt;https://kiro.dev/docs&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&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;kiro&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;Kiro installed and configured.&lt;/strong&gt; Follow the &lt;a href=&quot;https://kiro.dev/docs&quot;&gt;Kiro documentation&lt;/a&gt; for installation and authentication.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;partial-tier-note&quot;&gt;Partial-tier note&lt;/h2&gt;
&lt;p&gt;Kiro is the rebrand-target of Amazon Q. In 3.2 the Spec Kitty installer ships a &lt;strong&gt;bootstrap-only&lt;/strong&gt; surface for Kiro — the directory layout is in place, but the full &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.*&lt;/code&gt; command set is not yet integration-tested end-to-end against this harness. Expect feature parity with Amazon Q at the prompt-file level; verify each command before relying on it for production missions.&lt;/p&gt;
&lt;p&gt;The promotion criteria (&lt;code dir=&quot;auto&quot;&gt;partial → supported&lt;/code&gt;) are 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;plugin-install-classification&quot;&gt;Plugin-install classification&lt;/h2&gt;
&lt;p&gt;Kiro is &lt;strong&gt;prompt-only&lt;/strong&gt; for Spec Kitty 3.3 plugin-install planning. Current
public Kiro docs describe steering files, hooks, MCP configuration, and prompt
surfaces, but do not document a plugin or Powers bundle primitive that Spec
Kitty can install as a packaged command-skill equivalent.&lt;/p&gt;
&lt;p&gt;Spec Kitty therefore keeps Kiro out of #1635 plugin-install scope until an
upstream package primitive is documented and smoke-tested. Continue using the
&lt;code dir=&quot;auto&quot;&gt;.kiro/prompts/&lt;/code&gt; surface for bootstrap coverage.&lt;/p&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;, Kiro uses the prompt-file mechanism. 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;.kiro/prompts/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Files:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;spec-kitty.*&lt;/code&gt; prompt set (specify, plan, tasks, implement, review, accept, merge, status, charter, analyze, research).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;canonical-invocation&quot;&gt;Canonical invocation&lt;/h2&gt;
&lt;p&gt;Inside Kiro, prompts are invoked via the host’s prompt-discovery convention. The current best guess (mirroring Amazon Q) is:&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;plaintext&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;/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;/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;/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;/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;p&gt;If Kiro’s current syntax differs, consult the host docs at &lt;a href=&quot;https://kiro.dev/docs&quot;&gt;https://kiro.dev/docs&lt;/a&gt; for the canonical prompt invocation.&lt;/p&gt;
&lt;h2 id=&quot;worked-example&quot;&gt;Worked example&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;From your project root, launch Kiro.&lt;/li&gt;
&lt;li&gt;At the prompt, attempt:
&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;plaintext&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;/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;If the prompt is recognized, Spec Kitty’s interview prompts appear — answer them inline and pick a kebab-case slug.&lt;/li&gt;
&lt;li&gt;If it is not recognized, fall back to running Spec Kitty from another configured harness (Claude Code, OpenCode, Cursor, etc.) — the on-disk artifacts under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; are harness-agnostic.&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;&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.*&lt;/code&gt; prompts do not appear.&lt;/strong&gt;
Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config sync&lt;/code&gt; from the repo root. This rewrites &lt;code dir=&quot;auto&quot;&gt;.kiro/prompts/&lt;/code&gt; from the canonical source templates. Restart Kiro.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Profile not loading.&lt;/strong&gt;
Run inside Kiro:&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;plaintext&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;/spk-charter-profile-load researcher-robbie&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Use the profile id from the work-package frontmatter.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;where-to-learn-more-about-kiro&quot;&gt;Where to learn more about Kiro&lt;/h2&gt;
&lt;p&gt;Authoritative documentation: &lt;a href=&quot;https://kiro.dev/docs&quot;&gt;https://kiro.dev/docs&lt;/a&gt; (accessed 2026-06-03).&lt;/p&gt;</content>
</entry>
