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

62
dist/agents/architect.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/agents/architect.md ====================
==================== START: bmad-core/agents/architect.md ====================
# architect
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:
@@ -102,9 +102,9 @@ dependencies:
- front-end-architecture-tmpl.yaml
- fullstack-architecture-tmpl.yaml
```
==================== END: .bmad-core/agents/architect.md ====================
==================== END: bmad-core/agents/architect.md ====================
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
==================== START: bmad-core/tasks/create-deep-research-prompt.md ====================
<!-- Powered by BMAD™ Core -->
# Create Deep Research Prompt Task
@@ -384,9 +384,9 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
- Balance comprehensiveness with focus
- Document assumptions and limitations clearly
- Plan for iterative refinement based on initial findings
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
==================== END: bmad-core/tasks/create-deep-research-prompt.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)
@@ -405,7 +405,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
@@ -489,9 +489,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/document-project.md ====================
==================== START: bmad-core/tasks/document-project.md ====================
<!-- Powered by BMAD™ Core -->
# Document an Existing Project
@@ -836,9 +836,9 @@ Apply the advanced elicitation task after major sections to refine based on user
- Documents technical debt, workarounds, and constraints honestly
- For brownfield projects with PRD: Provides clear enhancement impact analysis
- The goal is PRACTICAL documentation for AI agents doing real work
==================== END: .bmad-core/tasks/document-project.md ====================
==================== END: bmad-core/tasks/document-project.md ====================
==================== START: .bmad-core/tasks/execute-checklist.md ====================
==================== START: bmad-core/tasks/execute-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Checklist Validation Task
@@ -846,7 +846,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
@@ -854,7 +854,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
@@ -926,9 +926,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/templates/architecture-tmpl.yaml ====================
==================== START: bmad-core/templates/architecture-tmpl.yaml ====================
# <!-- Powered by BMAD™ Core -->
template:
id: architecture-template-v2
@@ -1059,7 +1059,7 @@ sections:
instruction: |
This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
1. Review PRD technical assumptions and any preferences from .bmad-core/data/technical-preferences.yaml or an attached technical-preferences
1. Review PRD technical assumptions and any preferences from bmad-core/data/technical-preferences.yaml or an attached technical-preferences
2. For each category, present 2-3 viable options with pros/cons
3. Make a clear recommendation based on project needs
4. Get explicit user approval for each selection
@@ -1580,9 +1580,9 @@ sections:
- Key UI requirements from PRD
- Any frontend-specific decisions made here
- Request for detailed frontend architecture
==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
==================== END: bmad-core/templates/architecture-tmpl.yaml ====================
==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
==================== START: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
# <!-- Powered by BMAD™ Core -->
template:
id: brownfield-architecture-template-v2
@@ -2060,9 +2060,9 @@ sections:
- Key technical decisions based on real project constraints
- Existing system compatibility requirements with specific verification steps
- Clear sequencing of implementation to minimize risk to existing functionality
==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
==================== END: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
==================== START: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
# <!-- Powered by BMAD™ Core -->
template:
id: frontend-architecture-template-v2
@@ -2282,9 +2282,9 @@ sections:
- Key import patterns
- File naming conventions
- Project-specific patterns and utilities
==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
==================== END: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
==================== START: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
# <!-- Powered by BMAD™ Core -->
template:
id: fullstack-architecture-template-v2
@@ -3109,9 +3109,9 @@ sections:
- id: checklist-results
title: Checklist Results Report
instruction: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the architect-checklist and populate results here.
==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
==================== END: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
==================== START: .bmad-core/checklists/architect-checklist.md ====================
==================== START: bmad-core/checklists/architect-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Architect Solution Validation Checklist
@@ -3551,11 +3551,11 @@ Now that you've completed the checklist, generate a comprehensive validation rep
- Component design clarity
After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]
==================== END: .bmad-core/checklists/architect-checklist.md ====================
==================== END: bmad-core/checklists/architect-checklist.md ====================
==================== 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 ====================