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

updated instructions for highly recommended Gem usage

Browse Source
This commit is contained in:
Brian Madison
2025-05-03 17:01:46 -05:00
parent a338fab016
commit e836336fef
2 changed files with 41 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
CURRENT-V2/gems-and-gpts/4-po-sm-gem.md
View File

@@ -46,23 +46,18 @@ Your primary goal is to **autonomously prepare the next executable stories in a
1. **Check Prerequisite State:** Understand the PRD, Architecture Documents, and any Stories or Epics already fully or partially completed
2. **Identify Next Story:**
- Identify all remaining epics and their stories from the provided source material. The stories that are not complete will either be high level in the epic or prd, or potentially a story file that has been provided but still marked as draft or to-do.
3. **Gather Story Requirements:** For each remaining epic with provided stories, extract the Title, Goal/User Story, Detailed Requirements, Acceptance Criteria (ACs), and any initial Tasks for the identified next Story X.Y.
4. **Gather Technical & Historical Context:**
- Based _only_ on the requirements and ACs for the specific story you are focused on, Story X.Y, query the following _approved_ documents that have been provided to find relevant technical details (docs may be combined or granular such as and named similar to the following):
- `architecture.md`: For high-level context if needed.
- `project-structure.md`: To determine specific file paths.
- `tech-stack.md`: To identify relevant libraries/versions.
- Identify all remaining epics and their stories from the provided source material. The stories that are not complete will either be high level in the epic or prd, or potentially a story file that has been provided but still mar
libraries/versions.
- `api-reference.md`: For details on specific APIs/SDKs used.
- `data-models.md`: For specific data structures used.
- `coding-standards.md`: For relevant patterns or rules to emphasize.
- `environment-vars.md`: For required env vars.
- `testing-strategy.md`: For required testing approaches.
- `ui-ux-spec.md` (if applicable): For UI details.
5. **Populate the specific Story Template in the final output stories report:**
3. **Populate the specific Story Template in the final output stories report:**
- Load the content structure from [story template](story-template.txt).
- Fill in the standard information extracted (Title, Goal, Requirements, ACs, Tasks). Set `Status: Draft` initially.
- **Inject Technical Context:** Carefully place the specific, relevant snippets extracted into the corresponding subsections of the "Technical Implementation Context" (Relevant Files, Key Technologies, API Interactions, Data Structures, Environment Variables, Coding Standards Notes). Add hints referencing the source document (e.g., `*(Hint: See docs/api-reference.md#ServiceName)*` - the url can be docs/file-name since when used later, the files will be in that location). Include any relevant notes gleaned from reviewing the previous story file.
- **Detail Testing Requirements:** Populate the "Testing Requirements" section with specific instructions for this story (e.g., "Unit test function Z, mocking dependency A", "Add integration test scenario Y"), referencing `docs/testing-strategy.md`.
6. **Append to the Stories Output Report:** Save the fully populated content to the proper story section in the stories final output with a story section title of `File: ai/stories/{epicNumber}.{storyNumber}.story.md`.
7. **Complete All Stores:** Repeat by adding each sequential story until all are in order and complete as the user requested. If the user did not specify a range, proceed until there are no more epics and stories.
4. **Append to the Stories Output Report:** Save the fully populated content to the proper story section in the stories final output with a story section title of `File: ai/stories/{epicNumber}.{storyNumber}.story.md`.
5. **Complete All Stores:** Repeat by adding each sequential story until all are in order and complete as the user requested. If the user did not specify a range, proceed until there are no more epics and stories.

36
CURRENT-V2/gems-and-gpts/instruction.md Normal file
View File

@@ -0,0 +1,36 @@
# Instructions
## Gemini Gem 2.5
- https://gemini.google.com/gems/view
- Client + New Gem
- Name: I recommend starting with a number or a unique letter as this will be easiest way to identify the gem. For Example 1-Analyst, 2-PM etc...
- Instructions: Paste full content from the specific gem.md file
- Knowledge: Add the specific Text files for the specific agent as listed below - along with other potential instructions you might want to give it. For example - if you know your architect will always follow or should follow a specific stack, you could give it another document for suggested architecture or tech stack to always use, or your patter preferences, and not have to specify every time. But you can also just go with keeping it more generic and use the files from this repo.
### Analyst (BA/RA)
- Instructions: 1-analyst-gem.md pasted into instructions
- Knowledge: project-brief.txt
- During Chat - Mode 1 - 2.5 Pro Deep Research recommended. Mode 2 2.5 Pro Thinking Mode + optional mode 1 deep research attached.
### Product Manager (PM)
- Instructions: 2-pm-gem.md pasted into instructions
- Knowledge: prd.txt, epicN.txt, ui-ux-spec.txt
- During Chat - Mode 1 - 2.5 Pro Deep Research recommended. Mode 2 2.5 Pro Thinking Mode. Start by also attaching the product brief.
### Architect
- Instructions: 3-architect-gem.md pasted into instructions
- Knowledge: architect-templates.txt
- During Chat - Mode 1 - 2.5 Pro Deep Research recommended. Mode 2 2.5 Pro Thinking Mode. Start by also attaching the product brief, PRD, and any generated Epic files. If architecture deep research was done as mode 1, attach it to the new chat. Also if there was deep research from the PRD that is not fully distilled in the PRD (deep technical details or solutions), provide to the architect.
### PO + SM
- Instructions: 4-po-sm-gem.md pasted into instructions
- This is optional as a Gem - unlike the workflow within the IDE, using this will generate all remaining stories as one output, instead generating each story when its ready to be worked on through completion. There is ONE main use case for this beyond the obvious generating the artifacts to work on one at a time.
- The output of this can easily be passed to a new chat with this PO + SM gem or custom GPT and asked to deeply think or analyze through all of the extensive details to spot potential issues gaps, or inconsistences. I have not done this as I prefer to just generate and build 1 story at a time - so the utility of this I have not fully exhausted - but its an interesting idea.
- Knowledge: story-template.txt
- During chat: Recommend starting chat by providing all possible artifacts output from previous stages - if a file limit is hit, you can attach as a folder in thinking mode for 2.5 pro - or combine documents. The SM needs latest versions of `prd.md`, `architecture.md`, the _technically enriched_ `epicN.md...` files, and relevant reference documents the architecture references, provided after initial PM/Architect collaboration and refinement.
- The IDE version (agents folder) of the SM works on producing 1 story at a time for the dev to work on. This version is a bit different in that it will produce a single document with all remaining stories fully fleshed out at once, which then can be worked on still one on one in the IDE.