mother-brain 0.0.25 → 0.0.26

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.25";
+var VERSION = "0.0.26";
 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.25",
+  "version": "0.0.26",
   "description": "AI-powered project management framework for GitHub Copilot CLI",
   "type": "module",
   "main": "dist/index.js",

package/skills/mother-brain/SKILL.md

@@ -1641,31 +1641,166 @@ This pattern ensures NO workflow ever traps the user—there's always an escape
    - Proceed to Step 3 (Vision Discovery) or next selected step
 
 ### 3. **Vision Discovery** (New Projects Only)
-   - Use `ask_user` to conduct product discovery
-   - Ask 8-12 contextual questions focusing on:
    
-   **Core Questions:**
-   1. **The Problem**: "What pain point or opportunity are you addressing?"
-   2. **The Vision**: "Imagine this project succeeds—what does that look like?"
-   3. **The Users**: "Who will benefit from this? Describe them."
-   4. **The Why**: "Why is this important? What changes if you DON'T build this?"
-   5. **Success Metrics**: "How will you know this project succeeded?"
-   6. **Constraints**: "What limitations exist? (Budget, skills, tech preferences)"
-   7. **MVP Definition**: "What's the minimum feature set that proves this works?"
+   **Purpose**: Adaptive, research-driven discovery that evolves understanding with each user response. Mother Brain becomes an expert in the user's domain DURING the conversation, not after.
    
-   **NOTE: Do NOT ask about timeline/duration.** AI execution speed is not a constraint. Every project receives the same quality treatment: proper research, design thinking, skill creation, and best practices. "Weekend project" vs "enterprise project" makes no difference to quality standards.
+   **ADAPTIVE DISCOVERY PROTOCOL (MANDATORY)**:
    
-   **Follow-up Questions (adapt based on responses):**
-   - "Who are your competitors/alternatives?"
-   - "What have you tried before?"
-   - "What's your biggest fear about this project?"
-   - "What would make you abandon this?"
+   This is NOT a static questionnaire. After EACH user response:
+   1. Extract keywords and domain signals
+   2. Research the domain using `web_search`
+   3. Identify knowledge gaps and skill needs
+   4. Generate dynamic follow-up questions based on research
+   5. Build running list of skill candidates
    
-   - Provide 2-3 options per question where appropriate
-   - Allow freeform responses for complex answers
-   - Dig deeper based on responses
+   **Step 3.1: Opening Question**
+   
+   - Start with the core question:
+     ```
+     🧠 Vision Discovery
+     
+     Tell me about what you want to build. 
+     What problem are you solving, or what opportunity are you pursuing?
+     ```
+   
+   - Use `ask_user` with freeform enabled
+   
+   **Step 3.2: Adaptive Response Loop (REPEAT UNTIL VISION IS COMPLETE)**
+   
+   **After EACH user response, do ALL of the following:**
+   
+   **3.2.1: Extract Domain Signals**
+   - Parse user response for:
+     - Industry/domain keywords (game, e-commerce, healthcare, etc.)
+     - Technology mentions (React, Shopify, Unity, etc.)
+     - Style/aesthetic mentions (minimal, retro, professional, etc.)
+     - User type mentions (developers, consumers, businesses, etc.)
+     - Problem space indicators (tracking, discovery, automation, etc.)
+   
+   - Display:
+     ```
+     📘 Noted: [brief summary of what was understood]
+     ```
+   
+   **3.2.2: Research Domain (MANDATORY)**
+   - For EACH new domain signal, research using `web_search`:
+     - "[domain] best practices"
+     - "[domain] common patterns"
+     - "[domain] user expectations"
+     - "[technology] implementation approaches"
+   
+   - Store research findings in memory for:
+     - Skill creation later
+     - Follow-up question generation
+     - Understanding what the user might NOT know to ask
+   
+   **3.2.3: Identify Knowledge Gaps**
+   - Based on research, determine:
+     - What aspects of the domain haven't been discussed yet?
+     - What decisions does the user need to make?
+     - What are common pitfalls in this space?
+     - What skills will Mother Brain need to help with this?
+   
+   - Add skill candidates to running list:
+     ```
+     🛠️ Skill needs identified so far:
+     - [skill-1]: [why it's needed]
+     - [skill-2]: [why it's needed]
+     ```
+   
+   **3.2.4: Generate Dynamic Follow-Up Question**
+   - Based on research and gaps, ask the MOST RELEVANT next question
+   - This should NOT be from a static list - it should be informed by:
+     - What research revealed about the domain
+     - What the user hasn't addressed yet
+     - What decisions will significantly impact the project
+   
+   - Example evolution:
+     - User says "roguelite car game with storybook art"
+     - Research: roguelite mechanics, car game physics, storybook illustration
+     - Generated question: "Roguelites rely heavily on the core gameplay loop - what's the moment-to-moment action? Is it racing, combat, exploration, or something else?"
+   
+   - Use `ask_user` with:
+     - 2-3 relevant options based on research
+     - Freeform allowed for complex answers
+   
+   **Step 3.3: Core Areas to Cover (Ensure These Are Addressed)**
+   
+   Through adaptive questioning, ensure these areas are explored (not as a checklist, but organically based on the domain):
+   
+   - **The Problem/Opportunity**: What pain point or gap exists?
+   - **The Vision**: What does success look like?
+   - **The Users**: Who benefits? Who uses it?
+   - **Differentiators**: What makes this unique in the space?
+   - **Aesthetic/Experience**: How should it feel? Look? Sound?
+   - **Constraints**: Budget, skills, platform limitations?
+   - **MVP Scope**: What proves the concept works?
+   
+   **Domain-Specific Questions (Generated From Research)**:
+   - For games: gameplay loop, art style, audio needs, target platform
+   - For e-commerce: payment integration, inventory management, shipping
+   - For SaaS: authentication, multi-tenancy, pricing model
+   - For mobile apps: offline capability, push notifications, app store requirements
+   - For Shopify: theme vs app, API usage, merchant needs
+   - For APIs: authentication, rate limiting, documentation needs
+   
+   **Step 3.4: Vision Summary and Skill Pre-Planning**
+   
+   - When sufficient understanding is reached (typically 6-10 exchanges):
+   
+   - Display comprehensive summary:
+     ```
+     🧠 Vision Summary
+     
+     **What You're Building:**
+     [1-2 sentence description]
+     
+     **Who It's For:**
+     [Target users/audience]
+     
+     **Key Features:**
+     - [Feature 1]
+     - [Feature 2]
+     - [Feature 3]
+     
+     **Aesthetic/Experience:**
+     [How it should look, feel, sound]
+     
+     **Success Looks Like:**
+     [What proves this works]
+     
+     **Domain Research Findings:**
+     [Key insights from research that will inform development]
+     
+     🛠️ **Skills Mother Brain Will Need:**
+     - [skill-1]: [what it will handle]
+     - [skill-2]: [what it will handle]
+     - [skill-3]: [what it will handle]
+     ```
+   
+   - Use `ask_user` with choices:
+     - "This captures it perfectly"
+     - "Mostly right, but let me clarify something"
+     - "I want to change the direction"
+   
+   - If clarification needed: Ask follow-up, update summary
+   - If direction change: Return to Step 3.2
+   
+   **Step 3.5: Store Research and Skill Candidates**
+   
+   - Before proceeding to project setup:
+     - Store domain research in `.mother-brain/domain-research.md`
+     - Store skill candidates in `.mother-brain/skill-candidates.md`
+   - These will be used during:
+     - Roadmap generation (Step 5)
+     - Skill creation (Step 6)
+     - Task execution (Step 9)
+   
+   **NOTE: Do NOT ask about timeline/duration.** AI execution speed is not a constraint.
+
+   - Proceed to Step 3.6 (Project Folder Setup)
 
-### 3.5. **Project Folder Setup** (MANDATORY - Framework vs Project Separation)
+### 3.6. **Project Folder Setup** (MANDATORY - Framework vs Project Separation)
    
    **Purpose**: Create a separate folder for the project so that:
    - Project commits go to project repo (not mother-brain)
@@ -1673,11 +1808,11 @@ This pattern ensures NO workflow ever traps the user—there's always an escape
    - Skills are copied so they work in the project
    
    **CRITICAL ORDERING RULE**: 
-   - Step 3.5 (Project Folder Setup) MUST run BEFORE creating any project files (vision.md, roadmap.md, etc.)
+   - 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.5 (create project folder) → Step 4 (create vision.md in project 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.5.1: Determine Project Location**
+   **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]/`
    
@@ -1692,13 +1827,13 @@ This pattern ensures NO workflow ever traps the user—there's always an escape
    - Display warning: "⚠️ Framework Testing Mode - commits will go to mother-brain repo"
    - Skip to Step 4 (Vision Document Creation)
    
-   **Step 3.5.2: Create Project Folder**
+   **Step 3.6.2: Create Project Folder**
    - Create the project directory:
      ```powershell
      New-Item -ItemType Directory -Path "[project-path]" -Force
      ```
    
-   **Step 3.5.3: Create Project Skill Structure**
+   **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
@@ -1719,7 +1854,7 @@ This pattern ensures NO workflow ever traps the user—there's always an escape
    
    - **Note**: Project-specific skills created during Step 6 go in project's `.github/skills/`. Core skills are accessed from the framework.
    
-   **Step 3.5.4: Initialize Git (Optional)**
+   **Step 3.6.4: Initialize Git (Optional)**
    - Use `ask_user` with choices:
      - "Initialize new git repo"
      - "I'll connect to an existing repo later"
@@ -1737,7 +1872,7 @@ This pattern ensures NO workflow ever traps the user—there's always an escape
      - Ask for repo URL
      - `git remote add origin [url]`
    
-   **Step 3.5.5: Switch Context to Project Folder**
+   **Step 3.6.5: Switch Context to Project Folder**
    - Change working directory to project folder:
      ```powershell
      Set-Location "[project-path]"