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

refactor: update file paths to remove leading dot from bmad-core references

Browse Source
This commit is contained in:
manjaroblack
2025-08-18 09:46:16 -05:00
parent aa9777a06e
commit ed7291f2ce
41 changed files with 901 additions and 909 deletions
Download Patch File Download Diff File Expand all files Collapse all files

160
dist/teams/team-ide-minimal.txt vendored
View File

@@ -8,13 +8,13 @@ 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: .bmad-core/folder/filename.md ====================`
- `==================== END: .bmad-core/folder/filename.md ====================`
- `==================== START: bmad-core/folder/filename.md ====================`
- `==================== END: bmad-core/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 the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/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: .bmad-core/utils/template-format.md ====================`
- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
- `tasks: create-story` → Look for `==================== START: bmad-core/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.
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
---
==================== START: .bmad-core/agent-teams/team-ide-minimal.yaml ====================
==================== START: bmad-core/agent-teams/team-ide-minimal.yaml ====================
# <!-- Powered by BMAD™ Core -->
bundle:
name: Team IDE Minimal
@@ -51,9 +51,9 @@ agents:
- dev
- qa
workflows: null
==================== END: .bmad-core/agent-teams/team-ide-minimal.yaml ====================
==================== END: bmad-core/agent-teams/team-ide-minimal.yaml ====================
==================== START: .bmad-core/agents/bmad-orchestrator.md ====================
==================== START: bmad-core/agents/bmad-orchestrator.md ====================
# bmad-orchestrator
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:
@@ -178,9 +178,9 @@ dependencies:
utils:
- workflow-management.md
```
==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
==================== END: bmad-core/agents/bmad-orchestrator.md ====================
==================== START: .bmad-core/agents/po.md ====================
==================== START: bmad-core/agents/po.md ====================
# po
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:
@@ -237,9 +237,9 @@ dependencies:
templates:
- story-tmpl.yaml
```
==================== END: .bmad-core/agents/po.md ====================
==================== END: bmad-core/agents/po.md ====================
==================== START: .bmad-core/agents/sm.md ====================
==================== START: bmad-core/agents/sm.md ====================
# sm
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:
@@ -282,9 +282,9 @@ dependencies:
templates:
- story-tmpl.yaml
```
==================== END: .bmad-core/agents/sm.md ====================
==================== END: bmad-core/agents/sm.md ====================
==================== START: .bmad-core/agents/dev.md ====================
==================== START: bmad-core/agents/dev.md ====================
# dev
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:
@@ -335,9 +335,9 @@ dependencies:
- execute-checklist.md
- validate-next-story.md
```
==================== END: .bmad-core/agents/dev.md ====================
==================== END: bmad-core/agents/dev.md ====================
==================== START: .bmad-core/agents/qa.md ====================
==================== START: bmad-core/agents/qa.md ====================
# qa
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:
@@ -406,9 +406,9 @@ dependencies:
- qa-gate-tmpl.yaml
- story-tmpl.yaml
```
==================== END: .bmad-core/agents/qa.md ====================
==================== END: bmad-core/agents/qa.md ====================
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
==================== START: bmad-core/tasks/advanced-elicitation.md ====================
<!-- Powered by BMAD™ Core -->
# Advanced Elicitation Task
@@ -527,9 +527,9 @@ Choose a number (0-8) or 9 to proceed:
- **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-core/tasks/advanced-elicitation.md ====================
==================== END: bmad-core/tasks/advanced-elicitation.md ====================
==================== START: .bmad-core/tasks/create-doc.md ====================
==================== START: bmad-core/tasks/create-doc.md ====================
<!-- Powered by BMAD™ Core -->
# Create Document from Template (YAML Driven)
@@ -548,7 +548,7 @@ When this task is invoked:
## Critical: Template Discovery
If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
## CRITICAL: Mandatory Elicitation Format
@@ -632,9 +632,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
- Select options 2-9 from data/elicitation-methods only
- Provide detailed rationale explaining decisions
- End with "Select 1-9 or just type your question/feedback:"
==================== END: .bmad-core/tasks/create-doc.md ====================
==================== END: bmad-core/tasks/create-doc.md ====================
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
==================== START: bmad-core/tasks/kb-mode-interaction.md ====================
<!-- Powered by BMAD™ Core -->
# KB Mode Interaction Task
@@ -711,9 +711,9 @@ Or ask me about anything else related to BMad-Method!
**User**: Tell me about workflows
**Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
==================== END: bmad-core/tasks/kb-mode-interaction.md ====================
==================== START: .bmad-core/data/bmad-kb.md ====================
==================== START: bmad-core/data/bmad-kb.md ====================
<!-- Powered by BMAD™ Core -->
# BMAD™ Knowledge Base
@@ -822,7 +822,7 @@ npx bmad-method install
**Verify Installation**:
- `.bmad-core/` folder created with all agents
- `bmad-core/` folder created with all agents
- IDE-specific integration files created
- All agent commands/rules/modes available
@@ -1521,9 +1521,9 @@ Use the **expansion-creator** pack to build your own:
- **Documentation**: Check `docs/` folder for project-specific context
- **Community**: Discord and GitHub resources available for support
- **Contributing**: See `CONTRIBUTING.md` for full guidelines
==================== END: .bmad-core/data/bmad-kb.md ====================
==================== END: bmad-core/data/bmad-kb.md ====================
==================== START: .bmad-core/data/elicitation-methods.md ====================
==================== START: bmad-core/data/elicitation-methods.md ====================
<!-- Powered by BMAD™ Core -->
# Elicitation Methods Data
@@ -1679,9 +1679,9 @@ Use the **expansion-creator** pack to build your own:
- Acknowledge choice to finalize current work
- Accept output as-is or move to next step
- Prepare to continue without additional elicitation
==================== END: .bmad-core/data/elicitation-methods.md ====================
==================== END: bmad-core/data/elicitation-methods.md ====================
==================== START: .bmad-core/utils/workflow-management.md ====================
==================== START: bmad-core/utils/workflow-management.md ====================
<!-- Powered by BMAD™ Core -->
# Workflow Management
@@ -1752,15 +1752,15 @@ Handle conditional paths by asking clarifying questions when needed.
## Agent Integration
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
==================== END: .bmad-core/utils/workflow-management.md ====================
==================== END: bmad-core/utils/workflow-management.md ====================
==================== START: .bmad-core/tasks/correct-course.md ====================
==================== START: bmad-core/tasks/correct-course.md ====================
<!-- Powered by BMAD™ Core -->
# Correct Course Task
## Purpose
- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
- Guide a structured response to a change trigger using the `bmad-core/checklists/change-checklist`.
- Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
- Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
- Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
@@ -1774,7 +1774,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
- **Acknowledge Task & Inputs:**
- Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
- Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
- Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
- Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `bmad-core/checklists/change-checklist`.
- **Establish Interaction Mode:**
- Ask the user their preferred interaction mode for this task:
- **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
@@ -1826,9 +1826,9 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
- A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
- Specific, clearly drafted proposed edits for all affected project artifacts.
- **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
==================== END: .bmad-core/tasks/correct-course.md ====================
==================== END: bmad-core/tasks/correct-course.md ====================
==================== START: .bmad-core/tasks/execute-checklist.md ====================
==================== START: bmad-core/tasks/execute-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Checklist Validation Task
@@ -1836,7 +1836,7 @@ This task provides instructions for validating documentation against checklists.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the .bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
## Instructions
@@ -1844,7 +1844,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from .bmad-core/checklists/
- Load the appropriate checklist from bmad-core/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder
@@ -1916,9 +1916,9 @@ The LLM will:
- Execute the complete checklist validation
- Present a final report with pass/fail rates and key findings
- Offer to provide detailed analysis of any section, especially those with warnings or failures
==================== END: .bmad-core/tasks/execute-checklist.md ====================
==================== END: bmad-core/tasks/execute-checklist.md ====================
==================== START: .bmad-core/tasks/shard-doc.md ====================
==================== START: bmad-core/tasks/shard-doc.md ====================
<!-- Powered by BMAD™ Core -->
# Document Sharding Task
@@ -1930,20 +1930,20 @@ The LLM will:
## Primary Method: Automatic with markdown-tree
[[LLM: First, check if markdownExploder is set to true in .bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
2. Or set markdownExploder to false in .bmad-core/core-config.yaml
2. Or set markdownExploder to false in bmad-core/core-config.yaml
**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
1. Set markdownExploder to true in .bmad-core/core-config.yaml
1. Set markdownExploder to true in bmad-core/core-config.yaml
2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
I will now proceed with the manual sharding process."
@@ -2105,9 +2105,9 @@ Document sharded successfully:
- Preserve ALL formatting, including whitespace where significant
- Handle edge cases like sections with code blocks containing ## symbols
- Ensure the sharding is reversible (could reconstruct the original from shards)
==================== END: .bmad-core/tasks/shard-doc.md ====================
==================== END: bmad-core/tasks/shard-doc.md ====================
==================== START: .bmad-core/tasks/validate-next-story.md ====================
==================== START: bmad-core/tasks/validate-next-story.md ====================
<!-- Powered by BMAD™ Core -->
# Validate Next Story Task
@@ -2119,7 +2119,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
### 0. Load Core Configuration and Inputs
- Load `.bmad-core/core-config.yaml`
- Load `bmad-core/core-config.yaml`
- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
- Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
- Identify and load the following inputs:
@@ -2243,9 +2243,9 @@ Provide a structured validation report including:
- **NO-GO**: Story requires fixes before implementation
- **Implementation Readiness Score**: 1-10 scale
- **Confidence Level**: High/Medium/Low for successful implementation
==================== END: .bmad-core/tasks/validate-next-story.md ====================
==================== END: bmad-core/tasks/validate-next-story.md ====================
==================== START: .bmad-core/templates/story-tmpl.yaml ====================
==================== START: bmad-core/templates/story-tmpl.yaml ====================
# <!-- Powered by BMAD™ Core -->
template:
id: story-template-v2
@@ -2384,9 +2384,9 @@ sections:
instruction: Results from QA Agent QA review of the completed story implementation
owner: qa-agent
editors: [qa-agent]
==================== END: .bmad-core/templates/story-tmpl.yaml ====================
==================== END: bmad-core/templates/story-tmpl.yaml ====================
==================== START: .bmad-core/checklists/change-checklist.md ====================
==================== START: bmad-core/checklists/change-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Change Navigation Checklist
@@ -2570,9 +2570,9 @@ Keep it action-oriented and forward-looking.]]
- [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
---
==================== END: .bmad-core/checklists/change-checklist.md ====================
==================== END: bmad-core/checklists/change-checklist.md ====================
==================== START: .bmad-core/checklists/po-master-checklist.md ====================
==================== START: bmad-core/checklists/po-master-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Product Owner (PO) Master Validation Checklist
@@ -3006,9 +3006,9 @@ After presenting the report, ask if the user wants:
- **APPROVED**: The plan is comprehensive, properly sequenced, and ready for implementation.
- **CONDITIONAL**: The plan requires specific adjustments before proceeding.
- **REJECTED**: The plan requires significant revision to address critical deficiencies.
==================== END: .bmad-core/checklists/po-master-checklist.md ====================
==================== END: bmad-core/checklists/po-master-checklist.md ====================
==================== START: .bmad-core/tasks/create-next-story.md ====================
==================== START: bmad-core/tasks/create-next-story.md ====================
<!-- Powered by BMAD™ Core -->
# Create Next Story Task
@@ -3020,7 +3020,7 @@ To identify the next logical story based on project progress and epic definition
### 0. Load Core Configuration and Check Workflow
- Load `.bmad-core/core-config.yaml` from the project root
- Load `bmad-core/core-config.yaml` from the project root
- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
- Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`, `workflow.*`
@@ -3114,17 +3114,17 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
- Verify all source references are included for technical details
- Ensure tasks align with both epic requirements and architecture constraints
- Update status to "Draft" and save the story file
- Execute `.bmad-core/tasks/execute-checklist` `.bmad-core/checklists/story-draft-checklist`
- Execute `bmad-core/tasks/execute-checklist` `bmad-core/checklists/story-draft-checklist`
- Provide summary to user including:
- Story created: `{devStoryLocation}/{epicNum}.{storyNum}.story.md`
- Status: Draft
- Key technical components included from architecture docs
- Any deviations or conflicts noted between epic and architecture
- Checklist Results
- Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `.bmad-core/tasks/validate-next-story`
==================== END: .bmad-core/tasks/create-next-story.md ====================
- Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `bmad-core/tasks/validate-next-story`
==================== END: bmad-core/tasks/create-next-story.md ====================
==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
==================== START: bmad-core/checklists/story-draft-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Story Draft Checklist
@@ -3279,9 +3279,9 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
- READY: The story provides sufficient context for implementation
- NEEDS REVISION: The story requires updates (see issues)
- BLOCKED: External information required (specify what information)
==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
==================== END: bmad-core/checklists/story-draft-checklist.md ====================
==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
==================== START: bmad-core/tasks/apply-qa-fixes.md ====================
<!-- Powered by BMAD™ Core -->
# apply-qa-fixes
@@ -3431,9 +3431,9 @@ Fix plan:
- Tests validate behavior and close gaps
- Strict adherence to allowed story update areas
- Gate ownership remains with QA; Dev signals readiness via Status
==================== END: .bmad-core/tasks/apply-qa-fixes.md ====================
==================== END: bmad-core/tasks/apply-qa-fixes.md ====================
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
==================== START: bmad-core/checklists/story-dod-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Story Definition of Done (DoD) Checklist
@@ -3529,9 +3529,9 @@ After completing the checklist:
Be honest - it's better to flag issues now than have them discovered later.]]
- [ ] I, the Developer Agent, confirm that all applicable items above have been addressed.
==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
==================== END: bmad-core/checklists/story-dod-checklist.md ====================
==================== START: .bmad-core/tasks/nfr-assess.md ====================
==================== START: bmad-core/tasks/nfr-assess.md ====================
<!-- Powered by BMAD™ Core -->
# nfr-assess
@@ -3876,9 +3876,9 @@ performance_deep_dive:
```
</details>
==================== END: .bmad-core/tasks/nfr-assess.md ====================
==================== END: bmad-core/tasks/nfr-assess.md ====================
==================== START: .bmad-core/tasks/qa-gate.md ====================
==================== START: bmad-core/tasks/qa-gate.md ====================
<!-- Powered by BMAD™ Core -->
# qa-gate
@@ -4041,9 +4041,9 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
- Always write to standard path
- Always update story with gate reference
- Clear, actionable findings
==================== END: .bmad-core/tasks/qa-gate.md ====================
==================== END: bmad-core/tasks/qa-gate.md ====================
==================== START: .bmad-core/tasks/review-story.md ====================
==================== START: bmad-core/tasks/review-story.md ====================
<!-- Powered by BMAD™ Core -->
# review-story
@@ -4359,9 +4359,9 @@ After review:
3. Recommend status: "Ready for Done" or "Changes Required" (owner decides)
4. If files were modified, list them in QA Results and ask Dev to update File List
5. Always provide constructive feedback and actionable recommendations
==================== END: .bmad-core/tasks/review-story.md ====================
==================== END: bmad-core/tasks/review-story.md ====================
==================== START: .bmad-core/tasks/risk-profile.md ====================
==================== START: bmad-core/tasks/risk-profile.md ====================
<!-- Powered by BMAD™ Core -->
# risk-profile
@@ -4716,9 +4716,9 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
- Link risks to specific test requirements
- Track residual risk after mitigation
- Update risk profile as story evolves
==================== END: .bmad-core/tasks/risk-profile.md ====================
==================== END: bmad-core/tasks/risk-profile.md ====================
==================== START: .bmad-core/tasks/test-design.md ====================
==================== START: bmad-core/tasks/test-design.md ====================
<!-- Powered by BMAD™ Core -->
# test-design
@@ -4894,9 +4894,9 @@ Before finalizing, verify:
- **Efficient coverage**: Test once at the right level
- **Maintainability**: Consider long-term test maintenance
- **Fast feedback**: Quick tests run first
==================== END: .bmad-core/tasks/test-design.md ====================
==================== END: bmad-core/tasks/test-design.md ====================
==================== START: .bmad-core/tasks/trace-requirements.md ====================
==================== START: bmad-core/tasks/trace-requirements.md ====================
<!-- Powered by BMAD™ Core -->
# trace-requirements
@@ -5162,9 +5162,9 @@ Trace matrix: qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
- Identify both presence and absence
- Prioritize based on risk
- Make recommendations actionable
==================== END: .bmad-core/tasks/trace-requirements.md ====================
==================== END: bmad-core/tasks/trace-requirements.md ====================
==================== START: .bmad-core/templates/qa-gate-tmpl.yaml ====================
==================== START: bmad-core/templates/qa-gate-tmpl.yaml ====================
# <!-- Powered by BMAD™ Core -->
template:
id: qa-gate-template-v1
@@ -5268,11 +5268,11 @@ optional_fields_examples:
future: # Can be addressed later
- action: "Consider caching for better performance"
refs: ["services/data.service.ts"]
==================== END: .bmad-core/templates/qa-gate-tmpl.yaml ====================
==================== END: bmad-core/templates/qa-gate-tmpl.yaml ====================
==================== START: .bmad-core/data/technical-preferences.md ====================
==================== START: bmad-core/data/technical-preferences.md ====================
<!-- Powered by BMAD™ Core -->
# User-Defined Preferred Patterns and Preferences
None Listed
==================== END: .bmad-core/data/technical-preferences.md ====================
==================== END: bmad-core/data/technical-preferences.md ====================