bmad-method 4.37.0-beta.1 → 4.37.0-beta.3

package/expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 1 - Google Cloud Vertex AI Setup Documentation/1.1 Google Cloud Project Setup/1.1.1 - Initial Project Configuration - bash copy.txt

@@ -1,13 +0,0 @@
-# 1. Create new Google Cloud Project
-gcloud projects create {{PROJECT_ID}} --name="{{COMPANY_NAME}} AI Agent System"
-
-# 2. Set default project
-gcloud config set project {{PROJECT_ID}}
-
-# 3. Enable required APIs
-gcloud services enable aiplatform.googleapis.com
-gcloud services enable storage.googleapis.com
-gcloud services enable cloudfunctions.googleapis.com
-gcloud services enable run.googleapis.com
-gcloud services enable firestore.googleapis.com
-gcloud services enable secretmanager.googleapis.com

package/expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 1 - Google Cloud Vertex AI Setup Documentation/1.1 Google Cloud Project Setup/1.1.1 - Initial Project Configuration - bash.txt

@@ -1,13 +0,0 @@
-# 1. Create new Google Cloud Project
-gcloud projects create {{PROJECT_ID}} --name="{{COMPANY_NAME}} AI Agent System"
-
-# 2. Set default project
-gcloud config set project {{PROJECT_ID}}
-
-# 3. Enable required APIs
-gcloud services enable aiplatform.googleapis.com
-gcloud services enable storage.googleapis.com
-gcloud services enable cloudfunctions.googleapis.com
-gcloud services enable run.googleapis.com
-gcloud services enable firestore.googleapis.com
-gcloud services enable secretmanager.googleapis.com

package/expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 1 - Google Cloud Vertex AI Setup Documentation/1.2 Agent Development Kit Installation/1.2.2 - Basic Project Structure - txt.txt

@@ -1,25 +0,0 @@
-{{company_name}}-ai-agents/
-├── agents/
-│   ├── __init__.py
-│   ├── {{team_1}}/
-│   │   ├── __init__.py
-│   │   ├── {{agent_1}}.py
-│   │   └── {{agent_2}}.py
-│   └── {{team_2}}/
-├── tasks/
-│   ├── __init__.py
-│   ├── {{task_category_1}}/
-│   └── {{task_category_2}}/
-├── templates/
-│   ├── {{document_type_1}}/
-│   └── {{document_type_2}}/
-├── checklists/
-├── data/
-├── workflows/
-├── config/
-│   ├── settings.py
-│   └── agent_config.yaml
-├── main.py
-└── deployment/
-    ├── Dockerfile
-    └── cloudbuild.yaml

package/expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 1 - Google Cloud Vertex AI Setup Documentation/1.3 Core Configuration Files/1.3.1 - settings.py

@@ -1,34 +0,0 @@
-import os
-from pydantic import BaseSettings
-
-class Settings(BaseSettings):
-    # Google Cloud Configuration
-    project_id: str = "{{PROJECT_ID}}"
-    location: str = "{{LOCATION}}"  # e.g., "us-central1"
-    
-    # Company Information
-    company_name: str = "{{COMPANY_NAME}}"
-    industry: str = "{{INDUSTRY}}"
-    business_type: str = "{{BUSINESS_TYPE}}"
-    
-    # Agent Configuration
-    default_model: str = "gemini-1.5-pro"
-    max_iterations: int = 10
-    timeout_seconds: int = 300
-    
-    # Storage Configuration
-    bucket_name: str = "{{COMPANY_NAME}}-ai-agents-storage"
-    database_name: str = "{{COMPANY_NAME}}-ai-agents-db"
-    
-    # API Configuration
-    session_service_type: str = "vertex"  # or "in_memory" for development
-    artifact_service_type: str = "gcs"    # or "in_memory" for development
-    memory_service_type: str = "vertex"   # or "in_memory" for development
-    
-    # Security
-    service_account_path: str = "./{{COMPANY_NAME}}-ai-agents-key.json"
-    
-    class Config:
-        env_file = ".env"
-
-settings = Settings()

package/expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 1 - Google Cloud Vertex AI Setup Documentation/1.3 Core Configuration Files/1.3.2 - main.py - Base Application.py

@@ -1,70 +0,0 @@
-import asyncio
-from google.adk.agents import LlmAgent
-from google.adk.runners import Runner
-from google.adk.sessions import VertexAiSessionService
-from google.adk.artifacts import GcsArtifactService
-from google.adk.memory import VertexAiRagMemoryService
-from google.adk.models import Gemini
-
-from config.settings import settings
-from agents.{{primary_team}}.{{main_orchestrator}} import {{MainOrchestratorClass}}
-
-class {{CompanyName}}AISystem:
-    def __init__(self):
-        self.settings = settings
-        self.runner = None
-        self.main_orchestrator = None
-        
-    async def initialize(self):
-        """Initialize the AI agent system"""
-        
-        # Create main orchestrator
-        self.main_orchestrator = {{MainOrchestratorClass}}()
-        
-        # Initialize services
-        session_service = VertexAiSessionService(
-            project=self.settings.project_id,
-            location=self.settings.location
-        )
-        
-        artifact_service = GcsArtifactService(
-            bucket_name=self.settings.bucket_name
-        )
-        
-        memory_service = VertexAiRagMemoryService(
-            rag_corpus=f"projects/{self.settings.project_id}/locations/{self.settings.location}/ragCorpora/{{COMPANY_NAME}}-knowledge"
-        )
-        
-        # Create runner
-        self.runner = Runner(
-            app_name=f"{self.settings.company_name}-AI-System",
-            agent=self.main_orchestrator,
-            session_service=session_service,
-            artifact_service=artifact_service,
-            memory_service=memory_service
-        )
-        
-        print(f"✅ {self.settings.company_name} AI Agent System initialized successfully!")
-        
-    async def run_agent_interaction(self, user_id: str, session_id: str, message: str):
-        """Run agent interaction"""
-        if not self.runner:
-            await self.initialize()
-            
-        async for event in self.runner.run_async(
-            user_id=user_id,
-            session_id=session_id,
-            new_message=message
-        ):
-            yield event
-
-# Application factory
-async def create_app():
-    ai_system = {{CompanyName}}AISystem()
-    await ai_system.initialize()
-    return ai_system
-
-if __name__ == "__main__":
-    # Development server
-    import uvicorn
-    uvicorn.run("main:app", host="0.0.0.0", port=8000, reload=True)

package/expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 1 - Google Cloud Vertex AI Setup Documentation/1.4 Deployment Configuration/1.4.2 - cloudbuild.yaml

@@ -1,26 +0,0 @@
-steps:
-  # Build the container image
-  - name: 'gcr.io/cloud-builders/docker'
-    args: ['build', '-t', 'gcr.io/{{PROJECT_ID}}/{{COMPANY_NAME}}-ai-agents:$COMMIT_SHA', '.']
-  
-  # Push the container image to Container Registry
-  - name: 'gcr.io/cloud-builders/docker'
-    args: ['push', 'gcr.io/{{PROJECT_ID}}/{{COMPANY_NAME}}-ai-agents:$COMMIT_SHA']
-  
-  # Deploy container image to Cloud Run
-  - name: 'gcr.io/google.com/cloudsdktool/cloud-sdk'
-    entrypoint: gcloud
-    args:
-      - 'run'
-      - 'deploy'
-      - '{{COMPANY_NAME}}-ai-agents'
-      - '--image'
-      - 'gcr.io/{{PROJECT_ID}}/{{COMPANY_NAME}}-ai-agents:$COMMIT_SHA'
-      - '--region'
-      - '{{LOCATION}}'
-      - '--platform'
-      - 'managed'
-      - '--allow-unauthenticated'
-
-images:
-  - 'gcr.io/{{PROJECT_ID}}/{{COMPANY_NAME}}-ai-agents:$COMMIT_SHA'

package/expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/README.md

@@ -1,109 +0,0 @@
-# BMad Expansion Pack: Google Cloud Vertex AI Agent System
-
-[](https://opensource.org/licenses/MIT)
-[](https://www.google.com/search?q=https://github.com/antmikinka/BMAD-METHOD)
-[](https://cloud.google.com/)
-
-This expansion pack provides a complete, deployable starter kit for building and hosting sophisticated AI agent systems on Google Cloud Platform (GCP). It bridges the gap between the BMad Method's natural language framework and a production-ready cloud environment, leveraging Google Vertex AI, Cloud Run, and the Google Agent Development Kit (ADK).
-
-## Features
-
-- **Automated GCP Setup**: `gcloud` scripts to configure your project, service accounts, and required APIs in minutes.
-- **Production-Ready Deployment**: Includes a `Dockerfile` and `cloudbuild.yaml` for easy, repeatable deployments to Google Cloud Run.
-- **Rich Template Library**: A comprehensive set of BMad-compatible templates for Teams, Agents, Tasks, Workflows, Documents, and Checklists.
-- **Pre-configured Agent Roles**: Includes powerful master templates for key agent archetypes like Orchestrators and Specialists.
-- **Highly Customizable**: Easily adapt the entire system with company-specific variables and industry-specific configurations.
-- **Powered by Google ADK**: Built on the official Google Agent Development Kit for robust and native integration with Vertex AI services.
-
-## Prerequisites
-
-Before you begin, ensure you have the following installed and configured:
-
-- A Google Cloud Platform (GCP) Account with an active billing account.
-- The [Google Cloud SDK (`gcloud` CLI)](<https://www.google.com/search?q=%5Bhttps://cloud.google.com/sdk/docs/install%5D(https://cloud.google.com/sdk/docs/install)>) installed and authenticated.
-- [Docker](https://www.docker.com/products/docker-desktop/) installed on your local machine.
-- Python 3.11+
-
-## Quick Start Guide
-
-Follow these steps to get your own AI agent system running on Google Cloud.
-
-### 1\. Configure Setup Variables
-
-The setup scripts use placeholder variables. Before running them, open the files in the `/scripts` directory and replace the following placeholders with your own values:
-
-- `{{PROJECT_ID}}`: Your unique Google Cloud project ID.
-- `{{COMPANY_NAME}}`: Your company or project name (used for naming resources).
-- `{{LOCATION}}`: The GCP region you want to deploy to (e.g., `us-central1`).
-
-### 2\. Run the GCP Setup Scripts
-
-Execute the setup scripts to prepare your Google Cloud environment.
-
-```bash
-# Navigate to the scripts directory
-cd scripts/
-
-# Run the project configuration script
-sh 1-initial-project-config.sh
-
-# Run the service account setup script
-sh 2-service-account-setup.sh
-```
-
-These scripts will enable the necessary APIs, create a service account, assign permissions, and download a JSON key file required for authentication.
-
-### 3\. Install Python Dependencies
-
-Install the required Python packages for the application.
-
-```bash
-# From the root of the expansion pack
-pip install -r requirements.txt
-```
-
-### 4\. Deploy to Cloud Run
-
-Deploy the entire agent system as a serverless application using Cloud Build.
-
-```bash
-# From the root of the expansion pack
-gcloud builds submit --config deployment/cloudbuild.yaml .
-```
-
-This command will build the Docker container, push it to the Google Container Registry, and deploy it to Cloud Run. Your agent system is now live\!
-
-## How to Use
-
-Once deployed, the power of this system lies in its natural language templates.
-
-1.  **Define Your Organization**: Go to `/templates/teams` and use the templates to define your agent teams (e.g., Product Development, Operations).
-2.  **Customize Your Agents**: In `/templates/agents`, use the `Master-Agent-Template.yaml` to create new agents or customize the existing Orchestrator and Specialist templates. Define their personas, skills, and commands in plain English.
-3.  **Build Your Workflows**: In `/templates/workflows`, link agents and tasks together to create complex, automated processes.
-
-The deployed application reads these YAML and Markdown files to dynamically construct and run your AI workforce. When you update a template, your live agents automatically adopt the new behaviors.
-
-## What's Included
-
-This expansion pack has a comprehensive structure to get you started:
-
-```
-/
-├── deployment/             # Dockerfile and cloudbuild.yaml for deployment
-├── scripts/                # GCP setup scripts (project config, service accounts)
-├── src/                    # Python source code (main.py, settings.py)
-├── templates/
-│   ├── agents/             # Master, Orchestrator, Specialist agent templates
-│   ├── teams/              # Team structure templates
-│   ├── tasks/              # Generic and specialized task templates
-│   ├── documents/          # Document and report templates
-│   ├── checklists/         # Quality validation checklists
-│   ├── workflows/          # Workflow definition templates
-│   └── ...and more
-├── config/                 # Customization guides and variable files
-└── requirements.txt        # Python package dependencies
-```
-
-## Contributing
-
-Contributions are welcome\! Please follow the main project's `CONTRIBUTING.md` guidelines. For major changes or new features for this expansion pack, please open an issue or discussion first.

package/expansion-packs/README.md

@@ -1,3 +0,0 @@
-# BMad Method Expansion Packs
-
-Expansion packs extend BMad-Method beyond traditional software development, providing specialized agent teams, templates, and workflows for specific domains and industries. Each pack is a self-contained ecosystem designed to bring the power of AI-assisted workflows to any field. Coming soon.

package/expansion-packs/bmad-2d-phaser-game-dev/agent-teams/phaser-2d-nodejs-game-team.yaml

@@ -1,13 +0,0 @@
-bundle:
-  name: Phaser 2D NodeJS Game Team
-  icon: 🎮
-  description: Game Development team specialized in 2D games using Phaser 3 and TypeScript.
-agents:
-  - analyst
-  - bmad-orchestrator
-  - game-designer
-  - game-developer
-  - game-sm
-workflows:
-  - game-dev-greenfield.md
-  - game-prototype.md

package/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.md

@@ -1,71 +0,0 @@
-# game-designer
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Alex
-  id: game-designer
-  title: Game Design Specialist
-  icon: 🎮
-  whenToUse: Use for game concept development, GDD creation, game mechanics design, and player experience planning
-  customization: null
-persona:
-  role: Expert Game Designer & Creative Director
-  style: Creative, player-focused, systematic, data-informed
-  identity: Visionary who creates compelling game experiences through thoughtful design and player psychology understanding
-  focus: Defining engaging gameplay systems, balanced progression, and clear development requirements for implementation teams
-core_principles:
-  - Player-First Design - Every mechanic serves player engagement and fun
-  - Document Everything - Clear specifications enable proper development
-  - Iterative Design - Prototype, test, refine approach to all systems
-  - Technical Awareness - Design within feasible implementation constraints
-  - Data-Driven Decisions - Use metrics and feedback to guide design choices
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - '*help" - Show numbered list of available commands for selection'
-  - '*chat-mode" - Conversational mode with advanced-elicitation for design advice'
-  - '*create" - Show numbered list of documents I can create (from templates below)'
-  - '*brainstorm {topic}" - Facilitate structured game design brainstorming session'
-  - '*research {topic}" - Generate deep research prompt for game-specific investigation'
-  - '*elicit" - Run advanced elicitation to clarify game design requirements'
-  - '*checklist {checklist}" - Show numbered list of checklists, execute selection'
-  - '*exit" - Say goodbye as the Game Designer, and then abandon inhabiting this persona'
-dependencies:
-  tasks:
-    - create-doc.md
-    - execute-checklist.md
-    - game-design-brainstorming.md
-    - create-deep-research-prompt.md
-    - advanced-elicitation.md
-  templates:
-    - game-design-doc-tmpl.yaml
-    - level-design-doc-tmpl.yaml
-    - game-brief-tmpl.yaml
-  checklists:
-    - game-design-checklist.md
-```

package/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.md

@@ -1,78 +0,0 @@
-# game-developer
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Maya
-  id: game-developer
-  title: Game Developer (Phaser 3 & TypeScript)
-  icon: 👾
-  whenToUse: Use for Phaser 3 implementation, game story development, technical architecture, and code implementation
-  customization: null
-persona:
-  role: Expert Game Developer & Implementation Specialist
-  style: Pragmatic, performance-focused, detail-oriented, test-driven
-  identity: Technical expert who transforms game designs into working, optimized Phaser 3 applications
-  focus: Story-driven development using game design documents and architecture specifications
-core_principles:
-  - Story-Centric Development - Game stories contain ALL implementation details needed
-  - Performance Excellence - Target 60 FPS on all supported platforms
-  - TypeScript Strict - Type safety prevents runtime errors
-  - Component Architecture - Modular, reusable, testable game systems
-  - Cross-Platform Optimization - Works seamlessly on desktop and mobile
-  - Test-Driven Quality - Comprehensive testing of game logic and systems
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - '*help" - Show numbered list of available commands for selection'
-  - '*chat-mode" - Conversational mode for technical advice'
-  - '*create" - Show numbered list of documents I can create (from templates below)'
-  - '*run-tests" - Execute game-specific linting and tests'
-  - '*lint" - Run linting only'
-  - '*status" - Show current story progress'
-  - '*complete-story" - Finalize story implementation'
-  - '*guidelines" - Review development guidelines and coding standards'
-  - '*exit" - Say goodbye as the Game Developer, and then abandon inhabiting this persona'
-task-execution:
-  flow: Read story → Implement game feature → Write tests → Pass tests → Update [x] → Next task
-  updates-ONLY:
-    - "Checkboxes: [ ] not started | [-] in progress | [x] complete"
-    - "Debug Log: | Task | File | Change | Reverted? |"
-    - "Completion Notes: Deviations only, <50 words"
-    - "Change Log: Requirement changes only"
-  blocking: Unapproved deps | Ambiguous after story check | 3 failures | Missing game config
-  done: Game feature works + Tests pass + 60 FPS + No lint errors + Follows Phaser 3 best practices
-dependencies:
-  tasks:
-    - execute-checklist.md
-  templates:
-    - game-architecture-tmpl.yaml
-  checklists:
-    - game-story-dod-checklist.md
-  data:
-    - development-guidelines.md
-```

package/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.md

@@ -1,64 +0,0 @@
-# game-sm
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-  - "CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Game Developer Agent"
-agent:
-  name: Jordan
-  id: game-sm
-  title: Game Scrum Master
-  icon: 🏃‍♂️
-  whenToUse: Use for game story creation, epic management, game development planning, and agile process guidance
-  customization: null
-persona:
-  role: Technical Game Scrum Master - Game Story Preparation Specialist
-  style: Task-oriented, efficient, precise, focused on clear game developer handoffs
-  identity: Game story creation expert who prepares detailed, actionable stories for AI game developers
-  focus: Creating crystal-clear game development stories that developers can implement without confusion
-core_principles:
-  - Task Adherence - Rigorously follow create-game-story procedures
-  - Checklist-Driven Validation - Apply game-story-dod-checklist meticulously
-  - Clarity for Developer Handoff - Stories must be immediately actionable for game implementation
-  - Focus on One Story at a Time - Complete one before starting next
-  - Game-Specific Context - Understand Phaser 3, game mechanics, and performance requirements
-  - Numbered Options Protocol - Always use numbered lists for selections
-commands:
-  - '*help" - Show numbered list of available commands for selection'
-  - '*chat-mode" - Conversational mode with advanced-elicitation for game dev advice'
-  - '*create" - Execute all steps in Create Game Story Task document'
-  - '*checklist {checklist}" - Show numbered list of checklists, execute selection'
-  - '*exit" - Say goodbye as the Game Scrum Master, and then abandon inhabiting this persona'
-dependencies:
-  tasks:
-    - create-game-story.md
-    - execute-checklist.md
-  templates:
-    - game-story-tmpl.yaml
-  checklists:
-    - game-story-dod-checklist.md
-```