docs: consolidate command orchestrators in getdraft.dev, book, and LLMs context

- Updated website home page pipeline, Track Impact Memory, and interactive terminal to use '/draft:plan' and consolidated commands
- Updated book chapters (Context-Driven Development, Getting Started, Specs & Plans, ADRs, and Command Reference) to align with '/draft:plan' and new command structures
- Refreshed 'web/llms.txt' and 'web/llms-full.txt' to document all 32 consolidated slash commands and the correct Cursor/IDE onboarding flows

Author: Mayur Pise

web/book/adrs/index.html

@@ -381,7 +381,7 @@ <h2>ADR Evaluation</h2>
     </div>
 
     <h2>ADRs and Tracks</h2>
-    <p>A track (a feature, fix, or refactor managed by Draft) may generate one or more ADRs during its lifecycle. When <code>/draft:new-track</code> surfaces a technology choice or <code>/draft:decompose</code> reveals an architectural trade-off, those decisions are ADR candidates.</p>
+    <p>A track (a feature, fix, or refactor managed by Draft) may generate one or more ADRs during its lifecycle. When <code>/draft:plan</code> surfaces a technology choice or <code>/draft:decompose</code> reveals an architectural trade-off, those decisions are ADR candidates.</p>
 
     <p>ADRs created during a track reference the track in their context section. This creates bidirectional traceability: the ADR explains why a decision was made, and the track's spec or plan references the ADR number for any reader who wants the full context.</p>
 

web/book/chapters/02-context-driven-development.html

@@ -192,7 +192,7 @@ <h3>Track Lifecycle</h3>
     <p>Every track follows the same lifecycle:</p>
 
     <ol>
-        <li><strong>Create</strong> &mdash; <code>/draft:new-track "Add drag-and-drop reordering"</code> initiates collaborative spec creation</li>
+        <li><strong>Create</strong> &mdash; <code>/draft:plan "Add drag-and-drop reordering"</code> initiates collaborative spec creation</li>
         <li><strong>Plan</strong> &mdash; After spec approval, Draft generates a phased plan with task-level granularity</li>
         <li><strong>Review</strong> &mdash; The developer reviews spec and plan, edits them, commits them for peer review</li>
         <li><strong>Implement</strong> &mdash; <code>/draft:implement</code> executes tasks one at a time, following TDD cycles when enabled</li>

web/book/chapters/03-getting-started.html

@@ -270,7 +270,7 @@ <h3>State Files</h3>
     <h2>Your First Track</h2>
     <p>With initialization complete, you're ready to create your first feature track:</p>
 
-    <pre class="terminal"><code>$ /draft:new-track "Add user authentication"</code></pre>
+    <pre class="terminal"><code>$ /draft:plan "Add user authentication"</code></pre>
 
     <p>Draft loads your full project context &mdash; product vision, tech stack, architecture, workflow preferences, guardrails &mdash; and begins a collaborative dialogue to understand exactly what you need. It asks probing questions about scope, requirements, and constraints before generating anything.</p>
 
@@ -290,7 +290,7 @@ <h2>Your First Track</h2>
     <h2>The Quick Workflow</h2>
     <p>Not everything needs a full specification. For hotfixes, small changes, and well-understood tasks, Draft supports a streamlined workflow:</p>
 
-    <pre class="terminal"><code>$ /draft:new-track --quick "Fix login button not responding on mobile"</code></pre>
+    <pre class="terminal"><code>$ /draft:plan --quick "Fix login button not responding on mobile"</code></pre>
 
     <p>The <code>--quick</code> flag creates a lightweight track with a condensed spec and minimal plan. It still loads project context and creates trackable artifacts, but skips the extended dialogue and detailed phase breakdown. The fix is still constrained by your architecture and conventions &mdash; it's just faster to get started.</p>
 

web/book/chapters/04-specs-and-plans.html

@@ -50,9 +50,9 @@ <h1>Specs &amp; Plans</h1>
     </div>
 
     <h2>Starting a Track</h2>
-    <p>Every unit of work in Draft &mdash; a feature, a bug fix, a refactor &mdash; begins with <code>/draft:new-track</code>. This command does not generate code. It starts a <strong>collaborative intake process</strong> between you and the AI, producing two artifacts that govern everything that follows: a specification and a plan.</p>
+    <p>Every unit of work in Draft &mdash; a feature, a bug fix, a refactor &mdash; begins with <code>/draft:plan</code> (which orchestrates planning and routes to the specialist <code>/draft:new-track</code> workflow). This command does not generate code. It starts a <strong>collaborative intake process</strong> between you and the AI, producing two artifacts that govern everything that follows: a specification and a plan.</p>
 
-    <pre class="terminal"><code>$ /draft:new-track Add OAuth2 support for third-party login</code></pre>
+    <pre class="terminal"><code>$ /draft:plan Add OAuth2 support for third-party login</code></pre>
 
     <p>The AI reads your project's <code>product.md</code>, <code>tech-stack.md</code>, <code>.ai-context.md</code>, and <code>workflow.md</code> before asking a single question. It arrives at the conversation already understanding your architecture, your constraints, and your conventions. Then the intake begins.</p>
 
@@ -321,7 +321,7 @@ <h2>Status Markers</h2>
     <h2>Quick Mode</h2>
     <p>Not every change needs a full intake ceremony. For hotfixes and small, isolated changes scoped to 1&ndash;3 hours, the <code>--quick</code> flag skips the collaborative conversation entirely.</p>
 
-    <pre class="terminal"><code>$ /draft:new-track --quick Fix null pointer in email validation</code></pre>
+    <pre class="terminal"><code>$ /draft:plan --quick Fix null pointer in email validation</code></pre>
 
     <p>Quick mode asks exactly two questions: "What exactly needs to change?" and "How will you know it's done?" It then generates a minimal <code>spec.md</code> and a flat <code>plan.md</code> with a single phase. The metadata records <code>"type": "quick"</code> so the status display adjusts accordingly &mdash; no phase progress, just a flat task list.</p>
 

web/book/chapters/09-adrs.html

@@ -175,7 +175,7 @@ <h2>ADR Evaluation</h2>
     </div>
 
     <h2>ADRs and Tracks</h2>
-    <p>A track (a feature, fix, or refactor managed by Draft) may generate one or more ADRs during its lifecycle. When <code>/draft:new-track</code> surfaces a technology choice or <code>/draft:decompose</code> reveals an architectural trade-off, those decisions are ADR candidates.</p>
+    <p>A track (a feature, fix, or refactor managed by Draft) may generate one or more ADRs during its lifecycle. When <code>/draft:plan</code> surfaces a technology choice or <code>/draft:decompose</code> reveals an architectural trade-off, those decisions are ADR candidates.</p>
 
     <p>ADRs created during a track reference the track in their context section. This creates bidirectional traceability: the ADR explains why a decision was made, and the track's spec or plan references the ADR number for any reader who wants the full context.</p>
 

web/book/chapters/appendix-a-command-reference.html

@@ -2,7 +2,7 @@
     <h1>Appendix A: Command Reference</h1>
     <p class="chapter-meta"><span class="part-name">Appendix</span></p>
 
-    <p class="chapter-intro">Quick-reference for all 28 Draft commands. Syntax shown is for Claude Code; Copilot uses <code>draft command</code> (no slash), Cursor uses <code>@draft command</code>.</p>
+    <p class="chapter-intro">Quick-reference for all 32 Draft commands. Syntax shown is for Claude Code; Copilot uses <code>draft command</code> (no slash), Cursor uses <code>@draft command</code>.</p>
 
     <div class="figure">
         <div class="figure-content">
@@ -102,18 +102,25 @@ <h1>Appendix A: Command Reference</h1>
                 <td><code>/draft:init</code> at root and at least one service</td>
                 <td>18</td>
             </tr>
+            <tr>
+                <td><code>/draft:plan</code></td>
+                <td>Canonical parent planning command. Routes planning intent to specialist commands based on context</td>
+                <td><code>new-track</code>, <code>decompose</code>, <code>change</code>, <code>adr</code> &mdash; route directly; <code>&lt;description&gt;</code> &mdash; initial feature description</td>
+                <td><code>/draft:init</code></td>
+                <td>4, 7, 8, 9</td>
+            </tr>
             <tr>
                 <td><code>/draft:new-track</code></td>
                 <td>Create a feature/fix track with spec and phased plan through collaborative dialogue</td>
                 <td><code>--quick</code> &mdash; streamlined mode with fewer questions; <code>&lt;description&gt;</code> &mdash; initial feature description</td>
-                <td><code>/draft:init</code></td>
+                <td><code>/draft:init</code> (or routed from <code>/draft:plan</code>)</td>
                 <td>4</td>
             </tr>
             <tr>
                 <td><code>/draft:implement</code></td>
                 <td>Execute tasks from plan with TDD workflow and architecture checkpoints</td>
                 <td>Resumes in-progress tasks automatically</td>
-                <td><code>/draft:new-track</code> (requires plan.md)</td>
+                <td><code>/draft:plan</code> (requires plan.md)</td>
                 <td>5</td>
             </tr>
             <tr>
@@ -186,6 +193,13 @@ <h1>Appendix A: Command Reference</h1>
                 <td>Active track with commits</td>
                 <td>7</td>
             </tr>
+            <tr>
+                <td><code>/draft:ops</code></td>
+                <td>Canonical parent operations command. Routes intent to specialist commands based on context</td>
+                <td><code>debug</code>, <code>deploy-checklist</code>, <code>incident-response</code>, <code>standup</code> &mdash; route directly</td>
+                <td><code>/draft:init</code></td>
+                <td>7, 15</td>
+            </tr>
             <tr>
                 <td><code>/draft:debug</code></td>
                 <td>Structured debugging: reproduce, isolate, diagnose, fix</td>
@@ -235,13 +249,27 @@ <h1>Appendix A: Command Reference</h1>
                 <td>None</td>
                 <td>&mdash;</td>
             </tr>
+            <tr>
+                <td><code>/draft:docs</code></td>
+                <td>Canonical parent documentation command. Routes intent to specialist commands based on context</td>
+                <td><code>documentation</code>, <code>testing-strategy</code>, <code>tech-debt</code>, <code>tour</code> &mdash; route directly</td>
+                <td><code>/draft:init</code></td>
+                <td>0, 14, 17</td>
+            </tr>
             <tr>
                 <td><code>/draft:documentation</code></td>
                 <td>Technical documentation: readme, runbook, api, onboarding</td>
                 <td><code>readme</code>, <code>runbook &lt;service&gt;</code>, <code>api &lt;module&gt;</code>, <code>onboarding</code></td>
                 <td>init (optional)</td>
                 <td>&mdash;</td>
             </tr>
+            <tr>
+                <td><code>/draft:integrations</code></td>
+                <td>Canonical parent integrations command. Routes intent to specialist commands based on context</td>
+                <td><code>jira-preview</code>, <code>jira-create</code> &mdash; route directly</td>
+                <td><code>/draft:init</code></td>
+                <td>19</td>
+            </tr>
             <tr>
                 <td><code>/draft:jira-preview</code></td>
                 <td>Generate Jira export file from track plan for review before creating issues</td>

web/book/command-reference/index.html

@@ -310,23 +310,23 @@ <h1>Appendix A: Command Reference</h1>
             </tr>
             <tr>
                 <td><code>/draft:plan</code></td>
-                <td>Canonical planning parent command. Routes to new-track, decompose, change, or adr based on context.</td>
-                <td>&mdash;</td>
+                <td>Canonical parent planning command. Routes planning intent to specialist commands based on context</td>
+                <td><code>new-track</code>, <code>decompose</code>, <code>change</code>, <code>adr</code> &mdash; route directly; <code>&lt;description&gt;</code> &mdash; initial feature description</td>
                 <td><code>/draft:init</code></td>
-                <td>4</td>
+                <td>4, 7, 8, 9</td>
             </tr>
             <tr>
                 <td><code>/draft:new-track</code></td>
                 <td>Create a feature/fix track with spec and phased plan through collaborative dialogue</td>
                 <td><code>--quick</code> &mdash; streamlined mode with fewer questions; <code>&lt;description&gt;</code> &mdash; initial feature description</td>
-                <td><code>/draft:init</code></td>
+                <td><code>/draft:init</code> (or routed from <code>/draft:plan</code>)</td>
                 <td>4</td>
             </tr>
             <tr>
                 <td><code>/draft:implement</code></td>
                 <td>Execute tasks from plan with TDD workflow and architecture checkpoints</td>
                 <td>Resumes in-progress tasks automatically</td>
-                <td><code>/draft:new-track</code> (requires plan.md)</td>
+                <td><code>/draft:plan</code> (requires plan.md)</td>
                 <td>5</td>
             </tr>
             <tr>
@@ -401,10 +401,10 @@ <h1>Appendix A: Command Reference</h1>
             </tr>
             <tr>
                 <td><code>/draft:ops</code></td>
-                <td>Canonical operations parent command. Routes to debug, deploy-checklist, incident-response, or standup.</td>
-                <td>&mdash;</td>
-                <td>None</td>
-                <td>&mdash;</td>
+                <td>Canonical parent operations command. Routes intent to specialist commands based on context</td>
+                <td><code>debug</code>, <code>deploy-checklist</code>, <code>incident-response</code>, <code>standup</code> &mdash; route directly</td>
+                <td><code>/draft:init</code></td>
+                <td>7, 15</td>
             </tr>
             <tr>
                 <td><code>/draft:debug</code></td>
@@ -457,10 +457,10 @@ <h1>Appendix A: Command Reference</h1>
             </tr>
             <tr>
                 <td><code>/draft:docs</code></td>
-                <td>Canonical documentation parent command. Routes to readme, runbook, api, or onboarding generation.</td>
-                <td>&mdash;</td>
-                <td>init (optional)</td>
-                <td>&mdash;</td>
+                <td>Canonical parent documentation command. Routes intent to specialist commands based on context</td>
+                <td><code>documentation</code>, <code>testing-strategy</code>, <code>tech-debt</code>, <code>tour</code> &mdash; route directly</td>
+                <td><code>/draft:init</code></td>
+                <td>0, 14, 17</td>
             </tr>
             <tr>
                 <td><code>/draft:documentation</code></td>
@@ -471,9 +471,9 @@ <h1>Appendix A: Command Reference</h1>
             </tr>
             <tr>
                 <td><code>/draft:integrations</code></td>
-                <td>Canonical integrations parent command. Routes to Jira interactions.</td>
-                <td>&mdash;</td>
-                <td>None</td>
+                <td>Canonical parent integrations command. Routes intent to specialist commands based on context</td>
+                <td><code>jira-preview</code>, <code>jira-create</code> &mdash; route directly</td>
+                <td><code>/draft:init</code></td>
                 <td>19</td>
             </tr>
             <tr>

web/book/context-driven-development/index.html

@@ -398,7 +398,7 @@ <h3>Track Lifecycle</h3>
     <p>Every track follows the same lifecycle:</p>
 
     <ol>
-        <li><strong>Create</strong> &mdash; <code>/draft:new-track "Add drag-and-drop reordering"</code> initiates collaborative spec creation</li>
+        <li><strong>Create</strong> &mdash; <code>/draft:plan "Add drag-and-drop reordering"</code> initiates collaborative spec creation</li>
         <li><strong>Plan</strong> &mdash; After spec approval, Draft generates a phased plan with task-level granularity</li>
         <li><strong>Review</strong> &mdash; The developer reviews spec and plan, edits them, commits them for peer review</li>
         <li><strong>Implement</strong> &mdash; <code>/draft:implement</code> executes tasks one at a time, following TDD cycles when enabled</li>

web/book/getting-started/index.html

@@ -476,7 +476,7 @@ <h3>State Files</h3>
     <h2>Your First Track</h2>
     <p>With initialization complete, you're ready to create your first feature track:</p>
 
-    <pre class="terminal"><code>$ /draft:new-track "Add user authentication"</code></pre>
+    <pre class="terminal"><code>$ /draft:plan "Add user authentication"</code></pre>
 
     <p>Draft loads your full project context &mdash; product vision, tech stack, architecture, workflow preferences, guardrails &mdash; and begins a collaborative dialogue to understand exactly what you need. It asks probing questions about scope, requirements, and constraints before generating anything.</p>
 
@@ -496,7 +496,7 @@ <h2>Your First Track</h2>
     <h2>The Quick Workflow</h2>
     <p>Not everything needs a full specification. For hotfixes, small changes, and well-understood tasks, Draft supports a streamlined workflow:</p>
 
-    <pre class="terminal"><code>$ /draft:new-track --quick "Fix login button not responding on mobile"</code></pre>
+    <pre class="terminal"><code>$ /draft:plan --quick "Fix login button not responding on mobile"</code></pre>
 
     <p>The <code>--quick</code> flag creates a lightweight track with a condensed spec and minimal plan. It still loads project context and creates trackable artifacts, but skips the extended dialogue and detailed phase breakdown. The fix is still constrained by your architecture and conventions &mdash; it's just faster to get started.</p>
 

web/book/specs-and-plans/index.html

@@ -256,9 +256,9 @@ <h1>Specs &amp; Plans</h1>
     </div>
 
     <h2>Starting a Track</h2>
-    <p>Every unit of work in Draft &mdash; a feature, a bug fix, a refactor &mdash; begins with <code>/draft:new-track</code>. This command does not generate code. It starts a <strong>collaborative intake process</strong> between you and the AI, producing two artifacts that govern everything that follows: a specification and a plan.</p>
+    <p>Every unit of work in Draft &mdash; a feature, a bug fix, a refactor &mdash; begins with <code>/draft:plan</code> (which orchestrates planning and routes to the specialist <code>/draft:new-track</code> workflow). This command does not generate code. It starts a <strong>collaborative intake process</strong> between you and the AI, producing two artifacts that govern everything that follows: a specification and a plan.</p>
 
-    <pre class="terminal"><code>$ /draft:new-track Add OAuth2 support for third-party login</code></pre>
+    <pre class="terminal"><code>$ /draft:plan Add OAuth2 support for third-party login</code></pre>
 
     <p>The AI reads your project's <code>product.md</code>, <code>tech-stack.md</code>, <code>.ai-context.md</code>, and <code>workflow.md</code> before asking a single question. It arrives at the conversation already understanding your architecture, your constraints, and your conventions. Then the intake begins.</p>
 
@@ -527,7 +527,7 @@ <h2>Status Markers</h2>
     <h2>Quick Mode</h2>
     <p>Not every change needs a full intake ceremony. For hotfixes and small, isolated changes scoped to 1&ndash;3 hours, the <code>--quick</code> flag skips the collaborative conversation entirely.</p>
 
-    <pre class="terminal"><code>$ /draft:new-track --quick Fix null pointer in email validation</code></pre>
+    <pre class="terminal"><code>$ /draft:plan --quick Fix null pointer in email validation</code></pre>
 
     <p>Quick mode asks exactly two questions: "What exactly needs to change?" and "How will you know it's done?" It then generates a minimal <code>spec.md</code> and a flat <code>plan.md</code> with a single phase. The metadata records <code>"type": "quick"</code> so the status display adjusts accordingly &mdash; no phase progress, just a flat task list.</p>