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

80
dist/agents/pm.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/pm.md ====================
==================== START: bmad-core/agents/pm.md ====================
# pm
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:
@@ -101,9 +101,9 @@ dependencies:
- brownfield-prd-tmpl.yaml
- prd-tmpl.yaml
```
==================== END: .bmad-core/agents/pm.md ====================
==================== END: bmad-core/agents/pm.md ====================
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
==================== START: bmad-core/tasks/brownfield-create-epic.md ====================
<!-- Powered by BMAD™ Core -->
# Create Brownfield Epic Task
@@ -265,9 +265,9 @@ The epic creation is successful when:
- If the scope grows beyond 3 stories, consider the full brownfield PRD process
- Always prioritize existing system integrity over new functionality
- When in doubt about scope or complexity, escalate to full brownfield planning
==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
==================== END: bmad-core/tasks/brownfield-create-epic.md ====================
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
==================== START: bmad-core/tasks/brownfield-create-story.md ====================
<!-- Powered by BMAD™ Core -->
# Create Brownfield Story Task
@@ -416,15 +416,15 @@ The story creation is successful when:
- Always prioritize existing system integrity
- When in doubt about integration complexity, use brownfield-create-epic instead
- Stories should take no more than 4 hours of focused development work
==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
==================== END: bmad-core/tasks/brownfield-create-story.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.
@@ -438,7 +438,7 @@ The story creation is successful when:
- **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."
@@ -490,9 +490,9 @@ The story creation is successful when:
- 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/create-deep-research-prompt.md ====================
==================== START: bmad-core/tasks/create-deep-research-prompt.md ====================
<!-- Powered by BMAD™ Core -->
# Create Deep Research Prompt Task
@@ -772,9 +772,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)
@@ -793,7 +793,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
@@ -877,9 +877,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/execute-checklist.md ====================
==================== START: bmad-core/tasks/execute-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Checklist Validation Task
@@ -887,7 +887,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
@@ -895,7 +895,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
@@ -967,9 +967,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
@@ -981,20 +981,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."
@@ -1156,9 +1156,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/templates/brownfield-prd-tmpl.yaml ====================
==================== START: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
# <!-- Powered by BMAD™ Core -->
template:
id: brownfield-prd-template-v2
@@ -1440,9 +1440,9 @@ sections:
- template: "IV1: {{existing_functionality_verification}}"
- template: "IV2: {{integration_point_verification}}"
- template: "IV3: {{performance_impact_verification}}"
==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
==================== END: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
==================== START: bmad-core/templates/prd-tmpl.yaml ====================
# <!-- Powered by BMAD™ Core -->
template:
id: prd-template-v2
@@ -1545,7 +1545,7 @@ sections:
instruction: |
Gather technical decisions that will guide the Architect. Steps:
1. Check if .bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
1. Check if bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
3. For unknowns, offer guidance based on project goals and MVP scope
4. Document ALL technical choices with rationale (why this choice fits the project)
@@ -1646,9 +1646,9 @@ sections:
- id: architect-prompt
title: Architect Prompt
instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.
==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
==================== END: bmad-core/templates/prd-tmpl.yaml ====================
==================== START: .bmad-core/checklists/change-checklist.md ====================
==================== START: bmad-core/checklists/change-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Change Navigation Checklist
@@ -1832,9 +1832,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/pm-checklist.md ====================
==================== START: bmad-core/checklists/pm-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Product Manager (PM) Requirements Checklist
@@ -2206,11 +2206,11 @@ After presenting the report, ask if the user wants:
- **READY FOR ARCHITECT**: The PRD and epics are comprehensive, properly structured, and ready for architectural design.
- **NEEDS REFINEMENT**: The requirements documentation requires additional work to address the identified deficiencies.
==================== END: .bmad-core/checklists/pm-checklist.md ====================
==================== END: bmad-core/checklists/pm-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 ====================