@benzotti/jedi 0.1.22 → 0.1.23

package/dist/index.js

@@ -9301,6 +9301,7 @@ You are Jedi, an AI development framework that uses specialised agents to plan,
 You are **Jedi**, not Claude. Always refer to yourself as "Jedi" in your responses.
 Use "Jedi" in summaries and status updates (e.g. "Jedi has completed..." not "Claude has completed...").
 Do not add a signature line \u2014 the response is already branded by the Jedi CLI.
+Never include meta-commentary about agent activation (e.g. "You are now active as jdi-planner" or "Plan created as requested"). Just give the response directly.
 
 ## Framework
 
@@ -9328,7 +9329,8 @@ and saving it to \`.jdi/persistence/codebase-index.md\` for future runs.
 
 Only do what was explicitly requested. Do not add extras, tooling, or features the user did not ask for.
 If something is ambiguous, ask \u2014 do not guess.
-Use S/M/L t-shirt sizing, never time estimates.
+NEVER use time estimates (minutes, hours, etc). Use S/M/L t-shirt sizing for all task and plan sizing.
+Follow response templates exactly as instructed in the prompt \u2014 do not improvise the layout or structure.
 
 ## Workflow Routing
 
@@ -11129,7 +11131,7 @@ async function fetchCommentThread(repo, issueNumber) {
         author: parsed.author,
         body: parsed.body,
         createdAt: parsed.createdAt,
-        isJedi: parsed.body.includes("### \u2694\uFE0F Jedi")
+        isJedi: parsed.body.includes("Jedi <sup>")
       });
     } catch {}
   }
@@ -11170,19 +11172,33 @@ function buildConversationContext(thread, currentCommentId) {
   return { history: lines.join(`
 `), previousJediRuns, isFollowUp };
 }
-function formatJediComment(response) {
+var COMMAND_EMOJI = {
+  plan: "\uD83D\uDD2E",
+  implement: "\u25B6",
+  quick: "\u26A1",
+  review: "\uD83D\uDCA0",
+  feedback: "\uD83C\uDF00",
+  ping: "\uD83D\uDD39"
+};
+function formatJediComment(command, response) {
+  const emoji = COMMAND_EMOJI[command] ?? "\u25C8";
   return [
-    `### \u2694\uFE0F Jedi`,
+    `<h3>${emoji} Jedi <sup>${command}</sup></h3>`,
+    ``,
+    `---`,
     ``,
     response
   ].join(`
 `);
 }
 function formatErrorComment(command, summary) {
+  const emoji = COMMAND_EMOJI[command] ?? "\u25C8";
   return [
-    `### \u2694\uFE0F Jedi`,
+    `<h3>${emoji} Jedi <sup>${command} \xB7 failed</sup></h3>`,
+    ``,
+    `---`,
     ``,
-    `**${command} failed.** ${summary}`
+    summary
   ].join(`
 `);
 }
@@ -11304,9 +11320,14 @@ var actionCommand = defineCommand({
     if (repo && commentId) {
       await reactToComment(repo, commentId, "eyes").catch(() => {});
     }
+    const commandLabel = intent.isFeedback ? "feedback" : intent.command;
     let placeholderCommentId = null;
     if (repo && issueNumber) {
-      const thinkingBody = formatJediComment("_Thinking..._");
+      const thinkingBody = `<h3>\uD83E\uDDE0 Jedi <sup>thinking</sup></h3>
+
+---
+
+_Working on it..._`;
       placeholderCommentId = await postGitHubComment(repo, issueNumber, thinkingBody).catch(() => null);
     }
     if (intent.command === "ping") {
@@ -11336,7 +11357,7 @@ var actionCommand = defineCommand({
         `| Version | \`${version}\` |`
       ].join(`
 `);
-      const finalBody = formatJediComment(statusBody);
+      const finalBody = formatJediComment("ping", statusBody);
       if (repo && placeholderCommentId) {
         await updateGitHubComment(repo, placeholderCommentId, finalBody).catch((err) => {
           consola.error("Failed to update ping comment:", err);
@@ -11443,22 +11464,51 @@ Use the ClickUp ticket above as the primary requirements source.` : ``,
             `## Scope Rules`,
             `IMPORTANT: Only plan what was explicitly requested. Do NOT add extras like testing, linting, formatting, CI, or tooling unless the user asked for them.`,
             `If something is ambiguous, ask \u2014 do not guess.`,
+            `NEVER use time estimates (minutes, hours, etc). Use t-shirt sizes: S, M, L. This is mandatory.`,
             ``,
             `## Learnings`,
             `Before planning, read .jdi/persistence/learnings.md and .jdi/framework/learnings/ if they exist. Apply any team preferences found.`,
             ``,
-            `## Presentation`,
-            `Follow the planning workflow in your spec. When presenting the plan:`,
-            `1. Start with a brief summary of the approach`,
-            `2. Include the FULL plan in a collapsible details block using this format:`,
-            `   <details>`,
-            `   <summary>View full plan</summary>`,
-            `   `,
-            `   [full plan content here as markdown]`,
-            `   `,
-            `   </details>`,
-            `3. After the plan, suggest 3-5 optional additions the user might want (e.g. "Would you also like testing? linting? state management?"). These are NOT part of the plan.`,
-            `4. Ask for feedback. The user will respond via another GitHub comment.`
+            `## Response Format`,
+            `Follow the planning workflow in your spec to write plan files. Then respond with EXACTLY this structure (no deviations, no meta-commentary like "You are now active as..." or "Plan created"):`,
+            ``,
+            `1-2 sentence summary of the approach.`,
+            ``,
+            `<details>`,
+            `<summary>View full plan</summary>`,
+            ``,
+            `## {Plan Name}`,
+            ``,
+            `**Overall size:** {S|M|L}`,
+            ``,
+            `### Tasks`,
+            ``,
+            `| Task | Name | Size | Type | Wave |`,
+            `|------|------|------|------|------|`,
+            `| T1 | {name} | {S|M|L} | auto | 1 |`,
+            ``,
+            `### T1 \u2014 {Task Name}`,
+            `**Objective:** {what this achieves}`,
+            ``,
+            `**Steps:**`,
+            `1. {step}`,
+            ``,
+            `**Done when:** {completion criterion}`,
+            ``,
+            `---`,
+            `(repeat for each task)`,
+            ``,
+            `### Verification`,
+            `- [ ] {check 1}`,
+            `- [ ] {check 2}`,
+            ``,
+            `</details>`,
+            ``,
+            `**Optional additions** \u2014 not included in this plan:`,
+            `1. {suggestion}`,
+            `2. {suggestion}`,
+            ``,
+            `Any changes before implementation?`
           ].join(`
 `);
           break;
@@ -11576,11 +11626,11 @@ Use the ClickUp ticket above as the primary requirements source.` : ``,
       const actionLabel = intent.isFeedback ? "feedback" : intent.command;
       let commentBody;
       if (success && fullResponse) {
-        commentBody = formatJediComment(fullResponse);
+        commentBody = formatJediComment(actionLabel, fullResponse);
       } else if (!success) {
         commentBody = formatErrorComment(actionLabel, "Check workflow logs for details.");
       } else {
-        commentBody = formatJediComment(`Executed \`${actionLabel}\` successfully.`);
+        commentBody = formatJediComment(actionLabel, `Executed \`${actionLabel}\` successfully.`);
       }
       if (placeholderCommentId) {
         await updateGitHubComment(repo, placeholderCommentId, commentBody).catch((err) => {
@@ -11662,7 +11712,7 @@ var setupActionCommand = defineCommand({
 // package.json
 var package_default = {
   name: "@benzotti/jedi",
-  version: "0.1.22",
+  version: "0.1.23",
   description: "JDI - Context-efficient AI development framework for Claude Code",
   type: "module",
   bin: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@benzotti/jedi",
-  "version": "0.1.22",
+  "version": "0.1.23",
   "description": "JDI - Context-efficient AI development framework for Claude Code",
   "type": "module",
   "bin": {