agentvibes 2.13.7 → 2.13.9

package/.bmad/bmm/workflows/workflow-status/paths/game-design.yaml

@@ -1,52 +0,0 @@
-# Game Development - Use BMGD Module
-# Game development workflows have been moved to the BMad Game Development module
-
-project_type: "game"
-level: "all"
-field_type: "any"
-description: "⚠️ Game development requires the BMGD module"
-
-error_message: |
-  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-  🎮 **GAME DEVELOPMENT DETECTED**
-
-  Game development workflows are now part of the **BMad Game Development (BMGD)** module,
-  which provides specialized workflows and agents for game creation.
-
-  **To proceed with game development:**
-
-  1. Install the BMGD module:
-     ```bash
-     bmad install bmgd
-     ```
-
-  2. The BMGD module includes:
-     - Game Designer, Game Developer, Game Architect agents
-     - Game Dev Scrum Master for sprint coordination
-     - Industry-standard game dev workflows:
-       • Phase 1 (Preproduction): brainstorm-game, game-brief
-       • Phase 2 (Design): GDD, narrative design
-       • Phase 3 (Technical): game architecture
-       • Phase 4 (Production): sprint planning, story management
-
-  3. After installation, load the Game Designer or Game Dev Scrum Master agent
-     to begin your game development workflow
-
-  **Why a separate module?**
-  - Game development follows different phases than software development
-  - Specialized agents understand game-specific terminology and patterns
-  - Workflows configured for game development needs (playtesting, balancing, etc.)
-  - Can be used standalone or alongside BMM for complete coverage
-
-  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-# Placeholder phases - this file should not be used for actual workflow tracking
-# Users should install BMGD module instead
-phases:
-  - phase: 1
-    name: "ERROR - Install BMGD Module"
-    workflows:
-      - id: "install-bmgd"
-        required: true
-        note: "Run: bmad install bmgd"

package/.bmad/bmm/workflows/workflow-status/paths/method-brownfield.yaml

@@ -1,122 +0,0 @@
-# BMad Method - Brownfield
-# Full product + architecture planning for complex brownfield additions (10-50+ stories typically)
-
-method_name: "BMad Method"
-track: "bmad-method"
-field_type: "brownfield"
-description: "Complete product and system design for complex brownfield work"
-
-phases:
-  - prerequisite: true
-    name: "Documentation"
-    conditional: "if_undocumented"
-    note: "NOT a phase - prerequisite for brownfield without docs"
-    workflows:
-      - id: "document-project"
-        required: true
-        agent: "analyst"
-        command: "document-project"
-        output: "Comprehensive project documentation"
-        purpose: "Understand existing codebase before planning"
-
-  - phase: 0
-    name: "Discovery (Optional)"
-    optional: true
-    note: "User-selected during workflow-init"
-    workflows:
-      - id: "brainstorm-project"
-        optional: true
-        agent: "analyst"
-        command: "brainstorm-project"
-        included_by: "user_choice"
-
-      - id: "research"
-        optional: true
-        agent: "analyst"
-        command: "research"
-        included_by: "user_choice"
-
-      - id: "product-brief"
-        optional: true
-        agent: "analyst"
-        command: "product-brief"
-        included_by: "user_choice"
-        note: "Optional for brownfield, less common than greenfield"
-
-  - phase: 1
-    name: "Planning"
-    required: true
-    workflows:
-      - id: "prd"
-        required: true
-        agent: "pm"
-        command: "prd"
-        output: "PRD focused on new features/changes"
-        note: "Must consider existing system constraints"
-
-      - id: "validate-prd"
-        optional: true
-        agent: "pm"
-        command: "validate-prd"
-
-      - id: "create-epics-and-stories"
-        optional: true
-        agent: "pm"
-        command: "create-epics-and-stories"
-        note: "Optional: Create epic breakdown early (basic structure only)"
-
-      - id: "create-design"
-        conditional: "if_has_ui"
-        agent: "ux-designer"
-        command: "create-design"
-
-      - id: "create-epics-and-stories-after-ux"
-        optional: true
-        agent: "pm"
-        command: "create-epics-and-stories"
-        note: "Optional: Create epic breakdown with UX context"
-
-  - phase: 2
-    name: "Solutioning"
-    required: true
-    workflows:
-      - id: "create-architecture"
-        recommended: true
-        agent: "architect"
-        command: "create-architecture"
-        output: "Integration architecture - solution design for THIS project"
-        note: "HIGHLY RECOMMENDED: Distills massive brownfield context into focused solution design. Prevents agent confusion."
-
-      - id: "create-epics-and-stories-final"
-        required: true
-        agent: "pm"
-        command: "create-epics-and-stories"
-        note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)"
-
-      - id: "test-design"
-        recommended: true
-        agent: "tea"
-        command: "test-design"
-        output: "System-level testability review"
-        note: "Testability assessment before gate check - auto-detects system-level mode"
-
-      - id: "validate-architecture"
-        optional: true
-        agent: "architect"
-        command: "validate-architecture"
-
-      - id: "implementation-readiness"
-        required: true
-        agent: "architect"
-        command: "implementation-readiness"
-        note: "Validates PRD + UX + Architecture + Epics cohesion before implementation"
-
-  - phase: 3
-    name: "Implementation"
-    required: true
-    workflows:
-      - id: "sprint-planning"
-        required: true
-        agent: "sm"
-        command: "sprint-planning"
-        note: "Creates sprint plan with stories"

package/.bmad/bmm/workflows/workflow-status/paths/method-greenfield.yaml

@@ -1,113 +0,0 @@
-# BMad Method - Greenfield
-# Full product + architecture planning for greenfield projects (10-50+ stories typically)
-
-method_name: "BMad Method"
-track: "bmad-method"
-field_type: "greenfield"
-description: "Complete product and system design methodology for greenfield projects"
-
-phases:
-  - phase: 0
-    name: "Discovery (Optional)"
-    optional: true
-    note: "User-selected during workflow-init"
-    workflows:
-      - id: "brainstorm-project"
-        optional: true
-        agent: "analyst"
-        command: "brainstorm-project"
-        included_by: "user_choice"
-
-      - id: "research"
-        optional: true
-        agent: "analyst"
-        command: "research"
-        included_by: "user_choice"
-        note: "Can have multiple research workflows"
-
-      - id: "product-brief"
-        optional: true
-        agent: "analyst"
-        command: "product-brief"
-        included_by: "user_choice"
-        note: "Recommended for greenfield Method projects"
-
-  - phase: 1
-    name: "Planning"
-    required: true
-    workflows:
-      - id: "prd"
-        required: true
-        agent: "pm"
-        command: "prd"
-        output: "Product Requirements Document with FRs and NFRs"
-
-      - id: "validate-prd"
-        optional: true
-        agent: "pm"
-        command: "validate-prd"
-        note: "Quality check for PRD completeness"
-
-      - id: "create-epics-and-stories"
-        optional: true
-        agent: "pm"
-        command: "create-epics-and-stories"
-        note: "Optional: Create epic breakdown early (basic structure only)"
-
-      - id: "create-design"
-        conditional: "if_has_ui"
-        agent: "ux-designer"
-        command: "create-design"
-        note: "Determined after PRD - user/agent decides if needed"
-
-      - id: "create-epics-and-stories-after-ux"
-        optional: true
-        agent: "pm"
-        command: "create-epics-and-stories"
-        note: "Optional: Create epic breakdown with UX context"
-
-  - phase: 2
-    name: "Solutioning"
-    required: true
-    workflows:
-      - id: "create-architecture"
-        required: true
-        agent: "architect"
-        command: "create-architecture"
-        output: "System architecture document"
-        note: "Complete system design for greenfield projects"
-
-      - id: "create-epics-and-stories-final"
-        required: true
-        agent: "pm"
-        command: "create-epics-and-stories"
-        note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)"
-
-      - id: "test-design"
-        recommended: true
-        agent: "tea"
-        command: "test-design"
-        output: "System-level testability review"
-        note: "Testability assessment before gate check - auto-detects system-level mode"
-
-      - id: "validate-architecture"
-        optional: true
-        agent: "architect"
-        command: "validate-architecture"
-        note: "Quality check for architecture completeness"
-
-      - id: "implementation-readiness"
-        required: true
-        agent: "architect"
-        command: "implementation-readiness"
-        note: "Validates PRD + UX + Architecture + Epics + Testability cohesion before implementation"
-
-  - phase: 3
-    name: "Implementation"
-    required: true
-    workflows:
-      - id: "sprint-planning"
-        required: true
-        agent: "sm"
-        command: "sprint-planning"
-        note: "Creates sprint plan - subsequent work tracked there"

package/.bmad/bmm/workflows/workflow-status/paths/quick-flow-brownfield.yaml

@@ -1,58 +0,0 @@
-# BMad Quick Flow - Brownfield
-# Fast implementation path for existing codebases (1-15 stories typically)
-
-method_name: "BMad Quick Flow"
-track: "quick-flow"
-field_type: "brownfield"
-description: "Fast tech-spec based implementation for brownfield projects"
-
-phases:
-  - prerequisite: true
-    name: "Documentation"
-    conditional: "if_undocumented"
-    note: "NOT a phase - prerequisite for brownfield without docs"
-    workflows:
-      - id: "document-project"
-        required: true
-        agent: "analyst"
-        command: "document-project"
-        output: "Comprehensive project documentation"
-        purpose: "Understand existing codebase before planning"
-
-  - phase: 0
-    name: "Discovery (Optional)"
-    optional: true
-    note: "User-selected during workflow-init"
-    workflows:
-      - id: "brainstorm-project"
-        optional: true
-        agent: "analyst"
-        command: "brainstorm-project"
-        included_by: "user_choice"
-
-      - id: "research"
-        optional: true
-        agent: "analyst"
-        command: "research"
-        included_by: "user_choice"
-
-  - phase: 1
-    name: "Planning"
-    required: true
-    workflows:
-      - id: "tech-spec"
-        required: true
-        agent: "pm"
-        command: "tech-spec"
-        output: "Technical Specification with stories (auto-detects epic if 2+ stories)"
-        note: "Integrates with existing codebase patterns from document-project"
-
-  - phase: 2
-    name: "Implementation"
-    required: true
-    workflows:
-      - id: "sprint-planning"
-        required: true
-        agent: "sm"
-        command: "sprint-planning"
-        note: "Creates sprint plan with all stories"

package/.bmad/bmm/workflows/workflow-status/paths/quick-flow-greenfield.yaml

@@ -1,47 +0,0 @@
-# BMad Quick Flow - Greenfield
-# Fast implementation path with tech-spec planning (1-15 stories typically)
-
-method_name: "BMad Quick Flow"
-track: "quick-flow"
-field_type: "greenfield"
-description: "Fast tech-spec based implementation for greenfield projects"
-
-phases:
-  - phase: 0
-    name: "Discovery (Optional)"
-    optional: true
-    note: "User-selected during workflow-init"
-    workflows:
-      - id: "brainstorm-project"
-        optional: true
-        agent: "analyst"
-        command: "brainstorm-project"
-        included_by: "user_choice"
-
-      - id: "research"
-        optional: true
-        agent: "analyst"
-        command: "research"
-        included_by: "user_choice"
-        note: "Can have multiple research workflows"
-
-  - phase: 1
-    name: "Planning"
-    required: true
-    workflows:
-      - id: "tech-spec"
-        required: true
-        agent: "pm"
-        command: "tech-spec"
-        output: "Technical Specification with stories (auto-detects epic if 2+ stories)"
-        note: "Quick Spec Flow - implementation-focused planning"
-
-  - phase: 2
-    name: "Implementation"
-    required: true
-    workflows:
-      - id: "sprint-planning"
-        required: true
-        agent: "sm"
-        command: "sprint-planning"
-        note: "Creates sprint plan with all stories - subsequent work tracked in sprint plan output, not workflow-status"

package/.bmad/bmm/workflows/workflow-status/project-levels.yaml

@@ -1,59 +0,0 @@
-# BMM Project Scale Levels - Source of Truth
-# Reference: /.bmad/bmm/README.md lines 77-85
-
-levels:
-  0:
-    name: "Level 0"
-    title: "Single Atomic Change"
-    stories: "1 story"
-    description: "Bug fix, tiny feature, one small change"
-    documentation: "Minimal - tech spec only"
-    architecture: false
-
-  1:
-    name: "Level 1"
-    title: "Small Feature"
-    stories: "1-10 stories"
-    description: "Small coherent feature, minimal documentation"
-    documentation: "Tech spec"
-    architecture: false
-
-  2:
-    name: "Level 2"
-    title: "Medium Project"
-    stories: "5-15 stories"
-    description: "Multiple features, focused PRD"
-    documentation: "PRD + optional tech spec"
-    architecture: false
-
-  3:
-    name: "Level 3"
-    title: "Complex System"
-    stories: "12-40 stories"
-    description: "Subsystems, integrations, full architecture"
-    documentation: "PRD + architecture + JIT tech specs"
-    architecture: true
-
-  4:
-    name: "Level 4"
-    title: "Enterprise Scale"
-    stories: "40+ stories"
-    description: "Multiple products, enterprise architecture"
-    documentation: "PRD + architecture + JIT tech specs"
-    architecture: true
-
-# Quick detection hints for workflow-init
-detection_hints:
-  keywords:
-    level_0: ["fix", "bug", "typo", "small change", "quick update", "patch"]
-    level_1: ["simple", "basic", "small feature", "add", "minor"]
-    level_2: ["dashboard", "several features", "admin panel", "medium"]
-    level_3: ["platform", "integration", "complex", "system", "architecture"]
-    level_4: ["enterprise", "multi-tenant", "multiple products", "ecosystem", "scale"]
-
-  story_counts:
-    level_0: [1, 1]
-    level_1: [1, 10]
-    level_2: [5, 15]
-    level_3: [12, 40]
-    level_4: [40, 999]

package/.bmad/bmm/workflows/workflow-status/workflow-status-template.yaml

@@ -1,24 +0,0 @@
-# Workflow Status Template
-
-# This tracks progress through BMM methodology Analysis, Planning, and Solutioning phases.
-# Implementation phase is tracked separately in sprint-status.yaml
-
-# STATUS DEFINITIONS:
-# ==================
-# Initial Status (before completion):
-#   - required: Must be completed to progress
-#   - optional: Can be completed but not required
-#   - recommended: Strongly suggested but not required
-#   - conditional: Required only if certain conditions met (e.g., if_has_ui)
-#
-# Completion Status:
-#   - {file-path}: File created/found (e.g., "docs/product-brief.md")
-#   - skipped: Optional/conditional workflow that was skipped
-
-generated: "{{generated}}"
-project: "{{project_name}}"
-project_type: "{{project_type}}"
-selected_track: "{{selected_track}}"
-field_type: "{{field_type}}"
-workflow_path: "{{workflow_path_file}}"
-workflow_status: "{{workflow_items}}"

package/.bmad/bmm/workflows/workflow-status/workflow.yaml

@@ -1,28 +0,0 @@
-# Workflow Status - Master Router and Status Tracker
-name: workflow-status
-description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/.bmad/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Workflow components
-installed_path: "{project-root}/.bmad/bmm/workflows/workflow-status"
-instructions: "{installed_path}/instructions.md"
-
-# Template for status file creation (used by workflow-init)
-template: "{installed_path}/workflow-status-template.yaml"
-
-# Path definitions for project types
-path_files: "{installed_path}/paths/"
-
-# Output configuration - reads existing status
-default_output_file: "{output_folder}/bmm-workflow-status.yaml"
-
-standalone: true

package/.bmad/core/agents/bmad-master.md

@@ -1,72 +0,0 @@
----
-name: "bmad master"
-description: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator"
----
-
-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=".bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" 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_folder}/core/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">Load into memory {project-root}/.bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</step>
-  <step n="5">Remember the users name is {user_name}</step>
-  <step n="6">ALWAYS communicate in {communication_language}</step>
-  <step n="7">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="8">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
-      match</step>
-  <step n="9">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="10">When executing 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="action">
-        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
-        When menu item has: action="text" → Execute the text directly as an inline instruction
-      </handler>
-
-  <handler type="workflow">
-    When menu item has: workflow="path/to/workflow.yaml"
-    1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml
-    2. Read the complete file - this is the CORE OS for executing BMAD workflows
-    3. Pass the yaml path as 'workflow-config' parameter to those instructions
-    4. Execute workflow.xml instructions precisely following all steps
-    5. Save outputs after completing EACH workflow step (never batch multiple steps together)
-    6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-  </handler>
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator</role>
-    <identity>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.</identity>
-    <communication_style>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.</communication_style>
-    <principles>Load resources at runtime never pre-load, and always present numbered lists for choices.</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*list-tasks" action="list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv">List Available Tasks</item>
-    <item cmd="*list-workflows" action="list all workflows from {project-root}/.bmad/_cfg/workflow-manifest.csv">List Workflows</item>
-    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```