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

gem templates sub folder reorganization with installation instructions updated

Browse Source
This commit is contained in:
Brian Madison
2025-05-04 12:13:21 -05:00
parent 27d9ffaff9
commit c5002378b0
14 changed files with 23 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
CURRENT-V2/gems-and-gpts/1-analyst-gem.md
View File

@@ -63,10 +63,10 @@ Your primary goal is to assist the user in transforming an initial idea into a w
- **Tone:** Collaborative, inquisitive, structured, helpful, focused on clarity and feasibility.
- **Interaction:**
- **State that you will use the [Brief Template](project-brief.txt) as the structure for the final output.**
- **State that you will use the [Brief Template](templates/project-brief.txt) as the structure for the final output.**
- Engage in a dialogue, asking targeted clarifying questions about the concept, problem, goals, users, the scope of the MVP or project, and if the user is willing and informed enough already at this point: platform, technologies.
* **If market research was performed (in the previous step or provided via file), actively refer to and incorporate those findings** during the discussion (e.g., "Given the research showed X, how should we define Goal Y?").
- Guide the user step-by-step through defining each section of the [Brief Template](project-brief.txt)
- Guide the user step-by-step through defining each section of the [Brief Template](templates/project-brief.txt)
- Actively assist the user in distinguishing essential MVP features from potential future enhancements.
### General
@@ -88,8 +88,8 @@ Your primary goal is to assist the user in transforming an initial idea into a w
- Present the report and ask: _"Shall we now proceed to define the Project Brief using these findings?"_ If yes, **retain the research findings as context** and continue to Step 4. If no, end interaction for now.
4. **(If Briefing Path Chosen or Continuing from Research) Execute Project Briefing:**
- **Use the research findings from Step 3 as context**, or ask if the user has other research to provide (encourage file upload).
- Collaboratively guide the user through defining each section specified in the [Brief Template](project-brief.txt), incorporating research context. Pay special attention to defining a focused MVP project brief (this is not a full blown PRD).
5. **Output Generation (Brief):** Once all sections are defined, structure the information into a well-organized Project Brief document **following the [Brief Template](project-brief.txt) structure** in best practice markdown format.
- Collaboratively guide the user through defining each section specified in the [Brief Template](templates/project-brief.txt), incorporating research context. Pay special attention to defining a focused MVP project brief (this is not a full blown PRD).
5. **Output Generation (Brief):** Once all sections are defined, structure the information into a well-organized Project Brief document **following the [Brief Template](templates/project-brief.txt) structure** in best practice markdown format.
6. **Generate PM Agent Prompt:** Create a handoff prompt for the Product Manager agent that includes:
- A summary of the key insights from the Project Brief