My-Brain-Is-Full-Crew

smolkik_adm/My-Brain-Is-Full-Crew

Fork 0

mirror of https://github.com/gnekt/My-Brain-Is-Full-Crew.git synced 2026-08-26 02:04:43 +00:00

Commit Graph

Author	SHA1	Message	Date
Shachar Borenstein	340be6e497	feat: vault path tokenization — make the Crew work with any vault structure (#22 ) All 8 agents and 14 skills now use vault-role tokens ({{inbox}}, {{projects}}, {{areas}}, etc.) instead of hardcoded folder paths. Each file reads Meta/vault-map.md at runtime to resolve tokens to the user's actual folder names. Full backward compatibility: if vault-map.md is absent, agents fall back to built-in defaults. - Add Vault Path Resolution preamble to all 22 agent/skill files - Replace ~365 hardcoded folder paths with 11 vault-role tokens - Add docs/vault-mapping.md explaining the system and customization - Add Vault Path Resolution section to all dispatcher files - Add vault-token contributor rules to CONTRIBUTING.md - Update README.md with vault-mapping references - Add dispatcher backup logic to scripts/lib.sh Based on the approach by @sborenst, re-implemented on the current codebase. Co-authored-by: gnekt <dima9610@gmail.com> Co-authored-by: Shachar Borenstein <sborenst@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>	2026-05-10 13:04:11 +02:00
Giacomo Nunziati	53b605379e	feat: multi-platform adapter architecture (Claude Code, Gemini CLI, OpenCode) (#32 ) * Fix istall/update scripts * test: capture pre-refactor install snapshot for regression Adds take-snapshot.sh script and the resulting snapshot/ directory, capturing the exact vault state produced by launchme.sh before the framework-agnosticity refactor begins. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Summary: Refactor agents/skills/hooks/mcp in agentic-platform-agnostic templates. refactor: rename source CLAUDE.md → DISPATCHER.md (framework-neutral) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> refactor: convert agent frontmatter from tools: to neutral capabilities: Replace Claude Code-specific `tools:` frontmatter with framework-agnostic `mode: subagent` and `capabilities: [...]` in all 8 agent files. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> refactor: add neutral hook trigger manifests (.hook.yaml) refactor: hooks read neutral JSON schema (args.* instead of tool_input.) refactor: convert .mcp.json to neutral mcp/servers.yaml Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Implement agentic-platform adapters skeleton. build: add adapters/lib.sh skeleton with vocabulary constants test: bash test runner for adapter helpers Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(adapters): parse_frontmatter helper with tests Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(adapters): parse_capabilities helper with tests Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(adapters): should_include helper with tests Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(adapters): parse_hook_yaml helper with tests Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(adapters): agent_body helper with tests Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(adapters): enumerate_agents and enumerate_hooks helpers Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Implement agentic-platform adapter for Claude Code. build(adapters): claude-code adapter skeleton with capability/event tables build(claude-code): adapter_translate_dispatcher with test build(claude-code): adapter_translate_references with test build(claude-code): adapter_translate_skills with tests build(claude-code): adapter_translate_agents with capability→tools mapping build(claude-code): hook wrapper template (CC native → neutral schema) build(claude-code): adapter_translate_hooks with wrapper generation build(claude-code): adapter_translate_mcp with hand-rolled YAML parser build(claude-code): adapter_finalize and complete adapter_build wiring build: scripts/build.sh dispatches to per-framework adapter Also fix adapter_translate_hooks and adapter_translate_agents to use while-read loops (avoiding word-splitting on paths with spaces) and guard grep calls with \|\| true to survive set -eo pipefail when hooks have no match-tool field. Remove scripts/build.sh from .gitignore. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Refactor install/update scripts to support agentic-platform agnosticity. refactor(lib.sh): generalize install_claude_md → install_dispatcher New signature takes the full destination path instead of just the vault dir, allowing callers to install CLAUDE.md, AGENTS.md, or any dispatcher file to an explicit location. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> feat(launchme): support --framework flag, build dist/ before install Add --framework and --target arg parsing. Run build.sh before installing to populate dist/<framework>/. All install_* calls now read from dist/<framework>/ instead of the raw source dirs. MCP is now handled automatically by the adapter (no interactive prompt). Replaced install_claude_md with install_dispatcher. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> feat(updateme): support --framework flag, build dist/ before update Add --framework and --target arg parsing. Run build.sh before installing to populate dist/<framework>/. All install_* calls now read from dist/<framework>/ instead of raw source dirs. Replaced install_claude_md with install_dispatcher. Also fix set -e compatibility in lib.sh: add \|\| true to all conditional [[ ... ]] && info "..." logging lines so they don't abort the script when VERBOSE_COPY=0. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * test: regression runner diffs dist/claude-code against pre-refactor snapshot - Add tests/regression/run.sh that builds dist/claude-code and compares against snapshot, excluding runtime-only artifacts (.mbifc-manifest, .mcp.json, .claude-plugin/plugin.json) - Fix adapters/lib.sh agent_body: preserve '---' section dividers in body (awk now only skips '---' while still inside frontmatter, fm < 2) - Fix adapters/claude-code/adapter.sh: change 'read' capability to expand to only 'Read', appending 'Glob, Grep' at end of tools list to match snapshot ordering - Update snapshot to reflect intentional refactor changes: hook JSON schema (.args.* instead of .tool_input.), wrapper scripts, settings.json with wrapper paths, and consistent tool ordering for postman/sorter Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Implement opencode adapter. Co-Authored-By: win0na <winnie@winneon.moe> feat(lib.sh): add install_plugins helper for opencode JS plugins build(adapters): opencode adapter skeleton with capability/event tables build(opencode): adapter_translate_dispatcher (DISPATCHER.md → AGENTS.md) build(opencode): adapter_translate_references and adapter_translate_skills Implements Task 4 and Task 5: - adapter_translate_references: Copies reference markdown files to .opencode/references/ - adapter_translate_skills: Copies skill SKILL.md files to .opencode/skills/<name>/ with exclude filtering Both functions respect framework filtering via should_include(). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(opencode): adapter_translate_agents with capability→permission mapping Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(opencode): bash-executor template for spawning hook scripts build(opencode): plugin-stub template for mbifc-hooks.js build(opencode): adapter_translate_hooks with JS plugin generation Implements _oc_hook_registry_json and adapter_translate_hooks in the opencode adapter. Copies hook scripts to .opencode/hooks/, generates a single .opencode/plugins/mbifc-hooks.js by inlining bash-executor.js and synthesising a hook registry from .hook.yaml files. Uses python3 for template substitution to safely handle multi-line JS content. Adds 3 unit tests (copies scripts, registry entries, noop when no hooks dir). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(opencode): adapter_translate_mcp with local/remote handling build(opencode): adapter_finalize and complete adapter_build wiring Add adapter_finalize placeholder and wire adapter_translate_mcp into adapter_build; add end-to-end integration test (14/14 pass). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> feat(launchme): branch on --framework for opencode install layout Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> feat(updateme): branch on --framework for opencode install layout Mirror the same case "$FRAMEWORK" block from launchme.sh: framework-specific DIST_COMPONENTS_DIR, VAULT_COMPONENTS_DIR, DISPATCHER_SRC/DST, MCP_SRC/DST, HAS_PLUGINS; conditional install_plugins; conditional install_settings; framework-aware vault-setup check; framework-neutral summary messages. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Fix adapters to follow the same template. fix: restore adapter_build() contract, revert function renames Both adapters now export adapter_build() and adapter_translate_() as the uniform public contract. scripts/build.sh sources one adapter and calls adapter_build uniformly. Private helpers (_oc_) and vocabulary tables (cc_capability_to_tools, oc_capability_to_permission, etc.) retain their prefixes. CC regression and OC unit tests all pass. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> fix(tests): restore test_oc_ prefix on adapter_build end-to-end test * Fix agent format in opencode adapter * refactor: rename --framework to --platform across all scripts and tests Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Modify generic name for model tiers Co-Authored-By: win0na <winnie@winneon.moe> refactor: neutral model vocabulary (low/mid/high) in source agents feat(claude-code): cc_model_to_native() maps low/mid/high to haiku/sonnet/opus Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> feat(opencode): update oc_model_to_provider() for low/mid/high vocabulary Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Add gemini-cli adapter Co-Authored-By: win0na <winnie@winneon.moe> build(gemini-cli): adapter skeleton with capability/event/model tables build(gemini-cli): adapter_translate_dispatcher (DISPATCHER.md → GEMINI.md) build(gemini-cli): adapter_translate_references and adapter_translate_skills Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(gemini-cli): adapter_translate_agents with capability→tools mapping Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(gemini-cli): adapter_translate_hooks with wrapper scripts Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> feat(install): add gemini-cli platform to launchme.sh and updateme.sh Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Implement preserving config merge for opencode. Co-Authored-By: win0na <winnie@winneon.moe> feat(opencode): config-merge.sh with formatting-preserving JSON merge Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> build(opencode): source config-merge.sh from adapter Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> feat(install): use oc_config_merge for opencode.json instead of overwrite Source config-merge.sh from install scripts for opencode platform so user keys in opencode.json are preserved on reinstall and update. Fix in-place merge by writing to a temp file before moving to output. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Add mcp files to gitignore. * Fix claude-specific references in agents, skills and references * Fix: remove claude-specific reference from hooks. build: add platform_dir and dispatcher_name to all hook wrapper/plugin templates feat(hooks): platform-aware path checks using platform_dir and dispatcher_name from JSON input test: update regression snapshot for platform-aware hook wrappers and scripts * Added interactive platform choice in launchme, and platform auto-detection in updateme. * Fix: remove claude-specific references from documentation * Update documentation to reflect the new platform-agnostic architecture * fix: address Copilot review feedback on PR #32 - tests/run.sh: check source return code, report failures - tests/regression/run.sh: use mktemp + trap cleanup instead of fixed /tmp paths - tests/regression/run.sh: include .mcp.json in regression comparison - tests/regression/take-snapshot.sh: use --platform flag instead of stale scripted input - adapters/opencode/templates/plugin-stub.js.tmpl: include stdout in hook block error message * fix: address Copilot review round 2 - config-merge.sh: reword comment to only promise indentation preservation (not full formatting) - take-snapshot.sh: copy required artifacts explicitly, optional ones with existence check - adapters/lib.sh: document parse_hook_yaml single-trigger limitation * fix: address Copilot review round 3 - adapters/opencode/adapter.sh: replace python3 template substitution with pure bash (while-read loop with case matching), removing python3 dependency - adapters/lib.sh: should_include now falls back to plain YAML key read for files without frontmatter delimiters (fixes hook .yaml exclude: support) * fix: address Copilot review round 4 - scripts/launchme.sh: fix double-dot in FW_DIR_NAME display (basename already includes the dot, e.g. ".claude") - scripts/launchme.sh: replace undefined MCP_ANSWER with check on MCP_DST existence for summary banner --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-04-10 23:28:28 +02:00
Gnekt	1ee2dc415f	Add custom agent system with orchestration, templates, and broadened legal coverage (#21 ) * 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	2026-03-25 12:00:00 +01:00

Author

SHA1

Message

Date

Shachar Borenstein

340be6e497

feat: vault path tokenization — make the Crew work with any vault structure (#22 )

All 8 agents and 14 skills now use vault-role tokens ({{inbox}}, {{projects}},
{{areas}}, etc.) instead of hardcoded folder paths. Each file reads
Meta/vault-map.md at runtime to resolve tokens to the user's actual folder
names. Full backward compatibility: if vault-map.md is absent, agents fall
back to built-in defaults.

- Add Vault Path Resolution preamble to all 22 agent/skill files
- Replace ~365 hardcoded folder paths with 11 vault-role tokens
- Add docs/vault-mapping.md explaining the system and customization
- Add Vault Path Resolution section to all dispatcher files
- Add vault-token contributor rules to CONTRIBUTING.md
- Update README.md with vault-mapping references
- Add dispatcher backup logic to scripts/lib.sh

Based on the approach by @sborenst, re-implemented on the current codebase.

Co-authored-by: gnekt <dima9610@gmail.com>
Co-authored-by: Shachar Borenstein <sborenst@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

2026-05-10 13:04:11 +02:00

Giacomo Nunziati

53b605379e

feat: multi-platform adapter architecture (Claude Code, Gemini CLI, OpenCode) (#32 )

* Fix istall/update scripts

* test: capture pre-refactor install snapshot for regression

Adds take-snapshot.sh script and the resulting snapshot/ directory,
capturing the exact vault state produced by launchme.sh before the
framework-agnosticity refactor begins.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Summary: Refactor agents/skills/hooks/mcp in agentic-platform-agnostic templates.

refactor: rename source CLAUDE.md → DISPATCHER.md (framework-neutral)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

refactor: convert agent frontmatter from tools: to neutral capabilities:

Replace Claude Code-specific `tools:` frontmatter with framework-agnostic
`mode: subagent` and `capabilities: [...]` in all 8 agent files.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

refactor: add neutral hook trigger manifests (.hook.yaml)

refactor: hooks read neutral JSON schema (args.* instead of tool_input.*)

refactor: convert .mcp.json to neutral mcp/servers.yaml

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Implement agentic-platform adapters skeleton.

build: add adapters/lib.sh skeleton with vocabulary constants

test: bash test runner for adapter helpers

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(adapters): parse_frontmatter helper with tests

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(adapters): parse_capabilities helper with tests

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(adapters): should_include helper with tests

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(adapters): parse_hook_yaml helper with tests

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(adapters): agent_body helper with tests

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(adapters): enumerate_agents and enumerate_hooks helpers

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Implement agentic-platform adapter for Claude Code.

build(adapters): claude-code adapter skeleton with capability/event tables

build(claude-code): adapter_translate_dispatcher with test

build(claude-code): adapter_translate_references with test

build(claude-code): adapter_translate_skills with tests

build(claude-code): adapter_translate_agents with capability→tools mapping

build(claude-code): hook wrapper template (CC native → neutral schema)

build(claude-code): adapter_translate_hooks with wrapper generation

build(claude-code): adapter_translate_mcp with hand-rolled YAML parser

build(claude-code): adapter_finalize and complete adapter_build wiring

build: scripts/build.sh dispatches to per-framework adapter

Also fix adapter_translate_hooks and adapter_translate_agents to use
while-read loops (avoiding word-splitting on paths with spaces) and
guard grep calls with || true to survive set -eo pipefail when hooks
have no match-tool field. Remove scripts/build.sh from .gitignore.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Refactor install/update scripts to support agentic-platform agnosticity.

refactor(lib.sh): generalize install_claude_md → install_dispatcher

New signature takes the full destination path instead of just the vault
dir, allowing callers to install CLAUDE.md, AGENTS.md, or any dispatcher
file to an explicit location.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

feat(launchme): support --framework flag, build dist/ before install

Add --framework and --target arg parsing. Run build.sh before installing
to populate dist/<framework>/. All install_* calls now read from
dist/<framework>/ instead of the raw source dirs. MCP is now handled
automatically by the adapter (no interactive prompt). Replaced
install_claude_md with install_dispatcher.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

feat(updateme): support --framework flag, build dist/ before update

Add --framework and --target arg parsing. Run build.sh before installing
to populate dist/<framework>/. All install_* calls now read from
dist/<framework>/ instead of raw source dirs. Replaced install_claude_md
with install_dispatcher.

Also fix set -e compatibility in lib.sh: add || true to all conditional
[[ ... ]] && info "..." logging lines so they don't abort the script
when VERBOSE_COPY=0.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* test: regression runner diffs dist/claude-code against pre-refactor snapshot

- Add tests/regression/run.sh that builds dist/claude-code and compares
  against snapshot, excluding runtime-only artifacts (.mbifc-manifest,
  .mcp.json, .claude-plugin/plugin.json)
- Fix adapters/lib.sh agent_body: preserve '---' section dividers in body
  (awk now only skips '---' while still inside frontmatter, fm < 2)
- Fix adapters/claude-code/adapter.sh: change 'read' capability to expand
  to only 'Read', appending 'Glob, Grep' at end of tools list to match
  snapshot ordering
- Update snapshot to reflect intentional refactor changes: hook JSON schema
  (.args.* instead of .tool_input.*), wrapper scripts, settings.json with
  wrapper paths, and consistent tool ordering for postman/sorter

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Implement opencode adapter.

Co-Authored-By: win0na <winnie@winneon.moe>

feat(lib.sh): add install_plugins helper for opencode JS plugins

build(adapters): opencode adapter skeleton with capability/event tables

build(opencode): adapter_translate_dispatcher (DISPATCHER.md → AGENTS.md)

build(opencode): adapter_translate_references and adapter_translate_skills

Implements Task 4 and Task 5:
- adapter_translate_references: Copies reference markdown files to .opencode/references/
- adapter_translate_skills: Copies skill SKILL.md files to .opencode/skills/<name>/ with exclude filtering

Both functions respect framework filtering via should_include().

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(opencode): adapter_translate_agents with capability→permission mapping

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(opencode): bash-executor template for spawning hook scripts

build(opencode): plugin-stub template for mbifc-hooks.js

build(opencode): adapter_translate_hooks with JS plugin generation

Implements _oc_hook_registry_json and adapter_translate_hooks in the
opencode adapter. Copies hook scripts to .opencode/hooks/, generates a
single .opencode/plugins/mbifc-hooks.js by inlining bash-executor.js and
synthesising a hook registry from *.hook.yaml files. Uses python3 for
template substitution to safely handle multi-line JS content. Adds 3
unit tests (copies scripts, registry entries, noop when no hooks dir).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(opencode): adapter_translate_mcp with local/remote handling

build(opencode): adapter_finalize and complete adapter_build wiring

Add adapter_finalize placeholder and wire adapter_translate_mcp into
adapter_build; add end-to-end integration test (14/14 pass).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

feat(launchme): branch on --framework for opencode install layout

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

feat(updateme): branch on --framework for opencode install layout

Mirror the same case "$FRAMEWORK" block from launchme.sh: framework-specific
DIST_COMPONENTS_DIR, VAULT_COMPONENTS_DIR, DISPATCHER_SRC/DST, MCP_SRC/DST,
HAS_PLUGINS; conditional install_plugins; conditional install_settings;
framework-aware vault-setup check; framework-neutral summary messages.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Fix adapters to follow the same template.

fix: restore adapter_build() contract, revert function renames

Both adapters now export adapter_build() and adapter_translate_*() as
the uniform public contract. scripts/build.sh sources one adapter and
calls adapter_build uniformly. Private helpers (_oc_*) and vocabulary
tables (cc_capability_to_tools, oc_capability_to_permission, etc.)
retain their prefixes. CC regression and OC unit tests all pass.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

fix(tests): restore test_oc_ prefix on adapter_build end-to-end test

* Fix agent format in opencode adapter

* refactor: rename --framework to --platform across all scripts and tests

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Modify generic name for model tiers

Co-Authored-By: win0na <winnie@winneon.moe>

refactor: neutral model vocabulary (low/mid/high) in source agents

feat(claude-code): cc_model_to_native() maps low/mid/high to haiku/sonnet/opus

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

feat(opencode): update oc_model_to_provider() for low/mid/high vocabulary

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Add gemini-cli adapter

Co-Authored-By: win0na <winnie@winneon.moe>

build(gemini-cli): adapter skeleton with capability/event/model tables

build(gemini-cli): adapter_translate_dispatcher (DISPATCHER.md → GEMINI.md)

build(gemini-cli): adapter_translate_references and adapter_translate_skills

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(gemini-cli): adapter_translate_agents with capability→tools mapping

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(gemini-cli): adapter_translate_hooks with wrapper scripts

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

feat(install): add gemini-cli platform to launchme.sh and updateme.sh

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Implement preserving config merge for opencode.

Co-Authored-By: win0na <winnie@winneon.moe>

feat(opencode): config-merge.sh with formatting-preserving JSON merge

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

build(opencode): source config-merge.sh from adapter

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

feat(install): use oc_config_merge for opencode.json instead of overwrite

Source config-merge.sh from install scripts for opencode platform so
user keys in opencode.json are preserved on reinstall and update.
Fix in-place merge by writing to a temp file before moving to output.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Add mcp files to gitignore.

* Fix claude-specific references in agents, skills and references

* Fix: remove claude-specific reference from hooks.

build: add platform_dir and dispatcher_name to all hook wrapper/plugin templates

feat(hooks): platform-aware path checks using platform_dir and dispatcher_name from JSON input

test: update regression snapshot for platform-aware hook wrappers and scripts

* Added interactive platform choice in launchme, and platform auto-detection in updateme.

* Fix: remove claude-specific references from documentation

* Update documentation to reflect the new platform-agnostic architecture

* fix: address Copilot review feedback on PR #32

- tests/run.sh: check source return code, report failures
- tests/regression/run.sh: use mktemp + trap cleanup instead of fixed /tmp paths
- tests/regression/run.sh: include .mcp.json in regression comparison
- tests/regression/take-snapshot.sh: use --platform flag instead of stale scripted input
- adapters/opencode/templates/plugin-stub.js.tmpl: include stdout in hook block error message

* fix: address Copilot review round 2

- config-merge.sh: reword comment to only promise indentation preservation (not full formatting)
- take-snapshot.sh: copy required artifacts explicitly, optional ones with existence check
- adapters/lib.sh: document parse_hook_yaml single-trigger limitation

* fix: address Copilot review round 3

- adapters/opencode/adapter.sh: replace python3 template substitution with
  pure bash (while-read loop with case matching), removing python3 dependency
- adapters/lib.sh: should_include now falls back to plain YAML key read for
  files without frontmatter delimiters (fixes hook .yaml exclude: support)

* fix: address Copilot review round 4

- scripts/launchme.sh: fix double-dot in FW_DIR_NAME display (basename
  already includes the dot, e.g. ".claude")
- scripts/launchme.sh: replace undefined MCP_ANSWER with check on MCP_DST
  existence for summary banner

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-10 23:28:28 +02:00

Gnekt

1ee2dc415f

Add custom agent system with orchestration, templates, and broadened legal coverage (#21 )

* 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

2026-03-25 12:00:00 +01:00

3 Commits