mother-brain 0.0.32 → 0.0.34

package/dist/cli.js

@@ -653,7 +653,7 @@ async function uninstall(options) {
 // src/cli.ts
 import { exec as exec3 } from "child_process";
 var program = new Command();
-var VERSION = "0.0.32";
+var VERSION = "0.0.34";
 program.name("mother-brain").description("AI-powered project management framework for GitHub Copilot CLI").version(VERSION);
 program.command("init").description("Initialize Mother Brain in the current project").option("-f, --force", "Overwrite existing skills").action(init);
 program.command("update").description("Update Mother Brain skills to the latest version").action(update);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mother-brain",
-  "version": "0.0.32",
+  "version": "0.0.34",
   "description": "AI-powered project management framework for GitHub Copilot CLI",
   "type": "module",
   "main": "dist/index.js",

package/skills/mother-brain/SKILL.md

@@ -837,109 +837,121 @@ This pattern ensures NO workflow ever traps the user—there's always an escape
    
    - **If "Back to project"**: Return to main menu (Step 2)
 
-### 2A.1 **Send Improvement** (Automatic One-Click Contribution)
+### 2A.1 **Send Improvement** (Automatic Multi-Issue Contribution)
    - When user selects "📤 Send my local improvements":
    
-   **Purpose**: Automatically detect local Mother Brain improvements, gather context from learning logs, and submit a fully-formed GitHub issue in one click. No questions asked - just send.
+   **Purpose**: Automatically detect ALL local Mother Brain improvements, parse learning logs for each distinct improvement, and submit a separate GitHub issue for each one. Handles multiple improvements in one session.
    
    **AUTOMATIC WORKFLOW (No User Prompts)**:
    
-   **Step 2A.1.1: Auto-Detect Local Changes**
+   **Step 2A.1.1: Gather All Improvement Sources**
    
-   - Silently scan for changes to core files:
+   - Collect from THREE sources:
+   
+   **Source 1: Learning Log Entries**
+   - Read `.mother-brain/project-brain.md` or `docs/learning-log.md`
+   - Parse for individual learning entries (marked by `## [Date]` or similar)
+   - Each entry = potential improvement
+   - Extract: date, trigger, learning, resolution
+   
+   **Source 2: Core File Changes**
+   - Get changes to Mother Brain core files:
      ```powershell
-     git diff --name-only HEAD -- ".github/skills/mother-brain/" ".github/skills/child-brain/" ".github/skills/skill-creator/" "cli/"
-     git status --porcelain -- ".github/skills/mother-brain/" ".github/skills/child-brain/" ".github/skills/skill-creator/" "cli/"
+     git diff HEAD -- ".github/skills/mother-brain/SKILL.md"
+     git diff HEAD -- ".github/skills/child-brain/SKILL.md"  
+     git diff HEAD -- ".github/skills/skill-creator/SKILL.md"
      ```
+   - If files are new/untracked: `git diff /dev/null -- [file]`
    
-   - **Core files checked**:
-     - `.github/skills/mother-brain/SKILL.md`
-     - `.github/skills/child-brain/SKILL.md`
-     - `.github/skills/skill-creator/SKILL.md`
-     - `cli/src/**/*`
-     - `cli/package.json`
+   **Source 3: Conversation Context**
+   - Scan conversation history for:
+     - Friction points discussed
+     - Problems reported
+     - Solutions implemented
+     - Pattern: "this isn't working" → "fixed by..."
    
-   - **If no changes detected**:
-     - Display: "📭 No local Mother Brain changes to send. Make improvements first, then come back here."
+   - **If no improvements found across all sources**:
+     - Display: "📭 No local Mother Brain improvements to send."
      - Return to Step 2A (Improve Mother Brain Menu)
    
-   **Step 2A.1.2: Auto-Generate Diff Summary**
-
-   - For each changed file, get the diff silently
-   - AI generates a human-readable summary:
-     - What was changed
-     - Why it was changed (inferred from diff context)
-     - Expected benefit
+   **Step 2A.1.2: Correlate Learnings with File Changes**
    
-   **Step 2A.1.3: Auto-Extract Learning Context**
+   - For each learning entry found:
+     1. Identify which file(s) were modified for this learning
+     2. Extract the relevant diff sections (not the whole file diff)
+     3. Match learning description to code changes
    
-   - Check `.mother-brain/project-brain.md` for recent learnings:
-     - Extract last 3-5 relevant learning entries
-     - Focus on friction that triggered Mother Brain improvements
+   - Group by improvement type:
+     - **Behavioral improvements** → Mother Brain SKILL.md changes
+     - **Feedback handling** → Child Brain SKILL.md changes
+     - **Skill creation** → Skill Creator SKILL.md changes
    
-   - Check conversation history for:
-     - What friction was encountered
-     - How it was resolved
-     - What insight led to the improvement
+   **Step 2A.1.3: Generate Individual Issues**
    
-   **Step 2A.1.4: Auto-Create GitHub Issue**
+   - For EACH distinct improvement, create a separate issue:
    
-   - Generate complete issue automatically:
-     ```markdown
-     Title: [Improvement] [AI-generated brief title from changes]
-     
-     ## Summary
-     [AI-generated summary explaining the improvement in 2-3 sentences]
-     
-     ## Changes
-     [Collapsible diff for each file]
-     <details>
-     <summary>[filename] - [brief description]</summary>
-     
-     ```diff
-     [actual diff]
-     ```
-     </details>
-     
-     ## Why This Improvement
-     **Friction Encountered:**
-     [Extracted from learning log - what problem was faced]
-     
-     **Resolution:**
-     [How the improvement addresses the friction]
-     
-     **Expected Benefit:**
-     [How this helps all Mother Brain users]
-     
-     ## Learning Log Context
-     [Relevant excerpts from project-brain.md that led to this improvement]
-     
-     ---
-     *Submitted automatically via Mother Brain v[version]*
-     ```
+   ```markdown
+   Title: [Improvement] [Brief title describing THIS specific improvement]
    
-   - Create issue using GitHub MCP:
-     ```
-     github-mcp-server: create_issue
-     owner: [Mother Brain repo owner from git remote]
-     repo: [Mother Brain repo name]
-     title: [Generated title]
-     body: [Generated body]
-     labels: ["improvement", "community-contribution"]
-     ```
+   ## Summary
+   [2-3 sentences explaining what this specific improvement does]
+   
+   ## Problem
+   [What friction was encountered that triggered this improvement]
+   
+   ## Solution
+   [How Mother Brain addressed the friction]
+   
+   ## Changes Made
+   **File**: [filename] (lines ~X-Y)
+   
+   <details>
+   <summary>View diff</summary>
+   
+   ```diff
+   [relevant diff for THIS improvement only - not entire file]
+   ```
+   </details>
+   
+   ## Benefits
+   [How this helps all Mother Brain users]
    
-   **Step 2A.1.5: Confirm and Offer Revert**
+   ## Testing
+   [How the improvement was validated]
    
-   - Display success message:
+   ---
+   *Submitted via Mother Brain v[version]*
+   ```
+   
+   **Step 2A.1.4: Submit Issues (Batch)**
+   
+   - For each generated improvement:
+     1. Create GitHub issue using MCP
+     2. Collect issue numbers and URLs
+     3. Add small delay between submissions (avoid rate limiting)
+   
+   - Target repository: `super-state/mother-brain`
+     - Detected from: git remote (if configured)
+     - Fallback: hardcoded default
+   
+   **Step 2A.1.5: Display Results**
+   
+   - Display summary of ALL submitted issues:
      ```
-     ✅ Improvement Submitted!
+     ✅ Improvements Submitted!
+     
+     Created [N] issues:
+     
+     📝 #[1]: [title1]
+        [issue URL]
      
-     Issue #[number]: [title]
-     [issue URL]
+     📝 #[2]: [title2]
+        [issue URL]
      
-     Changes detected:
-     • [file1] - [brief change description]
-     • [file2] - [brief change description]
+     📝 #[3]: [title3]
+        [issue URL]
+     
+     Your contributions are now visible to maintainers.
      ```
    
    - Use `ask_user` with choices:
@@ -1875,61 +1887,44 @@ This pattern ensures NO workflow ever traps the user—there's always an escape
 
    - Proceed to Step 3.6 (Project Folder Setup)
 
-### 3.6. **Project Folder Setup** (MANDATORY - Framework vs Project Separation)
+### 3.6. **Initialize Mother Brain in Current Directory** (MANDATORY)
    
-   **Purpose**: Create a separate folder for the project so that:
-   - Project commits go to project repo (not mother-brain)
-   - Mother Brain folder stays clean for framework development
-   - Skills are copied so they work in the project
+   **Purpose**: Set up Mother Brain in the user's current working directory
+   - Works like `npm init` or `git init` - operates where you are
+   - Creates `.mother-brain/` for project state and documentation
+   - Creates `.github/skills/` for project-specific skills (created as needed)
    
    **CRITICAL ORDERING RULE**: 
-   - Step 3.6 (Project Folder Setup) MUST run BEFORE creating any project files (vision.md, roadmap.md, etc.)
-   - NEVER create `.mother-brain/` folder or project files in the framework folder
-   - The correct order is: Vision Discovery (questions only) → Step 3.6 (create project folder) → Step 4 (create vision.md in project folder)
-   
-   **Step 3.6.1: Determine Project Location**
-   - Derive project folder name from vision (kebab-case, e.g., "coffee-discovery-app")
-   - Default location: Sibling folder `../[project-name]/`
+   - Step 3.6 MUST run BEFORE creating any project files (vision.md, roadmap.md, etc.)
+   - The correct order is: Vision Discovery (questions only) → Step 3.6 (initialize) → Step 4 (create vision.md)
    
+   **Step 3.6.1: Confirm Current Directory**
+   - Display current working directory to user
    - Use `ask_user` with choices:
-     - "[project-name] folder next to mother-brain (recommended)"
-     - "I'll specify a custom location"
-     - "Keep in current folder (framework testing mode)"
-   
-   **If custom location**: Ask for path with `ask_user` freeform
+     - "Yes, set up Mother Brain here"
+     - "No, let me change directories first"
    
-   **If "Keep in current folder"**: 
-   - Display warning: "⚠️ Framework Testing Mode - commits will go to mother-brain repo"
-   - Skip to Step 4 (Vision Document Creation)
+   - If user says no:
+     - Display: "Please `cd` to your desired project directory and run `/mother-brain` again."
+     - STOP execution
    
-   **Step 3.6.2: Create Project Folder**
-   - Create the project directory:
+   **Step 3.6.2: Create Project Structure**
+   - Create Mother Brain folders in current directory:
      ```powershell
-     New-Item -ItemType Directory -Path "[project-path]" -Force
+     New-Item -ItemType Directory -Path ".mother-brain" -Force
+     New-Item -ItemType Directory -Path ".mother-brain/docs" -Force
+     New-Item -ItemType Directory -Path ".mother-brain/docs/tasks" -Force
+     New-Item -ItemType Directory -Path ".mother-brain/docs/research" -Force
+     New-Item -ItemType Directory -Path ".github/skills" -Force
      ```
    
-   **Step 3.6.3: Create Project Skill Structure**
-   - Create `.github/skills/` folder in project (for project-specific skills)
-   - **DO NOT copy core framework skills** (mother-brain, child-brain, skill-creator):
-     - These stay in the framework folder only
-     - They are invoked from framework, not duplicated
-     - Avoids sync issues and confusion about authoritative versions
-   
-   - Copy these files/folders to the new project:
-     - `docs/learning-log.md` (or create empty if doesn't exist)
-     - `.gitignore` (if exists)
-   
-   - Do NOT copy:
-     - `.github/skills/` core skills (mother-brain, child-brain, skill-creator)
-     - `README.md` (will create project-specific one)
-     - `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md` (framework-specific)
-     - `package.json` (framework-specific)
-   
-   - Create empty `.mother-brain/` folder for project docs
-   
-   - **Note**: Project-specific skills created during Step 6 go in project's `.github/skills/`. Core skills are accessed from the framework.
+   - Create initial version tracking:
+     ```powershell
+     $version = "[current-mother-brain-version]"
+     @{version=$version; initialized=(Get-Date -Format "o")} | ConvertTo-Json | Set-Content ".mother-brain/version.json"
+     ```
    
-   **Step 3.6.4: Initialize Git (MANDATORY)**
+   **Step 3.6.3: Initialize Git (MANDATORY)**
    - Git is REQUIRED for Mother Brain to function properly:
      - Improvement submissions require git diff
      - Version tracking requires git tags
@@ -1937,20 +1932,18 @@ This pattern ensures NO workflow ever traps the user—there's always an escape
    
    - Check if git is already initialized:
      ```powershell
-     $gitExists = Test-Path (Join-Path "[project-path]" ".git")
+     $gitExists = Test-Path ".git"
      ```
    
    - If git already exists:
      - Display: "✅ Git repository detected"
-     - Skip initialization
    
    - If git does NOT exist:
      - Initialize automatically:
        ```powershell
-       Set-Location "[project-path]"
        git init
        git add .
-       git commit -m "Initial project setup from Mother Brain"
+       git commit -m "Initialize Mother Brain"
        ```
      - Display: "✅ Git repository initialized"
    
@@ -1958,35 +1951,22 @@ This pattern ensures NO workflow ever traps the user—there's always an escape
      - "Continue (git is ready)"
      - "I want to connect to a remote repository"
    
-   - If user wants to connect existing repo:
+   - If user wants to connect remote:
      - Ask for repo URL with `ask_user` freeform
      - `git remote add origin [url]`
    
-   **Step 3.6.5: Switch Context to Project Folder**
-   - Change working directory to project folder:
-     ```powershell
-     Set-Location "[project-path]"
-     ```
-   
-   - **Add project folder to current VS Code workspace** (keeps terminal session active):
-     ```powershell
-     code --add "[project-path]"
-     ```
-   
+   **Step 3.6.4: Display Confirmation**
    - Display:
      ```
-     ✅ Project folder created!
+     ✅ Mother Brain initialized!
      
-     📁 Location: [project-path]
-     📦 Skills: Copied (mother-brain, child-brain, skill-creator)
-     🔗 Git: [Initialized / Not set up]
+     📁 Location: [current directory]
+     📂 Created: .mother-brain/, .github/skills/
+     🔗 Git: [Initialized / Already existed]
      
-     Project folder added to your workspace. Your file tree now shows the project.
-     Terminal session preserved - continue working here.
+     Ready to create your vision document.
      ```
    
-   - Store project path in memory for potential eject/return
-   - **CRITICAL**: Do NOT open a new VS Code window. Use `code --add` to add to current workspace, preserving the terminal session.
    - **Proceed to Step 4** (Vision Document Creation)
 
 ### 4. **Vision Document Creation**