mirror of
https://github.com/gnekt/My-Brain-Is-Full-Crew.git
synced 2026-08-26 02:04:43 +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
6.6 KiB
6.6 KiB
Real-World Usage Examples
Practical scenarios showing how the Crew works in daily life. Each example shows what you say and what happens behind the scenes.
Scenario 1: The Brain Dump
Situation: You just got out of a meeting and your head is full of scattered thoughts.
You say:
"Quick dump: Marco wants the API docs by Thursday, Lisa mentioned the budget is getting cut by 15%, I had an idea about using webhooks instead of polling for the notification system, and I need to book a dentist appointment"
What happens:
- Scribe detects 4 distinct items
- Creates 4 separate notes:
Task: API Docs for Marco.md(with deadline: Thursday, linked to[[Marco]])Note: Budget Cut 15 Percent.md(tagged with #budget, linked to[[Lisa]])Idea: Webhooks for Notifications.md(tagged with #architecture, #notifications)Task: Book Dentist Appointment.md(tagged with #personal, #health)
- All notes land in
00-Inbox/with proper frontmatter - Scribe reports: "Captured 4 notes: 2 tasks, 1 idea, 1 informational note. Shall I save them?"
Scenario 2: Evening Inbox Triage
Situation: End of the day. Your inbox has accumulated 12 notes.
You say:
"Triage my inbox"
What happens:
- The
/inbox-triageskill scans all 12 notes in00-Inbox/ - Reads each note's content and frontmatter
- Files them:
- 3 meeting notes go to
06-Meetings/2026/03/ - 2 project tasks go to
01-Projects/Rebrand/ - 1 person note goes to
05-People/ - 2 ideas go to
03-Resources/Ideas/ - 2 ambiguous notes are kept in inbox with questions for you
- 3 meeting notes go to
- Updates 3 MOCs that gained new entries
- Leaves a message for Connector to check new links
- Reports the full summary with a clear breakdown
Scenario 3: Meeting Transcription
Situation: You recorded a 45-minute sprint planning meeting and pasted the raw transcript.
You say:
"Transcribe this meeting, it was the Q2 sprint planning with Marco, Lisa, and Ahmed. We met today at 10am."
[pastes raw transcript]
What happens:
- The
/transcribeskill processes the raw text - Identifies speakers from context
- Generates:
- Executive summary (4 sentences)
- 8 key discussion points
- 3 decisions made (with who decided and conditions)
- Action items table (6 tasks, assigned to specific people, with deadlines)
- Detailed notes organized by topic
- 2 open questions for follow-up
- Creates wikilinks to all participants:
[[Marco]],[[Lisa]],[[Ahmed]] - Saves to
00-Inbox/as2026-03-21, Meeting, Q2 Sprint Planning.md - Leaves message for Postman: "Check if there were pre-meeting emails about Q2 planning"
Scenario 4: Email Triage
Situation: Monday morning. You want to know what's important in your email.
You say:
"Check my email for anything urgent"
What happens:
- The
/email-triageskill scans your Gmail inbox (last 48 hours) - Reads 34 emails
- Filters:
- 22 newsletters/promos/notifications are ignored
- 3 action requests are saved as notes with tasks
- 2 deadline reminders are saved with deadline tags
- 4 informational emails from key contacts are saved as reference notes
- 1 meeting invitation is saved and flagged for calendar sync
- 2 ambiguous emails are summarized for your decision
- All notes land in
00-Inbox/ - Creates wikilinks to people in
05-People/ - Reports: "34 emails scanned. 10 saved to vault (3 urgent, 2 deadlines, 4 info, 1 meeting). 22 filtered out. 2 need your input."
Scenario 7: Knowledge Discovery
Situation: You're writing a proposal and need context from your notes.
You say:
"What do I know about microservices architecture? I need to write a proposal."
What happens:
- Seeker searches your entire vault
- Finds 7 relevant notes across different areas:
- 2 meeting notes where architecture was discussed
- 1 resource note on microservices patterns
- 3 project notes that reference architectural decisions
- 1 archived note from a past project
- Synthesizes: "Based on your notes, here's what you've documented about microservices..."
- Provides a structured summary with source citations (
[[Meeting: Architecture Review]], etc.) - Identifies a gap: "Note: your vault has no notes on service mesh or container orchestration. You might want to add these to your proposal research."
Scenario 8: Weekly Review
Situation: Sunday morning. Time for your weekly vault check-up.
You say:
"Run the weekly review"
What happens:
- The
/vault-auditskill runs a multi-phase audit:- Structure scan: all folders intact
- Duplicate detection: found 1 near-duplicate
- Link integrity: 3 broken links fixed automatically, 2 orphan notes flagged
- Frontmatter audit: 5 notes missing tags (auto-fixed)
- MOC review: 2 MOCs updated with new entries
- Growth analytics: 23 notes added this week, vault health score: 94%
- Generates a health report saved to
Meta/health-reports/ - Reports: "Your vault is in great shape! 1 duplicate needs your decision, 2 orphan notes might need homes. Everything else is handled."
Scenario 10: Graph Intelligence
Situation: You want to understand how your knowledge connects.
You say:
"Analyze my vault graph and find missing connections"
What happens:
- Connector runs a full graph audit
- Reports:
- 247 notes, 412 links, average 1.7 links per note
- 18 orphan notes (7%, under the 10% target)
- 3 isolated clusters
- Top connected note: your MOC/Engineering with 23 links
- Discovers 12 suggested connections:
- 4 strong (should definitely be linked)
- 5 medium (probably useful)
- 3 serendipitous (unexpected but interesting)
- Presents each with explanation: "Your note on 'Team Communication Patterns' should link to 'Sprint Retrospective Q1', because both discuss the same communication breakdown from different angles."
Daily Workflow Cheat Sheet
| Time | What to say | Skill/Agent |
|---|---|---|
| Morning | "What's on my calendar today?" | Postman agent |
| Morning | "Check my email" | /email-triage skill |
| Any time | "Save this: [thought]" | Scribe agent |
| After meeting | "Transcribe this meeting: [paste]" | /transcribe skill |
| Evening | "Triage my inbox" | /inbox-triage skill |
| Weekly | "Weekly review" | /vault-audit skill |
| When lost | "Find [topic]" | Seeker agent |
| When stuck | "Find connections for [note]" | Connector agent |
These are just examples. The beauty of the Crew is that you don't need to memorize commands. Just talk naturally, and the right agent will pick it up.