ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

web build optimization

Browse Source
This commit is contained in:
Brian Madison
2025-07-06 10:32:39 -05:00
parent 4b0a9235ab
commit 5fc69d773a
30 changed files with 1346 additions and 1360 deletions
Download Patch File Download Diff File Expand all files Collapse all files

57
dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt vendored
View File

@@ -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 ====================