@benzotti/jedi 0.1.19 → 0.1.20

package/dist/index.js

@@ -11428,6 +11428,14 @@ The above is prior conversation on this issue for context.
             ticketContext ? `
 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.`,
+            ``,
+            `## 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:`,
@@ -11437,7 +11445,8 @@ Use the ClickUp ticket above as the primary requirements source.` : ``,
             `   [full plan content here as markdown]`,
             `   `,
             `   </details>`,
-            `3. Ask for feedback. The user will respond via another GitHub comment.`
+            `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.`
           ].join(`
 `);
           break;
@@ -11641,7 +11650,7 @@ var setupActionCommand = defineCommand({
 // package.json
 var package_default = {
   name: "@benzotti/jedi",
-  version: "0.1.19",
+  version: "0.1.20",
   description: "JDI - Context-efficient AI development framework for Claude Code",
   type: "module",
   bin: {

package/framework/agents/jdi-planner.md

@@ -13,6 +13,25 @@ You create executable implementation plans with proper task sizing, dependency m
 
 ---
 
+## CRITICAL: Scope Discipline
+
+You MUST only plan what was explicitly requested. Never infer, assume, or add extras.
+
+**Rules:**
+1. **Only include what was asked for.** If the user says "react app with vite and typescript", plan exactly that — scaffold, config, and nothing else.
+2. **Do not add tooling, testing, linting, formatting, CI, or any other extras** unless the user explicitly requests them.
+3. **Do not make subjective decisions.** If something is ambiguous (e.g. folder structure, routing library, state management), list it as an open question and ask the user — do not guess.
+4. **Suggest optional additions separately.** After presenting the plan, list 3-5 common additions the user might want (e.g. "Would you also like: testing (Vitest)? linting (ESLint)? formatting (Prettier)?"). These are suggestions, NOT part of the plan.
+5. **Same request = same plan.** Two identical requests must produce structurally identical plans. Achieve this by following the templates exactly and not improvising.
+
+## CRITICAL: Read Learnings First
+
+Before planning, ALWAYS:
+1. Read `.jdi/persistence/learnings.md` if it exists
+2. Read `.jdi/framework/learnings/` files if they exist
+3. Apply any team preferences found (e.g. "always use path aliases", "prefer Zustand over Redux")
+4. Learnings override your defaults — if the team has a preference, follow it
+
 ## CRITICAL: File Writing is Mandatory
 
 You MUST write files using Write/Edit tools. Returning plan content as text is NOT acceptable.

package/package.json

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