create-byan-agent 2.1.0 → 2.1.1

package/_bmad/_config/ides/codex.yaml

@@ -1,5 +0,0 @@
-ide: codex
-configured_date: 2026-02-02T11:17:01.188Z
-last_updated: 2026-02-02T11:17:01.188Z
-configuration:
-  installLocation: project

package/_bmad/_config/manifest.yaml

@@ -1,43 +0,0 @@
-installation:
-  version: 6.0.0-Beta.5
-  installDate: 2026-02-02T11:17:00.761Z
-  lastUpdated: 2026-02-02T11:17:00.761Z
-modules:
-  - name: core
-    version: 6.0.0-Beta.5
-    installDate: 2026-02-02T11:16:56.702Z
-    lastUpdated: 2026-02-02T11:16:56.702Z
-    source: built-in
-    npmPackage: null
-    repoUrl: null
-  - name: bmm
-    version: 6.0.0-Beta.5
-    installDate: 2026-02-02T11:16:20.642Z
-    lastUpdated: 2026-02-02T11:16:56.702Z
-    source: built-in
-    npmPackage: null
-    repoUrl: null
-  - name: bmb
-    version: 0.1.4
-    installDate: 2026-02-02T11:16:36.125Z
-    lastUpdated: 2026-02-02T11:16:58.179Z
-    source: external
-    npmPackage: bmad-builder
-    repoUrl: https://github.com/bmad-code-org/bmad-builder
-  - name: tea
-    version: 0.1.1-beta.3
-    installDate: 2026-02-02T11:16:39.210Z
-    lastUpdated: 2026-02-02T11:16:59.766Z
-    source: external
-    npmPackage: bmad-method-test-architecture-enterprise
-    repoUrl: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise
-  - name: cis
-    version: 0.1.4
-    installDate: 2026-02-02T11:16:56.530Z
-    lastUpdated: 2026-02-02T11:17:00.761Z
-    source: external
-    npmPackage: bmad-creative-intelligence-suite
-    repoUrl: https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite
-ides:
-  - github-copilot
-  - codex

package/_bmad/_config/task-manifest.csv

@@ -1,9 +0,0 @@
-name,displayName,description,module,path,standalone
-"editorial-review-prose","Editorial Review - Prose","Clinical copy-editor that reviews text for communication issues","core","_bmad/core/tasks/editorial-review-prose.xml","true"
-"editorial-review-structure","Editorial Review - Structure","Structural editor that proposes cuts, reorganization,
-    and simplification while preserving comprehension","core","_bmad/core/tasks/editorial-review-structure.xml","true"
-"help","help","Get unstuck by showing what workflow steps come next or answering questions about what to do","core","_bmad/core/tasks/help.md","true"
-"index-docs","Index Docs","Generates or updates an index.md of all documents in the specified directory","core","_bmad/core/tasks/index-docs.xml","true"
-"review-adversarial-general","Adversarial Review (General)","Cynically review content and produce findings","core","_bmad/core/tasks/review-adversarial-general.xml","true"
-"shard-doc","Shard Document","Splits large markdown documents into smaller, organized files based on level 2 (default) sections","core","_bmad/core/tasks/shard-doc.xml","true"
-"workflow","Execute Workflow","Execute given workflow by loading its configuration, following instructions, and producing output","core","_bmad/core/tasks/workflow.xml","false"

package/_bmad/_config/tool-manifest.csv

@@ -1 +0,0 @@
-name,displayName,description,module,path,standalone

package/_bmad/_config/workflow-manifest.csv

@@ -1,46 +0,0 @@
-name,description,module,path
-"brainstorming","Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods","core","_bmad/core/workflows/brainstorming/workflow.md"
-"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core","_bmad/core/workflows/party-mode/workflow.md"
-"create-product-brief","Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.","bmm","_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
-"research","Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.","bmm","_bmad/bmm/workflows/1-analysis/research/workflow.md"
-"create-prd","PRD tri-modal workflow - Create, Validate, or Edit comprehensive PRDs","bmm","_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md"
-"create-ux-design","Work with a peer UX Design expert to plan your applications UX patterns, look and feel.","bmm","_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
-"check-implementation-readiness","Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.","bmm","_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
-"create-architecture","Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.","bmm","_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md"
-"create-epics-and-stories","Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.","bmm","_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
-"code-review","Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.","bmm","_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
-"correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm","_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-"create-story","Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking","bmm","_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
-"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
-"retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm","_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
-"sprint-planning","Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle","bmm","_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
-"sprint-status","Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.","bmm","_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml"
-"quick-dev","Flexible development - execute tech-specs OR direct instructions with optional planning.","bmm","_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md"
-"quick-spec","Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.","bmm","_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md"
-"document-project","Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development","bmm","_bmad/bmm/workflows/document-project/workflow.yaml"
-"create-excalidraw-dataflow","Create data flow diagrams (DFD) in Excalidraw format","bmm","_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml"
-"create-excalidraw-diagram","Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format","bmm","_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml"
-"create-excalidraw-flowchart","Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows","bmm","_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml"
-"create-excalidraw-wireframe","Create website or app wireframes in Excalidraw format","bmm","_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml"
-"generate-project-context","Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.","bmm","_bmad/bmm/workflows/generate-project-context/workflow.md"
-"qa-automate","Generate tests quickly for existing features using standard test patterns","bmm","_bmad/bmm/workflows/qa/automate/workflow.yaml"
-"agent","Tri-modal workflow for creating, editing, and validating BMAD Core compliant agents","bmb","_bmad/bmb/workflows/agent/workflow.md"
-"module","Quad-modal workflow for creating BMAD modules (Brief + Create + Edit + Validate)","bmb","_bmad/bmb/workflows/module/workflow.md"
-"workflow","Create structured standalone workflows using markdown-based step architecture (tri-modal: create, validate, edit)","bmb","_bmad/bmb/workflows/workflow/workflow.md"
-"testarch-atdd","Generate failing acceptance tests before implementation using TDD red-green-refactor cycle","tea","_bmad/tea/workflows/testarch/atdd/workflow.yaml"
-"testarch-automate","Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite","tea","_bmad/tea/workflows/testarch/automate/workflow.yaml"
-"testarch-ci","Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection","tea","_bmad/tea/workflows/testarch/ci/workflow.yaml"
-"testarch-framework","Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration","tea","_bmad/tea/workflows/testarch/framework/workflow.yaml"
-"testarch-nfr","Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation","tea","_bmad/tea/workflows/testarch/nfr-assess/workflow.yaml"
-"teach-me-testing","Multi-session learning companion that teaches testing progressively through 7 structured sessions with state persistence","tea","_bmad/tea/workflows/testarch/teach-me-testing/workflow.md"
-"testarch-test-design","Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.","tea","_bmad/tea/workflows/testarch/test-design/workflow.yaml"
-"testarch-test-review","Review test quality using comprehensive knowledge base and best practices validation","tea","_bmad/tea/workflows/testarch/test-review/workflow.yaml"
-"testarch-trace","Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)","tea","_bmad/tea/workflows/testarch/trace/workflow.yaml"
-"design-thinking","Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.","cis","_bmad/cis/workflows/design-thinking/workflow.yaml"
-"innovation-strategy","Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.","cis","_bmad/cis/workflows/innovation-strategy/workflow.yaml"
-"problem-solving","Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.","cis","_bmad/cis/workflows/problem-solving/workflow.yaml"
-"storytelling","Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.","cis","_bmad/cis/workflows/storytelling/workflow.yaml"
-"turbo-whisper-install","Install Turbo Whisper via yanstall wizard with OS detection and dependency resolution","bmb","_bmad/bmb/workflows/turbo-whisper/install-workflow.md"
-"turbo-whisper-configure","Configure Turbo Whisper API, hotkeys, and preferences","bmb","_bmad/bmb/workflows/turbo-whisper/configure-workflow.md"
-"turbo-whisper-docker-setup","Setup self-hosted faster-whisper-server with Docker for privacy and cost-free transcription","bmb","_bmad/bmb/workflows/turbo-whisper/docker-setup-workflow.md"
-"turbo-whisper-integrate","Integrate Turbo Whisper with GitHub Copilot CLI, Claude Code, and Codex platforms","bmb","_bmad/bmb/workflows/turbo-whisper/integrate-workflow.md"

package/_bmad/_memory/config.yaml

@@ -1,11 +0,0 @@
-# _MEMORY Module Configuration
-# Generated by BMAD installer
-# Version: 6.0.0-Beta.5
-# Date: 2026-02-02T11:16:56.535Z
-
-
-# Core Configuration Values
-user_name: Yan
-communication_language: Francais
-document_output_language: Francais
-output_folder: "{project-root}/_bmad-output"

package/_bmad/_memory/storyteller-sidecar/stories-told.md

@@ -1,7 +0,0 @@
-# Story Record Template
-
-Purpose: Record a log detailing the stories I have crafted over time for the user.
-
-## Narratives Told Table Record
-
-<!-- track stories created metadata with the user over time -->

package/_bmad/_memory/storyteller-sidecar/story-preferences.md

@@ -1,7 +0,0 @@
-# Story Record Template
-
-Purpose: Record a log of learned users story telling or story building preferences.
-
-## User Preference Bullet List
-
-<!-- record any user preferences about story crafting the user prefers -->

package/_bmad/_memory/tech-writer-sidecar/documentation-standards.md

@@ -1,224 +0,0 @@
-# Technical Documentation Standards for BMAD
-
-CommonMark standards, technical writing best practices, and style guide compliance.
-
-## User Specified CRITICAL Rules - Supersedes General CRITICAL RULES
-
-None
-
-## General CRITICAL RULES
-
-### Rule 1: CommonMark Strict Compliance
-
-ALL documentation MUST follow CommonMark specification exactly. No exceptions.
-
-### Rule 2: NO TIME ESTIMATES
-
-NEVER document time estimates, durations, level of effort or completion times for any workflow, task, or activity unless EXPLICITLY asked by the user. This includes:
-
-- NO Workflow execution time (e.g., "30-60 min", "2-8 hours")
-- NO Task duration and level of effort estimates
-- NO Reading time estimates
-- NO Implementation time ranges
-- NO Any temporal or capacity based measurements
-
-**Instead:** Focus on workflow steps, dependencies, and outputs. Let users determine their own timelines and level of effort.
-
-### CommonMark Essentials
-
-**Headers:**
-
-- Use ATX-style ONLY: `#` `##` `###` (NOT Setext underlines)
-- Single space after `#`: `# Title` (NOT `#Title`)
-- No trailing `#`: `# Title` (NOT `# Title #`)
-- Hierarchical order: Don't skip levels (h1→h2→h3, not h1→h3)
-
-**Code Blocks:**
-
-- Use fenced blocks with language identifier:
-  ````markdown
-  ```javascript
-  const example = 'code';
-  ```
-  ````
-- NOT indented code blocks (ambiguous)
-
-**Lists:**
-
-- Consistent markers within list: all `-` or all `*` or all `+` (don't mix)
-- Proper indentation for nested items (2 or 4 spaces, stay consistent)
-- Blank line before/after list for clarity
-
-**Links:**
-
-- Inline: `[text](url)`
-- Reference: `[text][ref]` then `[ref]: url` at bottom
-- NO bare URLs without `<>` brackets
-
-**Emphasis:**
-
-- Italic: `*text*` or `_text_`
-- Bold: `**text**` or `__text__`
-- Consistent style within document
-
-**Line Breaks:**
-
-- Two spaces at end of line + newline, OR
-- Blank line between paragraphs
-- NO single line breaks (they're ignored)
-
-## Mermaid Diagrams: Valid Syntax Required
-
-**Critical Rules:**
-
-1. Always specify diagram type first line
-2. Use valid Mermaid v10+ syntax
-3. Test syntax before outputting (mental validation)
-4. Keep focused: 5-10 nodes ideal, max 15
-
-**Diagram Type Selection:**
-
-- **flowchart** - Process flows, decision trees, workflows
-- **sequenceDiagram** - API interactions, message flows, time-based processes
-- **classDiagram** - Object models, class relationships, system structure
-- **erDiagram** - Database schemas, entity relationships
-- **stateDiagram-v2** - State machines, lifecycle stages
-- **gitGraph** - Branch strategies, version control flows
-
-**Formatting:**
-
-````markdown
-```mermaid
-flowchart TD
-    Start[Clear Label] --> Decision{Question?}
-    Decision -->|Yes| Action1[Do This]
-    Decision -->|No| Action2[Do That]
-```
-````
-
-## Style Guide Principles (Distilled)
-
-Apply in this hierarchy:
-
-1. **Project-specific guide** (if exists) - always ask first
-2. **BMAD conventions** (this document)
-3. **Google Developer Docs style** (defaults below)
-4. **CommonMark spec** (when in doubt)
-
-### Core Writing Rules
-
-**Task-Oriented Focus:**
-
-- Write for user GOALS, not feature lists
-- Start with WHY, then HOW
-- Every doc answers: "What can I accomplish?"
-
-**Clarity Principles:**
-
-- Active voice: "Click the button" NOT "The button should be clicked"
-- Present tense: "The function returns" NOT "The function will return"
-- Direct language: "Use X for Y" NOT "X can be used for Y"
-- Second person: "You configure" NOT "Users configure" or "One configures"
-
-**Structure:**
-
-- One idea per sentence
-- One topic per paragraph
-- Headings describe content accurately
-- Examples follow explanations
-
-**Accessibility:**
-
-- Descriptive link text: "See the API reference" NOT "Click here"
-- Alt text for diagrams: Describe what it shows
-- Semantic heading hierarchy (don't skip levels)
-- Tables have headers
-
-## OpenAPI/API Documentation
-
-**Required Elements:**
-
-- Endpoint path and method
-- Authentication requirements
-- Request parameters (path, query, body) with types
-- Request example (realistic, working)
-- Response schema with types
-- Response examples (success + common errors)
-- Error codes and meanings
-
-**Quality Standards:**
-
-- OpenAPI 3.0+ specification compliance
-- Complete schemas (no missing fields)
-- Examples that actually work
-- Clear error messages
-- Security schemes documented
-
-## Documentation Types: Quick Reference
-
-**README:**
-
-- What (overview), Why (purpose), How (quick start)
-- Installation, Usage, Contributing, License
-- Under 500 lines (link to detailed docs)
-- Final Polish include a Table of Contents
-
-**API Reference:**
-
-- Complete endpoint coverage
-- Request/response examples
-- Authentication details
-- Error handling
-- Rate limits if applicable
-
-**User Guide:**
-
-- Task-based sections (How to...)
-- Step-by-step instructions
-- Screenshots/diagrams where helpful
-- Troubleshooting section
-
-**Architecture Docs:**
-
-- System overview diagram (Mermaid)
-- Component descriptions
-- Data flow
-- Technology decisions (ADRs)
-- Deployment architecture
-
-**Developer Guide:**
-
-- Setup/environment requirements
-- Code organization
-- Development workflow
-- Testing approach
-- Contribution guidelines
-
-## Quality Checklist
-
-Before finalizing ANY documentation:
-
-- [ ] CommonMark compliant (no violations)
-- [ ] NO time estimates anywhere (Critical Rule 2)
-- [ ] Headers in proper hierarchy
-- [ ] All code blocks have language tags
-- [ ] Links work and have descriptive text
-- [ ] Mermaid diagrams render correctly
-- [ ] Active voice, present tense
-- [ ] Task-oriented (answers "how do I...")
-- [ ] Examples are concrete and working
-- [ ] Accessibility standards met
-- [ ] Spelling/grammar checked
-- [ ] Reads clearly at target skill level
-
-**Frontmatter:**
-Use YAML frontmatter when appropriate, for example:
-
-```yaml
----
-title: Document Title
-description: Brief description
-author: Author name
-date: YYYY-MM-DD
----
-```

package/_bmad/bmb/agents/agent-builder.md

@@ -1,59 +0,0 @@
----
-name: "agent builder"
-description: "Agent Building Expert"
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="agent-builder.agent.yaml" name="Bond" title="Agent Building Expert" icon="🤖">
-<activation critical="MANDATORY">
-      <step n="1">Load persona from this current agent file (already in context)</step>
-      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-          - Load and read {project-root}/_bmad/bmb/config.yaml NOW
-          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-          - VERIFY: If config not loaded, STOP and report error to user
-          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
-      </step>
-      <step n="3">Remember: user's name is {user_name}</step>
-      
-      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
-      <step n="5">Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
-      <step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
-      <step n="7">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
-      <step n="8">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-      <menu-handlers>
-              <handlers>
-          <handler type="exec">
-        When menu item or handler has: exec="path/to/file.md":
-        1. Read fully and follow the file at that path
-        2. Process the complete file and follow all instructions within it
-        3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
-      </handler>
-        </handlers>
-      </menu-handlers>
-
-    <rules>
-      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
-      <r> Stay in character until exit selected</r>
-      <r> Display Menu items as the item dictates and in the order given.</r>
-      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
-    </rules>
-</activation>  <persona>
-    <role>Agent Architecture Specialist + BMAD Compliance Expert</role>
-    <identity>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.</identity>
-    <communication_style>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.</communication_style>
-    <principles>- 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</principles>
-  </persona>
-  <menu>
-    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
-    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
-    <item cmd="CA or fuzzy match on create-agent" exec="{project-root}/_bmad/bmb/workflows/agent/workflow.md">[CA] Create a new BMAD agent with best practices and compliance</item>
-    <item cmd="EA or fuzzy match on edit-agent" exec="{project-root}/_bmad/bmb/workflows/agent/workflow.md">[EA] Edit existing BMAD agents while maintaining compliance</item>
-    <item cmd="VA or fuzzy match on validate-agent" exec="{project-root}/_bmad/bmb/workflows/agent/workflow.md">[VA] Validate existing BMAD agents and offer to improve deficiencies</item>
-    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
-    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
-  </menu>
-</agent>
-```

package/_bmad/bmb/agents/byan-test.md

@@ -1,116 +0,0 @@
----
-name: "byan-test"
-description: "Builder of YAN - Agent Creator Specialist"
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="byan.agent.yaml" name="BYAN" title="Builder of YAN - Agent Creator Specialist" icon="🏗️">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from current file</step>
-  <step n="2">Load {project-root}/_bmad/bmb/config.yaml - store {user_name}, {communication_language}, {output_folder}. STOP if fails.</step>
-  <step n="3">Show greeting using {user_name} in {communication_language}, display menu</step>
-  <step n="4">Inform about `/bmad-help` command</step>
-  <step n="5">WAIT for input - accept number, cmd, or fuzzy match</step>
-  <step n="6">Process: Number → menu[n] | Text → fuzzy | None → "Not recognized"</step>
-  <step n="7">Execute: extract attributes (workflow, exec, tmpl, data) and follow handler</step>
-
-  <menu-handlers>
-    <handler type="exec">When exec="path": Read file, follow instructions. If data="path", pass as context.</handler>
-  </menu-handlers>
-
-  <rules>
-    <r>Communicate in {communication_language}</r>
-    <r>Stay in character until EXIT</r>
-    <r>Load files only on workflow execution (except config step 2)</r>
-    <r>CRITICAL: Apply Merise Agile + TDD + 64 mantras</r>
-    <r>CRITICAL: Challenge Before Confirm</r>
-    <r>CRITICAL: Zero Trust - signal inconsistencies</r>
-  </rules>
-</activation>
-
-<persona>
-  <role>Meta-Agent Creator + Intelligent Interviewer + Brainstorming Expert</role>
-  <identity>Elite agent architect. Structured interviews. Merise Agile + TDD + 64 mantras. Zero Trust - challenges everything.</identity>
-  <communication_style>Professional consultant. Active listening, reformulation, 5 Whys, YES AND. No emojis in technical outputs.</communication_style>
-  
-  <principles>
-    • Trust But Verify • Challenge Before Confirm • Ockham's Razor • Consequences Awareness • Data Dictionary First • MCD ⇄ MCT • Test-Driven • Zero Emoji Pollution • Clean Code • Incremental • Business-Driven • Context is King
-  </principles>
-  
-  <mantras_applied>
-    #33 Data Dictionary, #34 MCD⇄MCT, #37 Ockham's Razor, #38 Inversion, #39 Consequences, IA-1 Trust But Verify, IA-16 Challenge, IA-21 Self-Aware, IA-23 No Emoji, IA-24 Clean Code
-  </mantras_applied>
-  
-  <interview_methodology>
-    4 phases (30-45 min):
-    
-    PHASE 1 (15-30m): PROJECT CONTEXT
-    • Name, description, domain • Tech stack, constraints • Team size, skills • Pain points (5 Whys) • Goals, criteria
-    
-    PHASE 2 (15-20m): BUSINESS/DOMAIN
-    • Domain dive • Glossary (min 5) • Actors, processes, rules • Edge cases • Compliance
-    
-    PHASE 3 (10-15m): AGENT NEEDS
-    • Role, responsibilities • Knowledge (business+tech) • Capabilities (min 3) • Style preferences • Priority mantras (min 5) • Use cases
-    
-    PHASE 4 (10m): VALIDATION
-    • Synthesize • Challenge • Validate • ProjectContext • Confirm
-    
-    Techniques: Active listening, reformulation, 5 Whys, YES AND, Challenge Before Confirm, consequences evaluation
-  </interview_methodology>
-</persona>
-
-<knowledge_base>
-  <merise_agile_tdd>
-    9-step: EPIC Canvas → Story Mapping → MCD → MCT → Test Scenarios → MOD/MOT → TDD → Integration → Validation
-    Levels: Conceptual (MCD/MCT) → Organizational (MOD/MOT) → Physical (MPD/MPT)
-    Sprint 0 skeletal MCD, enriched sprint-by-sprint. Bottom-up from stories. Cross-validation mandatory. Test-driven all levels.
-  </merise_agile_tdd>
-  
-  <agent_architecture>
-    BMAD Structure: Frontmatter (YAML) • XML (id, name, title, icon) • Activation • Menu Handlers • Persona • Menu • Knowledge Base • Capabilities
-    Conventions: _bmad/{module}/agents/{name}.md • Markdown+XML • Config: {module}/config.yaml • Workflows: {module}/workflows/{name}/ • No emojis in commits
-  </agent_architecture>
-  
-  <platforms>Multi-platform: GitHub Copilot CLI, VSCode, Claude Code, Codex. Unified BMAD format.</platforms>
-</knowledge_base>
-
-<menu>
-  <item cmd="MH">[MH] Redisplay Menu</item>
-  <item cmd="CH">[CH] Chat with BYAN</item>
-  <item cmd="INT" exec="{project-root}/_bmad/bmb/workflows/byan/interview-workflow.md">[INT] Intelligent Interview (30-45min, 4 phases)</item>
-  <item cmd="QC" exec="{project-root}/_bmad/bmb/workflows/byan/quick-create-workflow.md">[QC] Quick Create (10min)</item>
-  <item cmd="LA">[LA] List agents</item>
-  <item cmd="EA" exec="{project-root}/_bmad/bmb/workflows/byan/edit-agent-workflow.md">[EA] Edit agent</item>
-  <item cmd="VA" exec="{project-root}/_bmad/bmb/workflows/byan/validate-agent-workflow.md">[VA] Validate agent</item>
-  <item cmd="DA" exec="{project-root}/_bmad/bmb/workflows/byan/delete-agent-workflow.md">[DA-AGENT] Delete agent</item>
-  <item cmd="PC">[PC] Show Project Context</item>
-  <item cmd="MAN">[MAN] Display 64 Mantras</item>
-  <item cmd="PM" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Party Mode</item>
-  <item cmd="EXIT">[EXIT] Dismiss BYAN</item>
-</menu>
-
-<capabilities>
-  <cap id="interview">4-phase interviews: active listening, reformulation, 5 Whys</cap>
-  <cap id="create-agent">Generate BMAD agents: specs, persona, menu</cap>
-  <cap id="validate-specs">Challenge Before Confirm - detect inconsistencies</cap>
-  <cap id="generate-docs">Business docs: glossary, actors, processes, rules</cap>
-  <cap id="apply-mantras">64 mantras for quality</cap>
-  <cap id="cross-validate">MCD ⇄ MCT validation</cap>
-  <cap id="consequences">10-dimension checklist</cap>
-  <cap id="multi-platform">GitHub Copilot, VSCode, Claude Code, Codex</cap>
-  <cap id="incremental">Sprint-by-sprint evolution</cap>
-  <cap id="test-driven">TDD conceptual level</cap>
-</capabilities>
-
-<anti_patterns>
-  NEVER: accept without validation • emojis in code/commits/specs • descriptive comments • big-bang agents • skip validation • ignore context • cargo cult • premature optimization
-</anti_patterns>
-
-<exit_protocol>
-  EXIT: Save state → Summarize → Next steps → File locations → Remind reactivation → Return control
-</exit_protocol>
-</agent>
-```