<?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/missions/create-plan/">
  <id>https://docs.spec-kitty.ai/guides/how-to/missions/create-plan/</id>
  <title>How to Create a Technical Plan</title>
  <updated>2026-10-04T00: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/missions/create-plan/"/>
  <summary>How to create a technical plan with Spec Kitty 3.2: Use this guide to turn a finished spec into a technical plan with /spec-kitty.plan.</summary>
  <content type="html">&lt;span id=&quot;how-to-create-a-technical-plan&quot;&gt;&lt;/span&gt;
&lt;p&gt;Use this guide to turn a finished spec into a technical plan with &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;prerequisites&quot;&gt;Prerequisites&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;feature&gt;/spec.md&lt;/code&gt; exists&lt;/li&gt;
&lt;li&gt;You are in the repository root checkout&lt;/li&gt;
&lt;li&gt;Planning artifacts stay on the mission’s target branch (current branch by default, or an explicit &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;the-command&quot;&gt;The Command&lt;/h2&gt;
&lt;p&gt;In your agent:&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;/spec-kitty.plan&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Optionally include your stack or architecture preferences in the same message.&lt;/p&gt;
&lt;h2 id=&quot;the-planning-interview&quot;&gt;The Planning Interview&lt;/h2&gt;
&lt;p&gt;The planner asks architecture and non-functional questions. It pauses with &lt;code dir=&quot;auto&quot;&gt;WAITING_FOR_PLANNING_INPUT&lt;/code&gt; until you answer each one.&lt;/p&gt;
&lt;h2 id=&quot;what-gets-created&quot;&gt;What Gets Created&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;feature&gt;/plan.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;feature&gt;/research.md&lt;/code&gt; (if research is required)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;feature&gt;/data-model.md&lt;/code&gt; (when data is involved)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;feature&gt;/contracts/&lt;/code&gt; (API contracts when applicable; a Mission that defines no interfaces can waive it, see &lt;a href=&quot;/guides/how-to/missions/accept-and-merge/#when-a-mission-defines-no-contracts&quot;&gt;When a Mission defines no contracts&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Updated agent context files (based on the plan)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;implementation-concern-map&quot;&gt;implementation concern map&lt;/h2&gt;
&lt;p&gt;When a mission involves multiple distinct architectural areas, &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt; includes an
&lt;strong&gt;implementation concern map&lt;/strong&gt; — a structured decomposition of intent before tasks are
generated.&lt;/p&gt;
&lt;p&gt;Implementation concerns (IC-01, IC-02, …) are plan-level architectural units. They are
&lt;strong&gt;not&lt;/strong&gt; work packages and are &lt;strong&gt;not&lt;/strong&gt; executable units. Each concern captures:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Purpose&lt;/strong&gt;: what this area addresses and why it matters&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Relevant requirements&lt;/strong&gt;: FR-### refs from &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Affected surfaces&lt;/strong&gt;: file paths or module names&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sequencing/depends-on&lt;/strong&gt;: which other concerns this one must follow&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Risks&lt;/strong&gt;: key coordination notes&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.tasks&lt;/code&gt; translates these concerns into executable work packages. One concern
may become multiple WPs; multiple small concerns may merge into one WP.&lt;/p&gt;
&lt;h2 id=&quot;example&quot;&gt;Example&lt;/h2&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;/spec-kitty.plan Use FastAPI + PostgreSQL. Deploy on Fly.io. Use JWTs for auth.&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;troubleshooting&quot;&gt;Troubleshooting&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;No plan generated&lt;/strong&gt;: Make sure the spec exists and you are running in the repository root checkout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Planner keeps asking questions&lt;/strong&gt;: Provide the missing architectural details; the plan will not generate until the interview is complete.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Planner is targeting the wrong branch&lt;/strong&gt;: Resolve branch intent first with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission branch-context --json&lt;/code&gt; or recreate the mission with the right &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Need to update the plan&lt;/strong&gt;: Re-run &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt; with the new constraints.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;command-reference&quot;&gt;Command Reference&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/api/slash-commands/&quot;&gt;Slash Commands&lt;/a&gt; - All &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.*&lt;/code&gt; commands&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/api/cli-commands/&quot;&gt;CLI Commands&lt;/a&gt; - Full CLI reference&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/api/file-structure/&quot;&gt;File Structure&lt;/a&gt; - Where plans are stored&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;see-also&quot;&gt;See Also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/guides/how-to/missions/create-specification/&quot;&gt;Create a Specification&lt;/a&gt; - Required before planning&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/guides/how-to/missions/keep-main-clean/&quot;&gt;Keep Main Clean&lt;/a&gt; - Choose a target branch without changing planning location&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/guides/how-to/missions/generate-tasks/&quot;&gt;Generate Tasks&lt;/a&gt; - Next step after planning&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;background&quot;&gt;Background&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/spec-driven-development/&quot;&gt;Spec-Driven Development&lt;/a&gt; - The philosophy&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/kanban-workflow/&quot;&gt;Kanban Workflow&lt;/a&gt; - How work flows after planning&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;getting-started&quot;&gt;Getting Started&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/guides/tutorials/your-first-mission/&quot;&gt;Your First Mission&lt;/a&gt; - Complete workflow walkthrough&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
