bmad-method 4.26.0 → 4.27.0

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:
@@ -92,9 +93,9 @@ dependencies:
     - agent-tmpl
     - expansion-pack-plan-tmpl
 ```
-==================== 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 +296,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 +1319,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 +1329,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**:
+
+1. **Always Include Core Methods** (choose 3-4):
+   - Expand or Contract for Audience
+   - Critique and Refine
+   - Identify Potential Risks
+   - Assess Alignment with Goals
 
-### 2. Processing Guidelines
+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
 
-**Do NOT show:**
+3. **Always Include**: "Proceed / No Further Actions" as option 9
 
-- 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
+### 2. Section Context and Review
 
-**After user selection from the list:**
+When invoked after outputting a section:
 
-- 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
+1. **Provide Context Summary**: Give a brief 1-2 sentence summary of what the user should look for in the section just presented
 
-## Action Definitions
+2. **Explain Visual Elements**: If the section contains diagrams, explain them briefly before offering elicitation options
 
-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.]]
+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)
 
-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. Present Elicitation Options
 
-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.]]
+**Review Request Process:**
 
-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.]]
+- 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
 
-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.]]
+**Action List Presentation Format:**
 
-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.]]
+```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
+```
 
-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.]]
+**Response Handling:**
 
-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.]]
+- **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
 
-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?]]
+### 4. Method Execution Framework
 
-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 ====================
+**Execution Process:**
+
+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: tasks#create-deep-research-prompt ====================
+==================== 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,9 +1743,9 @@ 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 ====================
+==================== END: .bmad-creator-tools/tasks/create-deep-research-prompt.md ====================
 
-==================== START: templates#agent-tmpl ====================
+==================== START: .bmad-creator-tools/templates/agent-tmpl.md ====================
 # [AGENT_ID]
 
 [[LLM: This is an agent definition template. When creating a new agent:
@@ -1863,9 +1889,9 @@ dependencies:
   utils:
     - template-format
 ```
-==================== END: templates#agent-tmpl ====================
+==================== END: .bmad-creator-tools/templates/agent-tmpl.md ====================
 
-==================== START: templates#expansion-pack-plan-tmpl ====================
+==================== START: .bmad-creator-tools/templates/expansion-pack-plan-tmpl.md ====================
 # {Pack Name} Expansion Pack Plan
 
 ## Overview
@@ -1957,4 +1983,4 @@ Users must add these files to `bmad-core/data/`:
 ---
 
 **Next Steps**: Once approved, proceed with Phase 3 implementation starting with the orchestrator agent.
-==================== END: templates#expansion-pack-plan-tmpl ====================
+==================== END: .bmad-creator-tools/templates/expansion-pack-plan-tmpl.md ====================

package/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.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-infrastructure-devops/folder/filename.md ====================`
+- `==================== END: .bmad-infrastructure-devops/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-infrastructure-devops/personas/analyst.md`, `.bmad-infrastructure-devops/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-infrastructure-devops/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: .bmad-infrastructure-devops/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#infra-devops-platform ====================
+
+==================== START: .bmad-infrastructure-devops/agents/infra-devops-platform.md ====================
 # infra-devops-platform
 
 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:
@@ -98,9 +99,9 @@ dependencies:
   utils:
     - template-format
 ```
-==================== END: agents#infra-devops-platform ====================
+==================== END: .bmad-infrastructure-devops/agents/infra-devops-platform.md ====================
 
-==================== START: tasks#create-doc ====================
+==================== START: .bmad-infrastructure-devops/tasks/create-doc.md ====================
 # Create Document from Template Task
 
 ## Purpose
@@ -120,7 +121,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 
 [[LLM: Check if plan tracking is enabled in core-config.yaml]]
 
-- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
+- If `workflow.trackProgress: true`, check for active plan using .bmad-infrastructure-devops/utils/plan-management.md
 - If plan exists and this document creation is part of the plan:
   - Verify this is the expected next step
   - If out of sequence and `enforceSequence: true`, warn user and halt without user override
@@ -129,7 +130,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 
 ### 1. Identify Template
 
-- Load from `templates#*` or `{root}/templates directory`
+- Load from `.bmad-infrastructure-devops/templates/*.md` or `.bmad-infrastructure-devops/templates directory`
 - Agent-specific templates are listed in agent's dependencies
 - If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
 
@@ -147,14 +148,14 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 
 ### 4. Key Execution Patterns
 
-**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
+**When you see:** `[[LLM: Draft X and immediately execute .bmad-infrastructure-devops/tasks/advanced-elicitation.md]]`
 
 - Draft the content
 - Present it to user
 - IMMEDIATELY execute the task
 - Wait for completion before continuing
 
-**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
+**When you see:** `[[LLM: After section completion, apply .bmad-infrastructure-devops/tasks/Y.md]]`
 
 - Finish the section
 - STOP and execute the task
@@ -192,9 +193,9 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 ## Remember
 
 Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
-==================== END: tasks#create-doc ====================
+==================== END: .bmad-infrastructure-devops/tasks/create-doc.md ====================
 
-==================== START: tasks#review-infrastructure ====================
+==================== START: .bmad-infrastructure-devops/tasks/review-infrastructure.md ====================
 # Infrastructure Review Task
 
 ## Purpose
@@ -355,9 +356,9 @@ Present the user with the following list of 'Advanced Reflective, Elicitation &
 After I perform the selected action, we can discuss the outcome and decide on any further revisions for this section."
 
 REPEAT by Asking the user if they would like to perform another Reflective, Elicitation & Brainstorming Action UNTIL the user indicates it is time to proceed to the next section (or selects #8)
-==================== END: tasks#review-infrastructure ====================
+==================== END: .bmad-infrastructure-devops/tasks/review-infrastructure.md ====================
 
-==================== START: tasks#validate-infrastructure ====================
+==================== START: .bmad-infrastructure-devops/tasks/validate-infrastructure.md ====================
 # Infrastructure Validation Task
 
 ## Purpose
@@ -512,9 +513,9 @@ Present the user with the following list of 'Advanced Reflective, Elicitation &
 After I perform the selected action, we can discuss the outcome and decide on any further revisions for this section."
 
 REPEAT by Asking the user if they would like to perform another Reflective, Elicitation & Brainstorming Action UNTIL the user indicates it is time to proceed to the next section (or selects #8)
-==================== END: tasks#validate-infrastructure ====================
+==================== END: .bmad-infrastructure-devops/tasks/validate-infrastructure.md ====================
 
-==================== START: templates#infrastructure-architecture-tmpl ====================
+==================== START: .bmad-infrastructure-devops/templates/infrastructure-architecture-tmpl.md ====================
 # {{Project Name}} Infrastructure Architecture
 
 [[LLM: Initial Setup
@@ -930,9 +931,9 @@ Define specific criteria for validating correct implementation:
 _Document Version: 1.0_
 _Last Updated: {{current_date}}_
 _Next Review: {{review_date}}_
-==================== END: templates#infrastructure-architecture-tmpl ====================
+==================== END: .bmad-infrastructure-devops/templates/infrastructure-architecture-tmpl.md ====================
 
-==================== START: templates#infrastructure-platform-from-arch-tmpl ====================
+==================== START: .bmad-infrastructure-devops/templates/infrastructure-platform-from-arch-tmpl.md ====================
 # {{Project Name}} Platform Infrastructure Implementation
 
 [[LLM: Initial Setup
@@ -1548,9 +1549,9 @@ _Platform Version: 1.0_
 _Implementation Date: {{implementation_date}}_
 _Next Review: {{review_date}}_
 _Approved by: {{architect_name}} (Architect), {{devops_name}} (DevOps/Platform Engineer)_
-==================== END: templates#infrastructure-platform-from-arch-tmpl ====================
+==================== END: .bmad-infrastructure-devops/templates/infrastructure-platform-from-arch-tmpl.md ====================
 
-==================== START: checklists#infrastructure-checklist ====================
+==================== START: .bmad-infrastructure-devops/checklists/infrastructure-checklist.md ====================
 # Infrastructure Change Validation Checklist
 
 This checklist serves as a comprehensive framework for validating infrastructure changes before deployment to production. The DevOps/Platform Engineer should systematically work through each item, ensuring the infrastructure is secure, compliant, resilient, and properly implemented according to organizational standards.
@@ -2035,15 +2036,15 @@ This checklist serves as a comprehensive framework for validating infrastructure
 - [ ] Local development environment compatibility verified
 - [ ] Platform component integration validated
 - [ ] Cross-platform functionality tested and verified
-==================== END: checklists#infrastructure-checklist ====================
+==================== END: .bmad-infrastructure-devops/checklists/infrastructure-checklist.md ====================
 
-==================== START: data#technical-preferences ====================
+==================== START: .bmad-infrastructure-devops/data/technical-preferences.md ====================
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: data#technical-preferences ====================
+==================== END: .bmad-infrastructure-devops/data/technical-preferences.md ====================
 
-==================== START: utils#template-format ====================
+==================== START: .bmad-infrastructure-devops/utils/template-format.md ====================
 # Template Format Conventions
 
 Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
@@ -2070,4 +2071,4 @@ Templates in the BMad method use standardized markup for AI processing. These co
 - Template elements are for AI processing only
 - Focus on faithful template execution and clean output
 - All template-specific instructions are embedded within templates
-==================== END: utils#template-format ====================
+==================== END: .bmad-infrastructure-devops/utils/template-format.md ====================