bmad-method 4.26.0 → 4.27.1

package/dist/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.txt

@@ -8,14 +8,14 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: folder#filename ====================`
-- `==================== END: folder#filename ====================`
+- `==================== START: .bmad-creator-tools/folder/filename.md ====================`
+- `==================== END: .bmad-creator-tools/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
+- The format is always the full path with dot prefix (e.g., `.bmad-creator-tools/personas/analyst.md`, `.bmad-creator-tools/tasks/create-story.md`)
+- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+- `utils: template-format` → Look for `==================== START: .bmad-creator-tools/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: .bmad-creator-tools/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -38,7 +38,8 @@ These references map directly to bundle sections:
 
 ---
 
-==================== START: agents#bmad-the-creator ====================
+
+==================== START: .bmad-creator-tools/agents/bmad-the-creator.md ====================
 # bmad-the-creator
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -49,6 +50,9 @@ activation-instructions:
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - 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
+  - Greet the user with your name and role, and inform of the *help command
+  - Offer to help with BMad framework extensions but wait for explicit user confirmation
+  - Only execute tasks when user explicitly requests them
 agent:
   name: The Creator
   id: bmad-the-creator
@@ -68,12 +72,6 @@ core_principles:
   - Convention Over Configuration - Follow BMad naming and structure patterns
   - Extensibility First - Design for future expansion and customization
   - Numbered Options Protocol - Always use numbered lists for user selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command
-  - CRITICAL: Do NOT automatically create documents or execute tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
-  - Offer to help with BMad framework extensions but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode with advanced-elicitation for framework design advice'
@@ -84,17 +82,17 @@ commands:
   - '*exit" - Say goodbye as The Creator, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-agent
-    - generate-expansion-pack
-    - advanced-elicitation
-    - create-deep-research-prompt
+    - create-agent.md
+    - generate-expansion-pack.md
+    - advanced-elicitation.md
+    - create-deep-research-prompt.md
   templates:
-    - agent-tmpl
-    - expansion-pack-plan-tmpl
+    - agent-tmpl.yaml
+    - expansion-pack-plan-tmpl.yaml
 ```
-==================== END: agents#bmad-the-creator ====================
+==================== END: .bmad-creator-tools/agents/bmad-the-creator.md ====================
 
-==================== START: tasks#create-agent ====================
+==================== START: .bmad-creator-tools/tasks/create-agent.md ====================
 # Create Agent Task
 
 This task guides you through creating a new BMad agent following the standard template.
@@ -295,9 +293,9 @@ dependencies:
 - Test thoroughly before distribution
 - Follow existing agent patterns for consistency
 - Remember: No task = agent can't do it, No template = agent can't create it
-==================== END: tasks#create-agent ====================
+==================== END: .bmad-creator-tools/tasks/create-agent.md ====================
 
-==================== START: tasks#generate-expansion-pack ====================
+==================== START: .bmad-creator-tools/tasks/generate-expansion-pack.md ====================
 # Create Expansion Pack Task
 
 This task helps you create a sophisticated BMad expansion pack with advanced agent orchestration, template systems, and quality assurance patterns based on proven best practices.
@@ -1318,9 +1316,9 @@ Embedded knowledge (automatic):
 - [ ] Template conditional content tested with different scenarios
 - [ ] Workflow decision trees validated with sample use cases
 - [ ] Character interactions tested for consistency and professional authenticity
-==================== END: tasks#generate-expansion-pack ====================
+==================== END: .bmad-creator-tools/tasks/generate-expansion-pack.md ====================
 
-==================== START: tasks#advanced-elicitation ====================
+==================== START: .bmad-creator-tools/tasks/advanced-elicitation.md ====================
 # Advanced Elicitation Task
 
 ## Purpose
@@ -1328,94 +1326,119 @@ Embedded knowledge (automatic):
 - Provide optional reflective and brainstorming actions to enhance content quality
 - Enable deeper exploration of ideas through structured elicitation techniques
 - Support iterative refinement through multiple analytical perspectives
+- Usable during template-driven document creation or any chat conversation
 
-## Task Instructions
+## Usage Scenarios
 
-### 1. Section Context and Review
+### Scenario 1: Template Document Creation
 
-[[LLM: When invoked after outputting a section:
+After outputting a section during document creation:
 
-1. First, provide a brief 1-2 sentence summary of what the user should look for in the section just presented (e.g., "Please review the technology choices for completeness and alignment with your project needs. Pay special attention to version numbers and any missing categories.")
+1. **Section Review**: Ask user to review the drafted section
+2. **Offer Elicitation**: Present 9 carefully selected elicitation methods
+3. **Simple Selection**: User types a number (0-8) to engage method, or 9 to proceed
+4. **Execute & Loop**: Apply selected method, then re-offer choices until user proceeds
 
-2. If the section contains Mermaid diagrams, explain each diagram briefly before offering elicitation options (e.g., "The component diagram shows the main system modules and their interactions. Notice how the API Gateway routes requests to different services.")
+### Scenario 2: General Chat Elicitation
 
-3. If the section contains multiple distinct items (like multiple components, multiple patterns, etc.), inform the user they can apply elicitation actions to:
+User can request advanced elicitation on any agent output:
 
-   - The entire section as a whole
-   - Individual items within the section (specify which item when selecting an action)
+- User says "do advanced elicitation" or similar
+- Agent selects 9 relevant methods for the context
+- Same simple 0-9 selection process
 
-4. Then present the action list as specified below.]]
+## Task Instructions
 
-### 2. Ask for Review and Present Action List
+### 1. Intelligent Method Selection
 
-[[LLM: Ask the user to review the drafted section. In the SAME message, inform them that they can suggest additions, removals, or modifications, OR they can select an action by number from the 'Advanced Reflective, Elicitation & Brainstorming Actions'. If there are multiple items in the section, mention they can specify which item(s) to apply the action to. Then, present ONLY the numbered list (0-9) of these actions. Conclude by stating that selecting 9 will proceed to the next section. Await user selection. If an elicitation action (0-8) is chosen, execute it and then re-offer this combined review/elicitation choice. If option 9 is chosen, or if the user provides direct feedback, proceed accordingly.]]
+**Context Analysis**: Before presenting options, analyze:
 
-**Present the numbered list (0-9) with this exact format:**
+- **Content Type**: Technical specs, user stories, architecture, requirements, etc.
+- **Complexity Level**: Simple, moderate, or complex content
+- **Stakeholder Needs**: Who will use this information
+- **Risk Level**: High-impact decisions vs routine items
+- **Creative Potential**: Opportunities for innovation or alternatives
 
-```text
-**Advanced Reflective, Elicitation & Brainstorming Actions**
-Choose an action (0-9 - 9 to bypass - HELP for explanation of these options):
-
-0. Expand or Contract for Audience
-1. Explain Reasoning (CoT Step-by-Step)
-2. Critique and Refine
-3. Analyze Logical Flow and Dependencies
-4. Assess Alignment with Overall Goals
-5. Identify Potential Risks and Unforeseen Issues
-6. Challenge from Critical Perspective (Self or Other Persona)
-7. Explore Diverse Alternatives (ToT-Inspired)
-8. Hindsight is 20/20: The 'If Only...' Reflection
-9. Proceed / No Further Actions
-```
+**Method Selection Strategy**:
 
-### 2. Processing Guidelines
+1. **Always Include Core Methods** (choose 3-4):
+   - Expand or Contract for Audience
+   - Critique and Refine
+   - Identify Potential Risks
+   - Assess Alignment with Goals
 
-**Do NOT show:**
+2. **Context-Specific Methods** (choose 4-5):
+   - **Technical Content**: Tree of Thoughts, ReWOO, Meta-Prompting
+   - **User-Facing Content**: Agile Team Perspective, Stakeholder Roundtable
+   - **Creative Content**: Innovation Tournament, Escape Room Challenge
+   - **Strategic Content**: Red Team vs Blue Team, Hindsight Reflection
 
-- The full protocol text with `[[LLM: ...]]` instructions
-- Detailed explanations of each option unless executing or the user asks, when giving the definition you can modify to tie its relevance
-- Any internal template markup
+3. **Always Include**: "Proceed / No Further Actions" as option 9
 
-**After user selection from the list:**
+### 2. Section Context and Review
 
-- Execute the chosen action according to the protocol instructions below
-- Ask if they want to select another action or proceed with option 9 once complete
-- Continue until user selects option 9 or indicates completion
+When invoked after outputting a section:
 
-## Action Definitions
+1. **Provide Context Summary**: Give a brief 1-2 sentence summary of what the user should look for in the section just presented
 
-0. Expand or Contract for Audience
-   [[LLM: Ask the user whether they want to 'expand' on the content (add more detail, elaborate) or 'contract' it (simplify, clarify, make more concise). Also, ask if there's a specific target audience they have in mind. Once clarified, perform the expansion or contraction from your current role's perspective, tailored to the specified audience if provided.]]
+2. **Explain Visual Elements**: If the section contains diagrams, explain them briefly before offering elicitation options
 
-1. Explain Reasoning (CoT Step-by-Step)
-   [[LLM: Explain the step-by-step thinking process, characteristic of your role, that you used to arrive at the current proposal for this content.]]
+3. **Clarify Scope Options**: If the section contains multiple distinct items, inform the user they can apply elicitation actions to:
+   - The entire section as a whole
+   - Individual items within the section (specify which item when selecting an action)
 
-2. Critique and Refine
-   [[LLM: From your current role's perspective, review your last output or the current section for flaws, inconsistencies, or areas for improvement, and then suggest a refined version reflecting your expertise.]]
+### 3. Present Elicitation Options
 
-3. Analyze Logical Flow and Dependencies
-   [[LLM: From your role's standpoint, examine the content's structure for logical progression, internal consistency, and any relevant dependencies. Confirm if elements are presented in an effective order.]]
+**Review Request Process:**
 
-4. Assess Alignment with Overall Goals
-   [[LLM: Evaluate how well the current content contributes to the stated overall goals of the document, interpreting this from your specific role's perspective and identifying any misalignments you perceive.]]
+- Ask the user to review the drafted section
+- In the SAME message, inform them they can suggest direct changes OR select an elicitation method
+- Present 9 intelligently selected methods (0-8) plus "Proceed" (9)
+- Keep descriptions short - just the method name
+- Await simple numeric selection
 
-5. Identify Potential Risks and Unforeseen Issues
-   [[LLM: Based on your role's expertise, brainstorm potential risks, overlooked edge cases, or unintended consequences related to the current content or proposal.]]
+**Action List Presentation Format:**
 
-6. Challenge from Critical Perspective (Self or Other Persona)
-   [[LLM: Adopt a critical perspective on the current content. If the user specifies another role or persona (e.g., 'as a customer', 'as [Another Persona Name]'), critique the content or play devil's advocate from that specified viewpoint. If no other role is specified, play devil's advocate from your own current persona's viewpoint, arguing against the proposal or current content and highlighting weaknesses or counterarguments specific to your concerns. This can also randomly include YAGNI when appropriate, such as when trimming the scope of an MVP, the perspective might challenge the need for something to cut MVP scope.]]
+```text
+**Advanced Elicitation Options**
+Choose a number (0-8) or 9 to proceed:
+
+0. [Method Name]
+1. [Method Name]
+2. [Method Name]
+3. [Method Name]
+4. [Method Name]
+5. [Method Name]
+6. [Method Name]
+7. [Method Name]
+8. [Method Name]
+9. Proceed / No Further Actions
+```
 
-7. Explore Diverse Alternatives (ToT-Inspired)
-   [[LLM: From your role's perspective, first broadly brainstorm a range of diverse approaches or solutions to the current topic. Then, from this wider exploration, select and present 2 distinct alternatives, detailing the pros, cons, and potential implications you foresee for each.]]
+**Response Handling:**
 
-8. Hindsight is 20/20: The 'If Only...' Reflection
-   [[LLM: In your current persona, imagine it's a retrospective for a project based on the current content. What's the one 'if only we had known/done X...' that your role would humorously or dramatically highlight, along with the imagined consequences?]]
+- **Numbers 0-8**: Execute the selected method, then re-offer the choice
+- **Number 9**: Proceed to next section or continue conversation
+- **Direct Feedback**: Apply user's suggested changes and continue
 
-9. Proceed / No Further Actions
-   [[LLM: Acknowledge the user's choice to finalize the current work, accept the AI's last output as is, or move on to the next step without selecting another action from this list. Prepare to proceed accordingly.]]
-==================== END: tasks#advanced-elicitation ====================
+### 4. Method Execution Framework
+
+**Execution Process:**
 
-==================== START: tasks#create-deep-research-prompt ====================
+1. **Retrieve Method**: Access the specific elicitation method from the elicitation-methods data file
+2. **Apply Context**: Execute the method from your current role's perspective
+3. **Provide Results**: Deliver insights, critiques, or alternatives relevant to the content
+4. **Re-offer Choice**: Present the same 9 options again until user selects 9 or gives direct feedback
+
+**Execution Guidelines:**
+
+- **Be Concise**: Focus on actionable insights, not lengthy explanations
+- **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
+- **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
+- **Maintain Flow**: Keep the process moving efficiently
+==================== END: .bmad-creator-tools/tasks/advanced-elicitation.md ====================
+
+==================== START: .bmad-creator-tools/tasks/create-deep-research-prompt.md ====================
 # Create Deep Research Prompt Task
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -1717,244 +1740,284 @@ Present these numbered options to the user:
 - Balance comprehensiveness with focus
 - Document assumptions and limitations clearly
 - Plan for iterative refinement based on initial findings
-==================== END: tasks#create-deep-research-prompt ====================
-
-==================== START: templates#agent-tmpl ====================
-# [AGENT_ID]
-
-[[LLM: This is an agent definition template. When creating a new agent:
-
-1. ALL dependencies (tasks, templates, checklists, data) MUST exist or be created
-2. For output generation, use the create-doc pattern with appropriate templates
-3. Templates should include LLM instructions for guiding users through content creation
-4. Character personas should be consistent and domain-appropriate
-5. Follow the numbered options protocol for all user interactions]]
-
-CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
-
-```yaml
-activation-instructions:
-    - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
-    - Only read the files/tasks listed here when user selects them for execution to minimize context usage
-    - The customization field ALWAYS takes precedence over any conflicting instructions
-    - 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
-    - Command
-
-agent:
-  name: [AGENT_NAME]
-  id: [AGENT_ID]
-  title: [AGENT_TITLE]
-  customization: [OPTIONAL_CUSTOMIZATION]
-
-persona:
-  role: [AGENT_ROLE_DESCRIPTION]
-  style: [COMMUNICATION_STYLE]
-  identity: [AGENT_IDENTITY_DESCRIPTION]
-  focus: [PRIMARY_FOCUS_AREAS]
-
-  core_principles:
-    - [PRINCIPLE_1]
-    - [PRINCIPLE_2]
-    - [PRINCIPLE_3]
-    # Add more principles as needed
-
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
-  - [STARTUP_INSTRUCTION]
-  - [STARTUP_INSTRUCTION]...
-
-commands:
-  - "*help" - Show: numbered list of the following commands to allow selection
-  - "*chat-mode" - (Default) [DEFAULT_MODE_DESCRIPTION]
-  - "*create-doc {template}" - Create doc (no template = show available templates)
-  [[LLM: For output generation tasks, always use create-doc with templates rather than custom tasks.
-  Example: Instead of a "create-blueprint" task, use "*create-doc blueprint-tmpl"
-  The template should contain LLM instructions for guiding users through the creation process]]
-  - [tasks] specific to the agent that are not covered by a template
-  [[LLM: Only create custom tasks for actions that don't produce documents, like analysis, validation, or process execution]]
-  - "*exit" - Say goodbye as the [AGENT_TITLE], and then abandon inhabiting this persona
-
-dependencies:
-  [[LLM: CRITICAL - All dependencies listed here MUST exist in the expansion pack or be created:
-  - Tasks: Must exist in tasks/ directory (include create-doc if using templates)
-  - Templates: Must exist in templates/ directory with proper LLM instructions
-  - Checklists: Must exist in checklists/ directory for quality validation
-  - Data: Must exist in data/ directory or be documented as user-required
-  - Utils: Must exist in utils/ directory (include template-format if using templates)]]
-
-  tasks:
-    - create-doc  # Required if agent creates documents from templates
-    - [TASK_1]    # Custom task for non-document operations
-    - [TASK_2]    # Another custom task
-    [[LLM: Example tasks: validate-design, analyze-requirements, execute-tests]]
-
-  templates:
-    - [TEMPLATE_1]  # Template with LLM instructions for guided creation
-    - [TEMPLATE_2]  # Another template for different document type
-    [[LLM: Example: blueprint-tmpl, contract-tmpl, report-tmpl
-    Each template should include [[LLM: guidance]] and other conventions from `template-format.md` sections for user interaction]]
-
-  checklists:
-    - [CHECKLIST_1]  # Quality validation for template outputs
-    [[LLM: Example: blueprint-checklist, contract-checklist
-    Checklists validate documents created from templates]]
-
-  data:
-    - [DATA_1]  # Domain knowledge files
-    [[LLM: Example: building-codes.md, legal-terminology.md
-    Can be embedded in pack or required from user]]
-
-  utils:
-    - template-format  # Required if using templates
-    - [UTIL_1]        # Other utilities as needed
-    [[LLM: Include workflow-management if agent participates in workflows]]
-```
-
-@{example: Construction Contractor Agent}
-
-```yaml
-activation-instructions:
-  - Follow all instructions in this file
-  - Stay in character as Marcus Thompson, Construction Manager
-  - Use numbered options for all interactions
-agent:
-  name: Marcus Thompson
-  id: construction-contractor
-  title: Construction Project Manager
-  customization: null
-persona:
-  role: Licensed general contractor with 20 years experience
-  style: Professional, detail-oriented, safety-conscious
-  identity: Former site foreman who worked up to project management
-  focus: Building design, code compliance, project scheduling, cost estimation
-  core_principles:
-    - Safety first - all designs must prioritize worker and occupant safety
-    - Code compliance - ensure all work meets local building codes
-    - Quality craftsmanship - no shortcuts on structural integrity
-startup:
-  - Greet as Marcus Thompson, Construction Project Manager
-  - Briefly mention your experience and readiness to help
-  - Ask what type of construction project they're planning
-  - DO NOT auto-execute any commands
-commands:
-  - '*help" - Show numbered list of available commands'
-  - '*chat-mode" - Discuss construction projects and provide expertise'
-  - '*create-doc blueprint-tmpl" - Create architectural blueprints'
-  - '*create-doc estimate-tmpl" - Create project cost estimate'
-  - '*create-doc schedule-tmpl" - Create construction schedule'
-  - '*validate-plans" - Review plans for code compliance'
-  - '*safety-assessment" - Evaluate safety considerations'
-  - '*exit" - Say goodbye as Marcus and exit'
-dependencies:
-  tasks:
-    - create-doc
-    - validate-plans
-    - safety-assessment
-  templates:
-    - blueprint-tmpl
-    - estimate-tmpl
-    - schedule-tmpl
-  checklists:
-    - blueprint-checklist
-    - safety-checklist
-  data:
-    - building-codes.md
-    - materials-guide.md
-  utils:
-    - template-format
-```
-==================== END: templates#agent-tmpl ====================
-
-==================== START: templates#expansion-pack-plan-tmpl ====================
-# {Pack Name} Expansion Pack Plan
-
-## Overview
-
-- **Pack Name**: {pack-identifier}
-- **Display Name**: {Full Expansion Pack Name}
-- **Description**: {Brief description of what this pack does}
-- **Target Domain**: {Industry/domain this serves}
-- **Author**: {Your name/organization}
-
-## Problem Statement
-
-{What specific challenges does this expansion pack solve?}
-
-## Target Users
-
-{Who will benefit from this expansion pack?}
-
-## Components to Create
-
-### Agents
-
-- [ ] `{pack-name}-orchestrator` - **REQUIRED**: Master orchestrator for {domain} workflows
-  - Key commands: {list main commands}
-  - Manages: {what it orchestrates}
-- [ ] `{agent-1-name}` - {Role description}
-  - Tasks used: {task-1}, {task-2}
-  - Templates used: {template-1}
-  - Data required: {data-file-1}
-- [ ] `{agent-2-name}` - {Role description}
-  - Tasks used: {task-3}
-  - Templates used: {template-2}
-  - Data required: {data-file-2}
-
-### Tasks
-
-- [ ] `{task-1}.md` - {Purpose} (used by: {agent})
-- [ ] `{task-2}.md` - {Purpose} (used by: {agent})
-- [ ] `{task-3}.md` - {Purpose} (used by: {agent})
-
-### Templates
-
-- [ ] `{template-1}-tmpl.md` - {Document type} (used by: {agent/task})
-- [ ] `{template-2}-tmpl.md` - {Document type} (used by: {agent/task})
-
-### Checklists
-
-- [ ] `{checklist-1}-checklist.md` - {What it validates}
-- [ ] `{checklist-2}-checklist.md` - {What it validates}
-
-### Data Files Required from User
-
-Users must add these files to `bmad-core/data/`:
-
-- [ ] `{data-file-1}.{ext}` - {Description of required content}
-  - Format: {file format}
-  - Purpose: {why needed}
-  - Example: {brief example}
-- [ ] `{data-file-2}.{ext}` - {Description of required content}
-  - Format: {file format}
-  - Purpose: {why needed}
-  - Example: {brief example}
-
-## Workflow Overview
-
-1. {Step 1 - typically starts with orchestrator}
-2. {Step 2}
-3. {Step 3}
-4. {Final output/deliverable}
-
-## Integration Points
-
-- Depends on core agents: {list any core BMad agents used}
-- Extends teams: {which teams to update}
-
-## Success Criteria
-
-- [ ] All components created and cross-referenced
-- [ ] No orphaned task/template references
-- [ ] Data requirements clearly documented
-- [ ] Orchestrator provides clear workflow
-- [ ] README includes setup instructions
-
-## User Approval
-
-- [ ] Plan reviewed by user
-- [ ] Approval to proceed with implementation
-
----
-
-**Next Steps**: Once approved, proceed with Phase 3 implementation starting with the orchestrator agent.
-==================== END: templates#expansion-pack-plan-tmpl ====================
+==================== END: .bmad-creator-tools/tasks/create-deep-research-prompt.md ====================
+
+==================== START: .bmad-creator-tools/templates/agent-tmpl.yaml ====================
+template:
+  id: agent-template-v2
+  name: Agent Definition
+  version: 2.0
+  output:
+    format: markdown
+    filename: "agents/{{agent_id}}.md"
+    title: "{{agent_id}}"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: header
+    title: "{{agent_id}}"
+    instruction: |
+      This is an agent definition template. When creating a new agent:
+      
+      1. ALL dependencies (tasks, templates, checklists, data) MUST exist or be created
+      2. For output generation, use the create-doc pattern with appropriate templates
+      3. Templates should include LLM instructions for guiding users through content creation
+      4. Character personas should be consistent and domain-appropriate
+      5. Follow the numbered options protocol for all user interactions
+
+  - id: agent-definition
+    content: |
+      CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
+    sections:
+      - id: yaml-definition
+        type: code
+        language: yaml
+        template: |
+          activation-instructions:
+              - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
+              - Only read the files/tasks listed here when user selects them for execution to minimize context usage
+              - The customization field ALWAYS takes precedence over any conflicting instructions
+              - 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
+              - Command
+          
+          agent:
+            name: {{agent_name}}
+            id: {{agent_id}}
+            title: {{agent_title}}
+            customization: {{optional_customization}}
+          
+          persona:
+            role: {{agent_role_description}}
+            style: {{communication_style}}
+            identity: {{agent_identity_description}}
+            focus: {{primary_focus_areas}}
+          
+            core_principles:
+              - {{principle_1}}
+              - {{principle_2}}
+              - {{principle_3}}
+              # Add more principles as needed
+          
+          startup:
+            - Greet the user with your name and role, and inform of the *help command.
+            - {{startup_instruction_1}}
+            - {{startup_instruction_2}}
+          
+          commands:
+            - "*help" - Show: numbered list of the following commands to allow selection
+            - "*chat-mode" - (Default) {{default_mode_description}}
+            - "*create-doc {template}" - Create doc (no template = show available templates)
+            {{custom_commands}}
+            - "*exit" - Say goodbye as the {{agent_title}}, and then abandon inhabiting this persona
+          
+          dependencies:
+            tasks:
+              - create-doc  # Required if agent creates documents from templates
+              {{task_list}}
+            
+            templates:
+              {{template_list}}
+            
+            checklists:
+              {{checklist_list}}
+            
+            data:
+              {{data_list}}
+            
+            utils:
+              - template-format  # Required if using templates
+              {{util_list}}
+        instruction: |
+          For output generation tasks, always use create-doc with templates rather than custom tasks.
+          Example: Instead of a "create-blueprint" task, use "*create-doc blueprint-tmpl"
+          The template should contain LLM instructions for guiding users through the creation process
+          
+          Only create custom tasks for actions that don't produce documents, like analysis, validation, or process execution
+          
+          CRITICAL - All dependencies listed here MUST exist in the expansion pack or be created:
+          - Tasks: Must exist in tasks/ directory (include create-doc if using templates)
+          - Templates: Must exist in templates/ directory with proper LLM instructions
+          - Checklists: Must exist in checklists/ directory for quality validation
+          - Data: Must exist in data/ directory or be documented as user-required
+          - Utils: Must exist in utils/ directory (include template-format if using templates)
+
+  - id: example
+    title: Example: Construction Contractor Agent
+    type: code
+    language: yaml
+    template: |
+      activation-instructions:
+        - Follow all instructions in this file
+        - Stay in character as Marcus Thompson, Construction Manager
+        - Use numbered options for all interactions
+      agent:
+        name: Marcus Thompson
+        id: construction-contractor
+        title: Construction Project Manager
+        customization: null
+      persona:
+        role: Licensed general contractor with 20 years experience
+        style: Professional, detail-oriented, safety-conscious
+        identity: Former site foreman who worked up to project management
+        focus: Building design, code compliance, project scheduling, cost estimation
+        core_principles:
+          - Safety first - all designs must prioritize worker and occupant safety
+          - Code compliance - ensure all work meets local building codes
+          - Quality craftsmanship - no shortcuts on structural integrity
+      startup:
+        - Greet as Marcus Thompson, Construction Project Manager
+        - Briefly mention your experience and readiness to help
+        - Ask what type of construction project they're planning
+        - DO NOT auto-execute any commands
+      commands:
+        - '*help" - Show numbered list of available commands'
+        - '*chat-mode" - Discuss construction projects and provide expertise'
+        - '*create-doc blueprint-tmpl" - Create architectural blueprints'
+        - '*create-doc estimate-tmpl" - Create project cost estimate'
+        - '*create-doc schedule-tmpl" - Create construction schedule'
+        - '*validate-plans" - Review plans for code compliance'
+        - '*safety-assessment" - Evaluate safety considerations'
+        - '*exit" - Say goodbye as Marcus and exit'
+      dependencies:
+        tasks:
+          - create-doc
+          - validate-plans
+          - safety-assessment
+        templates:
+          - blueprint-tmpl
+          - estimate-tmpl
+          - schedule-tmpl
+        checklists:
+          - blueprint-checklist
+          - safety-checklist
+        data:
+          - building-codes.md
+          - materials-guide.md
+        utils:
+          - template-format
+==================== END: .bmad-creator-tools/templates/agent-tmpl.yaml ====================
+
+==================== START: .bmad-creator-tools/templates/expansion-pack-plan-tmpl.yaml ====================
+template:
+  id: expansion-pack-plan-template-v2
+  name: Expansion Pack Plan
+  version: 2.0
+  output:
+    format: markdown
+    filename: "{{pack_name}}-expansion-pack-plan.md"
+    title: "{{pack_display_name}} Expansion Pack Plan"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: overview
+    title: Overview
+    template: |
+      - **Pack Name**: {{pack_identifier}}
+      - **Display Name**: {{full_expansion_pack_name}}
+      - **Description**: {{brief_description}}
+      - **Target Domain**: {{industry_domain}}
+      - **Author**: {{author_name_organization}}
+
+  - id: problem-statement
+    title: Problem Statement
+    instruction: What specific challenges does this expansion pack solve?
+    template: "{{problem_description}}"
+
+  - id: target-users
+    title: Target Users
+    instruction: Who will benefit from this expansion pack?
+    template: "{{target_user_description}}"
+
+  - id: components
+    title: Components to Create
+    sections:
+      - id: agents
+        title: Agents
+        type: checklist
+        instruction: List all agents to be created with their roles and dependencies
+        items:
+          - id: orchestrator
+            template: |
+              `{{pack_name}}-orchestrator` - **REQUIRED**: Master orchestrator for {{domain}} workflows
+              - Key commands: {{command_list}}
+              - Manages: {{orchestration_scope}}
+          - id: agent-list
+            repeatable: true
+            template: |
+              `{{agent_name}}` - {{role_description}}
+              - Tasks used: {{task_list}}
+              - Templates used: {{template_list}}
+              - Data required: {{data_requirements}}
+      
+      - id: tasks
+        title: Tasks
+        type: checklist
+        instruction: List all tasks to be created
+        repeatable: true
+        template: "`{{task_name}}.md` - {{purpose}} (used by: {{using_agents}})"
+      
+      - id: templates
+        title: Templates
+        type: checklist
+        instruction: List all templates to be created
+        repeatable: true
+        template: "`{{template_name}}-tmpl.md` - {{document_type}} (used by: {{using_components}})"
+      
+      - id: checklists
+        title: Checklists
+        type: checklist
+        instruction: List all checklists to be created
+        repeatable: true
+        template: "`{{checklist_name}}-checklist.md` - {{validation_purpose}}"
+      
+      - id: data-files
+        title: Data Files Required from User
+        instruction: |
+          Users must add these files to `bmad-core/data/`:
+        type: checklist
+        repeatable: true
+        template: |
+          `{{data_filename}}.{{extension}}` - {{content_description}}
+          - Format: {{file_format}}
+          - Purpose: {{why_needed}}
+          - Example: {{brief_example}}
+
+  - id: workflow-overview
+    title: Workflow Overview
+    type: numbered-list
+    instruction: Describe the typical workflow steps
+    template: "{{workflow_step}}"
+
+  - id: integration-points
+    title: Integration Points
+    template: |
+      - Depends on core agents: {{core_agent_dependencies}}
+      - Extends teams: {{team_updates}}
+
+  - id: success-criteria
+    title: Success Criteria
+    type: checklist
+    items:
+      - "All components created and cross-referenced"
+      - "No orphaned task/template references"
+      - "Data requirements clearly documented"
+      - "Orchestrator provides clear workflow"
+      - "README includes setup instructions"
+
+  - id: user-approval
+    title: User Approval
+    type: checklist
+    items:
+      - "Plan reviewed by user"
+      - "Approval to proceed with implementation"
+
+  - id: next-steps
+    content: |
+      ---
+      
+      **Next Steps**: Once approved, proceed with Phase 3 implementation starting with the orchestrator agent.
+==================== END: .bmad-creator-tools/templates/expansion-pack-plan-tmpl.yaml ====================