mother-brain 0.4.9 → 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/cli.js CHANGED
@@ -798,7 +798,7 @@ async function uninstall(options) {
798
798
  // src/cli.ts
799
799
  import { exec as exec3 } from "child_process";
800
800
  var program = new Command();
801
- var VERSION = "0.4.9";
801
+ var VERSION = "0.5.1";
802
802
  program.name("mother-brain").description("AI-powered project management framework for GitHub Copilot CLI and Codex CLI").version(VERSION);
803
803
  program.command("init").description("Initialize Mother Brain in the current project").option("-f, --force", "Overwrite existing skills").action(init);
804
804
  program.command("update").description("Update Mother Brain skills to the latest version").action(update);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mother-brain",
3
- "version": "0.4.9",
3
+ "version": "0.5.1",
4
4
  "description": "AI-powered project management framework for GitHub Copilot CLI",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -273,54 +273,25 @@ Based on root cause, determine what goes where:
273
273
  - UI (accessibility, responsive, design systems)
274
274
  - Platforms (Windows, macOS, Linux, mobile, web)
275
275
 
276
- **Step 4.5.2: Check if Knowledge Already Exists**
277
- - Search `experience-vault/[category]/` for related files
278
- - Use grep to check for technology mentions
279
- - If exists update existing file
280
- - If new → create new file
276
+ **Step 4.5.2: Invoke Elder Brain RECEIVE**
277
+ - Invoke `skill elder-brain` with the RECEIVE workflow
278
+ - Provide: category, technology name, the gotcha/pattern, solution
279
+ - Elder Brain handles: deduplication, file creation/update, cross-referencing
281
280
 
282
- **Step 4.5.3: Document the Gotcha**
283
-
284
- Create/update `experience-vault/[category]/[tech-name].md`:
285
-
286
- ```markdown
287
- # [Technology Name] - [Brief Title]
288
-
289
- ## Problem
290
- [What goes wrong - the error/failure user experiences]
291
-
292
- ## Gotcha
293
- [The non-obvious thing - why it happens, what's unexpected]
294
-
295
- ## Solution
296
- [How to fix/prevent - code examples, config, steps]
297
-
298
- **When to Consult**: [Which Mother Brain steps should reference this]
299
-
300
- ## Related Gotchas
301
- See also:
302
- - [Link to related experience-vault files]
303
-
304
- ## Sources
305
- - [Link to official docs]
306
- - [Link to community resources]
307
- ```
308
-
309
- **Step 4.5.4: Display Simple Confirmation**
281
+ **Step 4.5.3: Display Simple Confirmation**
310
282
 
311
283
  Display to user:
312
284
  ```
313
285
  🧙 Elder Brain will remember this
314
286
  ```
315
287
 
316
- **Step 4.5.5: Update Mother Brain Reference (If Needed)**
288
+ **Step 4.5.4: Update Mother Brain Reference (If Needed)**
317
289
 
318
290
  If this is a common gotcha that Mother Brain should ALWAYS check for:
319
291
  - Add reference to appropriate Mother Brain step
320
- - Example: "Before deploying, consult experience-vault/deployment/"
321
- - Mother Brain doesn't store the gotcha - just knows WHERE to look
292
+ - Mother Brain doesn't store the gotcha — just knows to invoke Elder Brain at the right time
322
293
 
323
- **Key Principle**: Elder Brain stores domain facts. Mother Brain learns to consult Elder Brain at the right times.
294
+ **Key Principle**: Elder Brain stores domain facts as a skill. Child Brain routes learnings to it via RECEIVE. Mother Brain consults it via RETRIEVE.
324
295
 
325
296
  ### Step 5: Apply Project-Level Learning (Course Correction) - ACTIVE
326
297