mirror of
https://github.com/gnekt/My-Brain-Is-Full-Crew.git
synced 2026-08-26 10:05:37 +00:00
1ee2dc415f
* Add standardized template for custom agent creation
New file: references/agent-template.md
This is a reference document that the Architect reads when generating
custom agents. It defines the exact structure every agent must follow:
YAML frontmatter format, required sections (Language, User Profile,
Inter-Agent Coordination, Core Responsibilities, Operational Rules),
placeholder tokens, and inline conventions (naming rules, tool
permissions, multilingual triggers).
The template is not an agent itself. It is a structural guide that
ensures custom agents are generated with the same quality and
consistency as the core 8.
* Add custom agent support to orchestration references
agents-registry.md:
- Added "Custom Agents" section with rules for how custom agents
are added to the registry (naming, priority, creation flow)
- Custom agents always have lower priority than core 8
- Names must be lowercase with hyphens, no conflicts with core names
agents.md:
- Added "Custom Agents" section explaining what they are, how they
coordinate with core agents, and how to create/edit/remove them
agent-orchestration.md:
- Added "Suggested new agent" signal format so agents can flag when
the user needs functionality that no existing agent provides
- Added step in Dispatcher Decision Logic to check for this signal
- Added "Custom Agent Lifecycle" section covering creation, discovery,
routing, chaining, maintenance, and deletion
* Add "Suggested new agent" capability to all 7 non-architect agents
Each agent now has a "When to suggest a new agent" subsection inside
its Inter-Agent Coordination block. When an agent detects that the
user needs functionality that no existing agent can handle, it
outputs a "Suggested new agent" section with:
- Need: what capability is missing
- Reason: why no existing agent covers it
- Suggested role: what the new agent would do
The dispatcher reads this and asks the user if they want the
Architect to create a custom agent for the detected need.
Agents are also told when NOT to suggest a new agent (existing
agent can handle it, one-off task, outside vault scope).
* Add full custom agent creation flow to the Architect
The Architect can now create, edit, and remove custom agents through
an extended conversational flow with the user.
Changes to the frontmatter:
- Added trigger phrases for custom agent creation in 6 languages
("create a new agent", "custom agent", "crea un nuovo agente", etc.)
New section "Custom Agent Creation" with:
- 5-phase conversation flow (Understanding, Capabilities, Output,
Advanced, Confirmation) where the Architect asks one question at
a time and adapts follow-ups based on user answers
- Agent file generation following references/agent-template.md
- Automatic updates to agents-registry.md and agents.md
- Management commands: edit, remove, list custom agents
- Validation rules: no name conflicts with core 8, minimal tool
permissions by default, mandatory coordination sections
- Quality standards: Core Responsibilities must be detailed enough
to produce a production-quality agent
Also added the "Suggested new agent" subsection (same as other agents).
* Update dispatcher routing to support custom agents
- Changed "The ONLY agents you may use are these 8" to acknowledge
that custom agents created by the Architect are also valid
- Added row 9+ to the routing priority table for custom agents
(always lower priority than core 8)
- Added section 9 "CUSTOM AGENTS" with routing logic: when no core
agent matches, check agents-registry.md for custom agents
- Added check for "Suggested new agent" signals in the multi-agent
routing decision flow (step 6)
* Add custom agents to README, CONTRIBUTING, and TERMS_OF_USE
README.md:
- Badge changed from "8 Agents" to "8+ Agents"
- Added custom agents as point 4 of "What makes this different",
positioned right after the main pitch for maximum visibility
- Includes a table of real-life scenarios (budget tracking, journaling,
paper reading, project monitoring, client deadline management)
- Links to Terms of Use for the responsibility disclaimer
CONTRIBUTING.md:
- Renamed "Propose a new crew member" to "Propose a new core crew
member" with a note that users can create custom agents via Architect
- Added "Custom agents vs. core agents" section explaining the
distinction between personal custom agents and project-shipped
core agents
TERMS_OF_USE.md:
- Added new Section 9 "Custom Agents" with full disclaimer: custom
agents are entirely the user's creation and responsibility, no
warranty on their behavior, author accepts no liability
- Updated Section 7 (Limitation of Liability) to reference custom
agents explicitly
- Renumbered sections 9-11 to 10-12
* Force the Architect to always run the full conversation before creating a custom agent
The Architect was generating custom agents immediately from a single
user message instead of going through the 5-phase conversation flow.
Added explicit blocking instructions at three points:
- Section intro: "NEVER create an agent in one shot"
- Before the conversation phases: "Do NOT generate the agent
immediately, even if the request seems clear"
- Explicit rule: "You are NOT allowed to create the agent file
until Phase 5"
- Reinforced one-question-per-message rule
* Force custom agent descriptions to use only the user's language
The Architect was copying the multilingual pattern from core agents
and adding translations in 6+ languages to custom agent descriptions.
Custom agents should have their description and trigger phrases
written exclusively in the language the user speaks. Reinforced
this rule in both the generation instructions and the validation
rules section.
* Force custom agent body to always be written in English
The frontmatter description uses the user's language (for trigger
matching), but the agent body (system prompt) must always be in
English for better LLM instruction-following performance. The agent
still responds in the user's language at runtime thanks to the
language matching rule.
* Add confirmation prompt before overwriting existing installation
launchme.sh:
- Detects if .claude/ or CLAUDE.md already exist in the vault
- Shows the user what will be overwritten
- Asks for explicit confirmation before proceeding
- Clarifies that custom agents and vault notes are never touched
updateme.sh:
- Asks for confirmation before overwriting core files
- Same clarification about custom agents being preserved
* Deprecate removed files instead of leaving orphans in the vault
When a file is removed from the repo (agents, references, or skills),
the updater now renames it with a "-DEPRECATED" suffix and prepends
a "DEPRECATED DO NOT USE" header instead of silently leaving it.
updateme.sh:
- Core agents in .claude/agents/ that no longer exist in the repo
get renamed to {name}-DEPRECATED.md with deprecation header
(custom agents are never touched)
- References in .claude/references/ that no longer exist in the repo
get the same treatment
- The entire .claude/skills/ directory (removed from the project)
gets renamed to .claude/skills-DEPRECATED/ with deprecation headers
on each SKILL.md
- Summary now reports deprecated file count
launchme.sh:
- Added confirmation prompt before overwriting existing installation
- Skills generation and copying kept intact (generate-skills.py runs
first, then copies to .claude/skills/)
* Add first-run setup section to custom agent template and creation flow
Custom agents now have a "First Run Setup" section that defines what
the agent must do the very first time it is invoked: what questions
to ask the user, what config files or folders to create, and how to
detect that it has already been set up.
agent-template.md:
- New "First Run Setup" section between Core Responsibilities and
Operational Rules, with subsections for detection, questions to
ask, what to create, and post-setup behavior
architect.md:
- New Phase 4 "First Run Setup" in the conversational flow where
the Architect asks the user what the agent should do on first run
- Previous Phase 4 (Advanced) becomes Phase 5
- Previous Phase 5 (Confirmation) becomes Phase 6
- Updated blocking rules to reference Phase 6
* Redesign README header and broaden legal disclaimers for custom agents
Improve README header visual hierarchy: centered title, prominent Discord
CTA, metadata badges moved to secondary row. Replace two custom agent
examples with funnier, gender-neutral ones. Rewrite TERMS_OF_USE Section 3
from "Health and Wellness Agents" to "Custom Agents and Advice-Generating
Output" covering health, legal, financial, and all regulated domains.
* Fix reference paths in architect to use .claude/references/ prefix
The agent runs inside the vault where references live under
.claude/references/, not under references/ (which is the repo layout).
* Fix reference paths in agent-template to use .claude/references/ prefix
* Add core-manifest to protect custom agents from deprecation
launchme.sh and updateme.sh now write .core-manifest listing which agent
files were installed as core. The deprecation loop checks this manifest
before touching any file, so custom agents are never deprecated.
* Skip agent deprecation if target DEPRECATED file already exists
* Include skill count in updateme.sh summary condition and message
* Fix agents-registry.md paths in CLAUDE.md to use .claude/references/ prefix
* Add edit/remove/list trigger phrases to custom agent routing
* Deprecate stale core agents on reinstall before copying new ones
On reinstall (EXISTING=1), read the old .core-manifest and deprecate
any agent that is no longer shipped in the repo, before writing the
new manifest. Prevents stale core agents from lingering in the vault.
* Fix custom agent description: triggers are in user's language, not multilingual
* Fix updateme.sh: deprecate stale agents before rewriting manifest
The manifest was being truncated and rewritten before the deprecation
loop ran, so removed core agents were no longer in the manifest and
got skipped as "custom". Now: read old manifest -> deprecate -> copy
new agents -> rewrite manifest.
* Fix grep exit code handling when removing last entry from manifest
* Fix nested fenced code blocks in agent-template using tildes
* Add core-manifest for references to protect user-created reference docs
Same pattern as agents: launchme/updateme write a .core-manifest in
.claude/references/ listing installed core files. The deprecation loop
only touches files in the manifest, leaving user-created references
untouched.
* Move deprecated files to .claude/deprecated/ to prevent auto-discovery
Deprecated agents kept in .claude/agents/ could still be auto-discovered
by Claude Code via their frontmatter. Moving them to .claude/deprecated/
ensures they are completely invisible to the dispatcher while still
preserved for user reference.
* Harden updateme.sh from Copilot review feedback
Address multiple issues raised during PR code review:
- Skip deprecation entirely when .core-manifest is missing, preventing
accidental deprecation of custom agents/references on first update
- Preserve user's "## Custom Agents" sections in agents-registry.md and
agents.md during reference updates (merge strategy instead of overwrite)
- Update confirmation message to accurately reflect what is preserved
* Preserve custom agent content during install and update
- launchme.sh: skip overwriting agents-registry.md and agents.md on
reinstall to preserve custom agent entries
- updateme.sh: extract and re-insert custom table rows from the
registry table plus custom sections, preventing data loss when
updating from upstream
- Require manifest before deprecating to avoid false positives
* Update wardrobe-coach example phrase in README
* Use robust string matching and printf for user-mutable refs
- Replace grep -qw with bash substring match for filename detection
- Replace echo with printf '%s\n' to prevent content mangling
* Enforce step-by-step conversation in Architect and fix registry row reinsertion
- Add HARD CONSTRAINT blocks to both onboarding and custom agent creation
flows, forcing the use of AskUserQuestion for each question to prevent
the Architect from skipping phases or bundling questions
- Replace hard-coded "| postman |" match in updateme.sh with generic
last-table-row detection to avoid breaking custom row reinsertion if
core agents are renamed or reordered
* Improve input handling in launchme.sh and updateme.sh for non-interactive shells
* Extract 13 skills from agents and update full documentation
Architecture change: complex multi-step flows (onboarding, email triage,
transcription, etc.) are now skills that run in the main conversation
context instead of agent subprocesses. This fixes the state/context loss
that caused agents to skip phases during multi-turn conversations.
Skills created (13):
- Architect: /onboarding, /create-agent, /manage-agent, /defrag
- Postman: /email-triage, /meeting-prep, /weekly-agenda, /deadline-radar
- Transcriber: /transcribe
- Librarian: /vault-audit, /deep-clean, /tag-garden
- Sorter: /inbox-triage
Agent changes:
- architect.md: -70% (1554 → 473 lines)
- transcriber.md: -72% (530 → 147 lines)
- postman.md: -42%, librarian.md: -37%, sorter.md: -11%
- All agents: explicit post-it create-if-not-exists
Scripts:
- launchme.sh/updateme.sh: copy skills/ directly, remove generate-skills.py
Docs updated:
- README.md: new Skills section, mermaid diagrams, routing
- getting-started.md, examples.md: skill references
- docs/agents/*.md: capability tables with skill vs agent routing
- references/agents.md, agent-orchestration.md, agents-registry.md,
agent-template.md: skill registry, skill-first routing protocol
9.0 KiB
9.0 KiB
Getting Started with My Brain Is Full - Crew
A step-by-step guide for setting up your AI-powered vault. No technical background required.
What you need before starting
Required
- Obsidian: A free note-taking app. Download it at obsidian.md
- Claude Code: Anthropic's coding assistant. You need a Claude Pro, Max, or Team subscription.
- An Obsidian vault: This is just a folder on your computer where Obsidian stores your notes. If you don't have one yet, Obsidian will create one for you when you first open it.
- Git: A tool to download the project. On Mac, the terminal will prompt you to install it automatically the first time you use it. On Windows, download it from git-scm.com.
Optional (but recommended)
- Gmail account: If you want the Postman agent to process your emails
- Google Calendar: If you want calendar integration
Step 1: Install Obsidian
- Go to obsidian.md and download the app for your system (Mac, Windows, or Linux)
- Open Obsidian
- If this is your first time, click "Create new vault"
- Give it a name (e.g., "My Brain", "Second Brain", "Knowledge Base", whatever feels right)
- Choose where to save it on your computer
- Remember this location. You'll need it in Step 3
Install recommended plugins
Inside Obsidian:
- Go to Settings (gear icon, bottom left)
- Click Community plugins
- Click Browse
- Search for and install these plugins:
Essential (install these first):
| Plugin | What it does |
|---|---|
| Templater | Makes templates work with dynamic content (dates, etc.) |
| Dataview | Lets you query your notes like a database |
| Calendar | Visual calendar in the sidebar |
| Tasks | Better task management with due dates and queries |
Recommended (install when ready):
| Plugin | What it does |
|---|---|
| QuickAdd | Rapid note capture |
| Folder Notes | Index notes for folders |
| Tag Wrangler | Manage and rename tags in bulk |
| Periodic Notes | Weekly and monthly review notes |
| Omnisearch | Better search across your vault |
Don't worry if this feels like a lot. The Architect agent will remind you about missing plugins during setup.
Step 2: Install Claude Code
- Go to claude.ai/code and follow the instructions to install Claude Code
- You need a Claude Pro, Max, or Team subscription
- You can use either the Desktop app (Cowork) or the CLI (command-line interface). The Crew works on both
Step 3: Install the Crew
Open your terminal and navigate to your Obsidian vault folder:
cd /path/to/your-vault
Not sure how to open the terminal? On Mac, press
Command + Space, type "Terminal", and press Enter. On Windows, pressWindows + R, type "cmd", and press Enter.
Clone the repo inside your vault:
git clone https://github.com/gnekt/My-Brain-Is-Full-Crew.git
Run the installer:
cd My-Brain-Is-Full-Crew
bash scripts/launchme.sh
The script will ask two quick questions:
- Is this your vault folder? Confirm or enter the correct path
- Do you use Gmail or Google Calendar? Choose yes to set up the Postman integration
When it's done, your vault will look like this:
your-vault/
├── .claude/
│ ├── agents/ ← 8 lightweight crew agents
│ ├── skills/ ← 13 specialized skills for complex flows
│ └── references/ ← shared docs the agents read
├── CLAUDE.md ← project instructions
├── .mcp.json ← Gmail + Calendar (only if you said yes)
├── My-Brain-Is-Full-Crew/ ← the repo (for future updates)
└── ... your Obsidian notes
Something went wrong? The most common issue is that
gitisn't installed. On Mac, the terminal will prompt you to install it automatically. On Windows, download it from git-scm.com. If you're stuck, just show this page to a tech-savvy friend. It takes 60 seconds.
Step 4: Connect your vault
- Open Claude Code (CLI or Desktop)
- Open it inside your Obsidian vault folder. This is important: Claude needs to be in your vault to read and write your notes.
If you're using the CLI:
cd /path/to/your-vault
claude
If you're using Claude Code Desktop (Cowork), open the vault folder as your working directory.
Step 5: Initialize your vault
This is the fun part. Just type:
"Initialize my vault"
The /onboarding skill will kick in and the Architect will start a friendly conversation with you. It will ask:
About you
- What should I call you?
- What's your preferred language?
- What do you do? (student, professional, creative, researcher...)
- What brought you here? (overwhelm, organization, health, productivity...)
About your vault
- Are you new to Obsidian, or migrating from an existing vault?
- Do you want all 8 agents, or just some?
- What areas of your life do you want to manage?
About integrations (optional)
- Do you want email triage? (requires Gmail connection)
- Do you want calendar integration? (requires Google Calendar connection)
After the conversation, the Architect creates your entire vault structure, saves your profile, and leaves you a personalized welcome note.
Agent memory (Post-it)
Every agent has a small "post-it" file in Meta/states/ where it jots down notes for its next run. This means agents remember what they did last time: the Sorter knows which files it already triaged, the Scribe remembers what you were brainstorming about, the Architect knows which onboarding step you were on if the conversation was interrupted.
You don't need to manage these files — agents handle them automatically. Each post-it is limited to 30 lines, so they never grow out of control.
Step 6: Start using it
From now on, you just talk to Claude. Here are some things to try on your first day:
Capture some thoughts
"Save this: I had an idea about reorganizing the team standup. Maybe we should do async updates on Mondays and only meet on Wednesdays"
The Scribe will turn this into a clean note in your inbox.
Dump several things at once
"Quick notes: need to call the dentist, also Marco mentioned a book called Thinking Fast and Slow, and I should review the Q3 budget before Friday"
The Scribe detects multiple items and creates separate notes for each.
Check your email
"Check my email for anything important"
The /email-triage skill scans your Gmail, saves actionable emails, and gives you a summary.
File everything
"Triage my inbox"
The /inbox-triage skill processes all notes in your inbox and files them to the right places.
Search your brain
"What do I know about the Henderson project?"
The Seeker searches your vault and synthesizes an answer with source citations.
Step 7: Build daily habits
The Crew works best with simple daily routines:
Morning (2 minutes)
"Check my calendar for today" to see what's ahead "Any messages from the crew?" to check if agents flagged anything
Throughout the day
Just dump thoughts as they come. The Scribe handles the rest.
Evening (5 minutes)
"Triage my inbox" to let the Sorter file everything
Weekly (10 minutes)
"Weekly review" to run the
/vault-auditskill for a full vault health check
Troubleshooting
"The agent doesn't seem to activate"
Make sure Claude Code is open inside your vault folder (not a different directory). Verify agent files exist at .claude/agents/ and skill files at .claude/skills/ in your vault. Try saying the trigger phrase differently. Agents and skills understand natural language in multiple languages.
"Gmail/Calendar isn't working"
The Postman needs Gmail and Google Calendar MCP connectors. Run the installer again (bash scripts/launchme.sh) and answer yes to the Gmail/Calendar question, or manually copy .mcp.json from the repo to your vault root. Then authorize the connection when Claude Code prompts you.
"My vault structure looks different from the docs"
The Architect customizes the structure based on your onboarding answers.
"How do I update to a new version?"
cd /path/to/your-vault/My-Brain-Is-Full-Crew
git pull
bash scripts/updateme.sh
Only changed files are updated. Your vault notes are never touched.
"An agent did something weird"
Open an issue on GitHub with:
- What you asked
- What happened
- What you expected
"I want to change my profile"
"Update my profile" and the Architect will help you modify your settings
Next steps
- Examples: See real-world usage scenarios
- Mobile Access: Use the Crew from your phone
- Meet the Agents: Deep-dive into each agent's capabilities
- Contributing: Help make the Crew better
Remember: the best organizational system is the one you actually use. Start small. Talk to Claude. Let the Crew handle the rest.