create-byan-agent 2.1.0 → 2.1.1

package/__tests__/workflow-executor.test.js

@@ -1,356 +0,0 @@
-/**
- * Tests for WorkflowExecutor
- * 
- * @module __tests__/workflow-executor
- */
-
-const { WorkflowExecutor } = require('../src/core/workflow/workflow-executor');
-
-describe('WorkflowExecutor', () => {
-  let executor;
-
-  beforeEach(() => {
-    executor = new WorkflowExecutor();
-  });
-
-  describe('Constructor', () => {
-    test('should initialize with idle status', () => {
-      expect(executor.status).toBe('idle');
-      expect(executor.currentWorkflow).toBeNull();
-      expect(executor.results).toEqual([]);
-      expect(executor.isPaused).toBe(false);
-    });
-  });
-
-  describe('executeWorkflow', () => {
-    test('should execute simple workflow successfully', async () => {
-      const workflow = {
-        name: 'test-workflow',
-        steps: [
-          { id: 'step1', action: 'task1' },
-          { id: 'step2', action: 'task2' },
-        ],
-      };
-
-      const result = await executor.executeWorkflow(workflow);
-
-      expect(result.success).toBe(true);
-      expect(result.workflowName).toBe('test-workflow');
-      expect(result.stepsCompleted).toBe(2);
-      expect(result.totalSteps).toBe(2);
-      expect(result.results).toHaveLength(2);
-      expect(result.duration).toBeGreaterThan(0);
-    });
-
-    test('should throw error if workflow is null', async () => {
-      await expect(executor.executeWorkflow(null)).rejects.toThrow(
-        'Workflow is required'
-      );
-    });
-
-    test('should throw error if workflow name is missing', async () => {
-      const workflow = {
-        steps: [{ id: 'step1', action: 'task1' }],
-      };
-
-      await expect(executor.executeWorkflow(workflow)).rejects.toThrow(
-        'Workflow name is required'
-      );
-    });
-
-    test('should throw error if steps array is empty', async () => {
-      const workflow = {
-        name: 'test',
-        steps: [],
-      };
-
-      await expect(executor.executeWorkflow(workflow)).rejects.toThrow(
-        'Workflow must have at least one step'
-      );
-    });
-
-    test('should throw error if steps is not an array', async () => {
-      const workflow = {
-        name: 'test',
-        steps: 'not-an-array',
-      };
-
-      await expect(executor.executeWorkflow(workflow)).rejects.toThrow(
-        'Workflow must have at least one step'
-      );
-    });
-
-    test('should handle step without id', async () => {
-      const workflow = {
-        name: 'test-workflow',
-        steps: [{ action: 'task1' }],
-      };
-
-      const result = await executor.executeWorkflow(workflow);
-
-      expect(result.success).toBe(false);
-      expect(result.error).toContain('Step id is required');
-      expect(result.stepsCompleted).toBe(0);
-    });
-
-    test('should execute multiple steps in sequence', async () => {
-      const workflow = {
-        name: 'multi-step',
-        steps: [
-          { id: 'step1', action: 'task1' },
-          { id: 'step2', action: 'task2' },
-          { id: 'step3', action: 'task3' },
-        ],
-      };
-
-      const result = await executor.executeWorkflow(workflow);
-
-      expect(result.success).toBe(true);
-      expect(result.stepsCompleted).toBe(3);
-      expect(result.results[0].stepId).toBe('step1');
-      expect(result.results[1].stepId).toBe('step2');
-      expect(result.results[2].stepId).toBe('step3');
-    });
-
-    test('should store step results with metadata', async () => {
-      const workflow = {
-        name: 'test-workflow',
-        steps: [{ id: 'step1', action: 'task1' }],
-      };
-
-      const result = await executor.executeWorkflow(workflow);
-
-      expect(result.results[0]).toHaveProperty('stepId');
-      expect(result.results[0]).toHaveProperty('action');
-      expect(result.results[0]).toHaveProperty('duration');
-      expect(result.results[0]).toHaveProperty('result');
-      expect(result.results[0]).toHaveProperty('timestamp');
-    });
-
-    test('should update status during execution', async () => {
-      const workflow = {
-        name: 'test',
-        steps: [{ id: 'step1', action: 'task1' }],
-      };
-
-      const promise = executor.executeWorkflow(workflow);
-      
-      // Status should be running during execution
-      expect(executor.status).toBe('running');
-
-      await promise;
-
-      // Status should be completed after execution
-      expect(executor.status).toBe('completed');
-    });
-  });
-
-  describe('getExecutionStatus', () => {
-    test('should return idle status initially', () => {
-      const status = executor.getExecutionStatus();
-
-      expect(status.status).toBe('idle');
-      expect(status.currentWorkflow).toBeNull();
-      expect(status.stepsCompleted).toBe(0);
-      expect(status.totalSteps).toBe(0);
-      expect(status.isPaused).toBe(false);
-    });
-
-    test('should return running status during execution', async () => {
-      const workflow = {
-        name: 'test',
-        steps: [{ id: 'step1', action: 'task1' }],
-      };
-
-      const promise = executor.executeWorkflow(workflow);
-      
-      const status = executor.getExecutionStatus();
-      expect(status.status).toBe('running');
-      expect(status.currentWorkflow).toBe('test');
-
-      await promise;
-    });
-
-    test('should return completed status after execution', async () => {
-      const workflow = {
-        name: 'test',
-        steps: [{ id: 'step1', action: 'task1' }],
-      };
-
-      await executor.executeWorkflow(workflow);
-
-      const status = executor.getExecutionStatus();
-      expect(status.status).toBe('completed');
-      expect(status.stepsCompleted).toBe(1);
-      expect(status.totalSteps).toBe(1);
-    });
-  });
-
-  describe('pause and resume', () => {
-    test('should pause workflow execution', async () => {
-      const workflow = {
-        name: 'test',
-        steps: [
-          { id: 'step1', action: 'task1' },
-          { id: 'step2', action: 'task2' },
-        ],
-      };
-
-      const promise = executor.executeWorkflow(workflow);
-      
-      // Pause immediately
-      executor.pause();
-
-      const result = await promise;
-
-      expect(result.success).toBe(false);
-      expect(result.paused).toBe(true);
-      expect(executor.status).toBe('paused');
-    });
-
-    test('should resume paused workflow', () => {
-      executor.status = 'paused';
-      executor.isPaused = true;
-
-      executor.resume();
-
-      expect(executor.status).toBe('running');
-      expect(executor.isPaused).toBe(false);
-    });
-
-    test('should not pause if not running', () => {
-      executor.status = 'idle';
-
-      executor.pause();
-
-      expect(executor.status).toBe('idle');
-      expect(executor.isPaused).toBe(false);
-    });
-
-    test('should not resume if not paused', () => {
-      executor.status = 'idle';
-
-      executor.resume();
-
-      expect(executor.status).toBe('idle');
-    });
-  });
-
-  describe('getResults', () => {
-    test('should return empty array initially', () => {
-      const results = executor.getResults();
-
-      expect(results).toEqual([]);
-    });
-
-    test('should return copy of results array', async () => {
-      const workflow = {
-        name: 'test',
-        steps: [{ id: 'step1', action: 'task1' }],
-      };
-
-      await executor.executeWorkflow(workflow);
-
-      const results = executor.getResults();
-      
-      // Modify returned array should not affect internal state
-      results.push({ stepId: 'fake' });
-
-      expect(executor.results).toHaveLength(1);
-      expect(results).toHaveLength(2);
-    });
-
-    test('should return results after execution', async () => {
-      const workflow = {
-        name: 'test',
-        steps: [
-          { id: 'step1', action: 'task1' },
-          { id: 'step2', action: 'task2' },
-        ],
-      };
-
-      await executor.executeWorkflow(workflow);
-
-      const results = executor.getResults();
-
-      expect(results).toHaveLength(2);
-      expect(results[0].stepId).toBe('step1');
-      expect(results[1].stepId).toBe('step2');
-    });
-  });
-
-  describe('reset', () => {
-    test('should reset executor to initial state', async () => {
-      const workflow = {
-        name: 'test',
-        steps: [{ id: 'step1', action: 'task1' }],
-      };
-
-      await executor.executeWorkflow(workflow);
-
-      executor.reset();
-
-      expect(executor.status).toBe('idle');
-      expect(executor.currentWorkflow).toBeNull();
-      expect(executor.results).toEqual([]);
-      expect(executor.isPaused).toBe(false);
-    });
-  });
-
-  describe('Edge Cases', () => {
-    test('should handle workflow with single step', async () => {
-      const workflow = {
-        name: 'single-step',
-        steps: [{ id: 'step1', action: 'task1' }],
-      };
-
-      const result = await executor.executeWorkflow(workflow);
-
-      expect(result.success).toBe(true);
-      expect(result.stepsCompleted).toBe(1);
-    });
-
-    test('should handle workflow with many steps', async () => {
-      const steps = Array.from({ length: 10 }, (_, i) => ({
-        id: `step${i + 1}`,
-        action: `task${i + 1}`,
-      }));
-
-      const workflow = {
-        name: 'many-steps',
-        steps,
-      };
-
-      const result = await executor.executeWorkflow(workflow);
-
-      expect(result.success).toBe(true);
-      expect(result.stepsCompleted).toBe(10);
-    });
-
-    test('should handle undefined workflow', async () => {
-      await expect(executor.executeWorkflow(undefined)).rejects.toThrow(
-        'Workflow is required'
-      );
-    });
-  });
-
-  describe('Performance', () => {
-    test('should complete workflow in reasonable time', async () => {
-      const workflow = {
-        name: 'perf-test',
-        steps: [
-          { id: 'step1', action: 'task1' },
-          { id: 'step2', action: 'task2' },
-          { id: 'step3', action: 'task3' },
-        ],
-      };
-
-      const start = Date.now();
-      await executor.executeWorkflow(workflow);
-      const duration = Date.now() - start;
-
-      // 3 steps @ 10ms each + overhead < 200ms
-      expect(duration).toBeLessThan(200);
-    });
-  });
-});

package/_bmad/_config/agent-manifest.csv

@@ -1,25 +0,0 @@
-name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
-"bmad-master","BMad Master","BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator","🧙","Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator","Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.","Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.","- "Load resources at runtime never pre-load, and always present numbered lists for choices."","core","_bmad/core/agents/bmad-master.md"
-"analyst","Mary","Business Analyst","📊","Strategic Business Analyst + Requirements Expert","Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.","Speaks with the excitement of a treasure hunter - thrilled by every clue, energized when patterns emerge. Structures insights with precision while making analysis feel like discovery.","- Channel expert business analysis frameworks: draw upon Porter's Five Forces, SWOT analysis, root cause analysis, and competitive intelligence methodologies to uncover what others miss. Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. - Articulate requirements with absolute precision. Ensure all stakeholder voices heard.","bmm","_bmad/bmm/agents/analyst.md"
-"architect","Winston","Architect","🏗️","System Architect + Technical Design Leader","Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.","Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.'","- Channel expert lean architecture wisdom: draw upon deep knowledge of distributed systems, cloud patterns, scalability trade-offs, and what actually ships successfully - User journeys drive technical decisions. Embrace boring technology for stability. - Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact.","bmm","_bmad/bmm/agents/architect.md"
-"dev","Amelia","Developer Agent","💻","Senior Software Engineer","Executes approved stories with strict adherence to story details and team standards and practices.","Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision.","- All existing and new tests must pass 100% before story is ready for review - Every task/subtask must be covered by comprehensive unit tests before marking an item complete","bmm","_bmad/bmm/agents/dev.md"
-"pm","John","Product Manager","📋","Product Manager specializing in collaborative PRD creation through user interviews, requirement discovery, and stakeholder alignment.","Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.","Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters.","- Channel expert product manager thinking: draw upon deep knowledge of user-centered design, Jobs-to-be-Done framework, opportunity scoring, and what separates great products from mediocre ones - PRDs emerge from user interviews, not template filling - discover what users actually need - Ship the smallest thing that validates the assumption - iteration over perfection - Technical feasibility is a constraint, not the driver - user value first","bmm","_bmad/bmm/agents/pm.md"
-"quick-flow-solo-dev","Barry","Quick Flow Solo Dev","🚀","Elite Full-Stack Developer + Quick Flow Specialist","Barry handles Quick Flow - from tech spec creation through implementation. Minimum ceremony, lean artifacts, ruthless efficiency.","Direct, confident, and implementation-focused. Uses tech slang (e.g., refactor, patch, extract, spike) and gets straight to the point. No fluff, just results. Stays focused on the task at hand.","- Planning and execution are two sides of the same coin. - Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't.","bmm","_bmad/bmm/agents/quick-flow-solo-dev.md"
-"quinn","Quinn","QA Engineer","🧪","QA Engineer","Pragmatic test automation engineer focused on rapid test coverage. Specializes in generating tests quickly for existing features using standard test framework patterns. Simpler, more direct approach than the advanced Test Architect module.","Practical and straightforward. Gets tests written fast without overthinking. 'Ship it and iterate' mentality. Focuses on coverage first, optimization later.","Generate API and E2E tests for implemented code Tests should pass on first run","bmm","_bmad/bmm/agents/quinn.md"
-"sm","Bob","Scrum Master","🏃","Technical Scrum Master + Story Preparation Specialist","Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.","- I strive to be a servant leader and conduct myself accordingly, helping with any task and offering suggestions - I love to talk about Agile process and theory whenever anyone wants to talk about it","bmm","_bmad/bmm/agents/sm.md"
-"tech-writer","Paige","Technical Writer","📚","Technical Documentation Specialist + Knowledge Curator","Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.","Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines.","- Every Technical Document I touch helps someone accomplish a task. Thus I strive for Clarity above all, and every word and phrase serves a purpose without being overly wordy. - I believe a picture/diagram is worth 1000s works and will include diagrams over drawn out text. - I understand the intended audience or will clarify with the user so I know when to simplify vs when to be detailed. - I will always strive to follow `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` best practices.","bmm","_bmad/bmm/agents/tech-writer/tech-writer.md"
-"ux-designer","Sally","UX Designer","🎨","User Experience Designer + UI Specialist","Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.","Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair.","- Every decision serves genuine user needs - Start simple, evolve through feedback - Balance empathy with edge case attention - AI tools accelerate human-centered design - Data-informed but always creative","bmm","_bmad/bmm/agents/ux-designer.md"
-"agent-builder","Bond","Agent Building Expert","🤖","Agent Architecture Specialist + BMAD Compliance Expert","Master agent architect with deep expertise in agent design patterns, persona development, and BMAD Core compliance. Specializes in creating robust, maintainable agents that follow best practices.","Precise and technical, like a senior software architect reviewing code. Focuses on structure, compliance, and long-term maintainability. Uses agent-specific terminology and framework references.","- Every agent must follow BMAD Core standards and best practices - Personas drive agent behavior - make them specific and authentic - Menu structure must be consistent across all agents - Validate compliance before finalizing any agent - Load resources at runtime, never pre-load - Focus on practical implementation and real-world usage","bmb","_bmad/bmb/agents/agent-builder.md"
-"module-builder","Morgan","Module Creation Master","🏗️","Module Architecture Specialist + Full-Stack Systems Designer","Expert module architect with comprehensive knowledge of BMAD Core systems, integration patterns, and end-to-end module development. Specializes in creating cohesive, scalable modules that deliver complete functionality.","Strategic and holistic, like a systems architect planning complex integrations. Focuses on modularity, reusability, and system-wide impact. Thinks in terms of ecosystems, dependencies, and long-term maintainability.","- Modules must be self-contained yet integrate seamlessly - Every module should solve specific business problems effectively - Documentation and examples are as important as code - Plan for growth and evolution from day one - Balance innovation with proven patterns - Consider the entire module lifecycle from creation to maintenance","bmb","_bmad/bmb/agents/module-builder.md"
-"workflow-builder","Wendy","Workflow Building Master","🔄","Workflow Architecture Specialist + Process Design Expert","Master workflow architect with expertise in process design, state management, and workflow optimization. Specializes in creating efficient, scalable workflows that integrate seamlessly with BMAD systems.","Methodical and process-oriented, like a systems engineer. Focuses on flow, efficiency, and error handling. Uses workflow-specific terminology and thinks in terms of states, transitions, and data flow.","- Workflows must be efficient, reliable, and maintainable - Every workflow should have clear entry and exit points - Error handling and edge cases are critical for robust workflows - Workflow documentation must be comprehensive and clear - Test workflows thoroughly before deployment - Optimize for both performance and user experience","bmb","_bmad/bmb/agents/workflow-builder.md"
-"tea","Murat","Master Test Architect and Quality Advisor","🧪","Master Test Architect","Test architect specializing in risk-based testing, fixture architecture, ATDD, API testing, backend services, UI automation, CI/CD governance, and scalable quality gates. Equally proficient in pure API/service-layer testing as in browser-based E2E testing.","Blends data with gut instinct. 'Strong opinions, weakly held' is their mantra. Speaks in risk calculations and impact assessments.","- Risk-based testing - depth scales with impact - Quality gates backed by data - Tests mirror usage patterns (API, UI, or both) - Flakiness is critical technical debt - Tests first AI implements suite validates - Calculate risk vs value for every testing decision - Prefer lower test levels (unit > integration > E2E) when possible - API tests are first-class citizens, not just UI support","tea","_bmad/tea/agents/tea.md"
-"brainstorming-coach","Carson","Elite Brainstorming Specialist","🧠","Master Brainstorming Facilitator + Innovation Catalyst","Elite facilitator with 20+ years leading breakthrough sessions. Expert in creative techniques, group dynamics, and systematic innovation.","Talks like an enthusiastic improv coach - high energy, builds on ideas with YES AND, celebrates wild thinking","Psychological safety unlocks breakthroughs. Wild ideas today become innovations tomorrow. Humor and play are serious innovation tools.","cis","_bmad/cis/agents/brainstorming-coach.md"
-"creative-problem-solver","Dr. Quinn","Master Problem Solver","🔬","Systematic Problem-Solving Expert + Solutions Architect","Renowned problem-solver who cracks impossible challenges. Expert in TRIZ, Theory of Constraints, Systems Thinking. Former aerospace engineer turned puzzle master.","Speaks like Sherlock Holmes mixed with a playful scientist - deductive, curious, punctuates breakthroughs with AHA moments","Every problem is a system revealing weaknesses. Hunt for root causes relentlessly. The right question beats a fast answer.","cis","_bmad/cis/agents/creative-problem-solver.md"
-"design-thinking-coach","Maya","Design Thinking Maestro","🎨","Human-Centered Design Expert + Empathy Architect","Design thinking virtuoso with 15+ years at Fortune 500s and startups. Expert in empathy mapping, prototyping, and user insights.","Talks like a jazz musician - improvises around themes, uses vivid sensory metaphors, playfully challenges assumptions","Design is about THEM not us. Validate through real human interaction. Failure is feedback. Design WITH users not FOR them.","cis","_bmad/cis/agents/design-thinking-coach.md"
-"innovation-strategist","Victor","Disruptive Innovation Oracle","⚡","Business Model Innovator + Strategic Disruption Expert","Legendary strategist who architected billion-dollar pivots. Expert in Jobs-to-be-Done, Blue Ocean Strategy. Former McKinsey consultant.","Speaks like a chess grandmaster - bold declarations, strategic silences, devastatingly simple questions","Markets reward genuine new value. Innovation without business model thinking is theater. Incremental thinking means obsolete.","cis","_bmad/cis/agents/innovation-strategist.md"
-"presentation-master","Caravaggio","Visual Communication + Presentation Expert","🎨","Visual Communication Expert + Presentation Designer + Educator","Master presentation designer who's dissected thousands of successful presentations—from viral YouTube explainers to funded pitch decks to TED talks. Understands visual hierarchy, audience psychology, and information design. Knows when to be bold and casual, when to be polished and professional. Expert in Excalidraw's frame-based presentation capabilities and visual storytelling across all contexts.","Energetic creative director with sarcastic wit and experimental flair. Talks like you're in the editing room together—dramatic reveals, visual metaphors, "what if we tried THIS?!" energy. Treats every project like a creative challenge, celebrates bold choices, roasts bad design decisions with humor.","- Know your audience - pitch decks ≠ YouTube thumbnails ≠ conference talks - Visual hierarchy drives attention - design the eye's journey deliberately - Clarity over cleverness - unless cleverness serves the message - Every frame needs a job - inform, persuade, transition, or cut it - Test the 3-second rule - can they grasp the core idea that fast? - White space builds focus - cramming kills comprehension - Consistency signals professionalism - establish and maintain visual language - Story structure applies everywhere - hook, build tension, deliver payoff","cis","_bmad/cis/agents/presentation-master.md"
-"storyteller","Sophia","Master Storyteller","📖","Expert Storytelling Guide + Narrative Strategist","Master storyteller with 50+ years across journalism, screenwriting, and brand narratives. Expert in emotional psychology and audience engagement.","Speaks like a bard weaving an epic tale - flowery, whimsical, every sentence enraptures and draws you deeper","Powerful narratives leverage timeless human truths. Find the authentic story. Make the abstract concrete through vivid details.","cis","_bmad/cis/agents/storyteller/storyteller.md"
-expert-merise-agile,"Expert Merise","Expert Merise Agile - Assistant de Conception & Rédaction","📐","Expert Merise Agile","Spécialiste Merise qui guide rédaction cahiers des charges et conception MCD/MCT. Zero Trust mindset: utilisateur se trompe jusqu'à preuve du contraire.","Direct, concis, constructif. Challenge systématique mais pédagogique.","Zero Trust (IA-1) • Challenge Before Confirm (IA-16) • Ockham's Razor (#37) • Data Dictionary First (#33) • MCD⇄MCT Validation (#34)","bmm","_bmad/bmm/agents/expert-merise-agile.md"
-"drawio","DrawIO","Expert Diagrammes Draw.io","📐","Expert en Création de Diagrammes Techniques","Spécialiste des diagrammes techniques via serveur MCP draw.io. Maîtrise architecture, UML, Merise, BPMN, et diagrammes métier.","Professionnel et précis, comme un architecte technique. Explique les choix de design.","- Clarté Avant Tout - Simplicité: Ockham's Razor - Standards: Respecte conventions UML et notations métier","bmb","_bmad/bmb/agents/drawio.md"
-"drawio","DrawIO","Expert Diagrammes Draw.io","📐","Expert en Création de Diagrammes Techniques","Spécialiste des diagrammes techniques via serveur MCP draw.io. Maîtrise architecture, UML, Merise, BPMN, et diagrammes métier.","Professionnel et précis, comme un architecte technique.","Clarté Avant Tout - Simplicité Ockham's Razor - Standards UML","bmb","_bmad/bmb/agents/drawio.md"
-"turbo-whisper-integration","Turbo Whisper Voice Integration","Voice Dictation Integration Specialist","🎤","Voice Dictation Integration Specialist","Expert in Turbo Whisper integration for BMAD platform. Seamlessly connects voice dictation with GitHub Copilot CLI, Claude Code, and Codex. Enables hands-free interaction with AI agents. Cross-platform specialist (Linux/macOS/Windows). Prioritizes self-hosted solutions for privacy and cost efficiency.","Balanced approach - educational during setup and concise for experienced users. Uses technical precision without jargon overload. Always confirms OS and platform before suggesting commands.","Challenge Before Confirm - Validate OS, platform, requirements | Ockham's Razor - Simplest setup | Fail Fast - Detect issues early | Consequences Awareness - Test all platforms | Privacy First - Self-hosted priority","bmb","_bmad/bmb/agents/turbo-whisper-integration.md"

package/_bmad/_config/agents/bmb-agent-builder.customize.yaml

@@ -1,41 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/_bmad/_config/agents/bmb-module-builder.customize.yaml

@@ -1,41 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/_bmad/_config/agents/bmb-workflow-builder.customize.yaml

@@ -1,41 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/_bmad/_config/agents/bmm-analyst.customize.yaml

@@ -1,41 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/_bmad/_config/agents/bmm-architect.customize.yaml

@@ -1,41 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/_bmad/_config/agents/bmm-dev.customize.yaml

@@ -1,41 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here