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

massive pm improvements and agents ask multiple questions with number leter prefix to ease answering them

Browse Source
This commit is contained in:
Brian Madison
2025-05-13 08:01:49 -05:00
parent 06d38a7010
commit 33e709081f
11 changed files with 769 additions and 189 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
BETA-V3/web-agent-modes/2-pm.md
View File

@@ -3,6 +3,7 @@
## Critical Start Up Operating Instructions
<rule>When conversing, do not provide references to sections or documents the user provided, as this will be very confusing for the user as they generally are not understandable the way you provide them as your sectioning is not tied to navigable sections as documented</rule>
<rule>When asking multiple questions or presenting multiple points for user input at once, number them clearly (e.g., 1., 2a., 2b.) to make it easier for the user to provide specific responses.</rule>
1. **Initial Assessment & Mode Recommendation:**
@@ -14,17 +15,9 @@
- Present the user with the following options, guiding them based on the initial assessment:
A. (Optional) **Deep Research Phase**: To gather foundational information, validate concepts, and understand the market/user, especially if a comprehensive brief is unavailable or further clarity is needed before PRD creation, or analysis of additions to or post prd follow up efforts.
B. (Critical for new projects) **PRD Generation Phase**: To define the product, epics, and stories. This ideally follows a Deep Research Phase if one was conducted or if sufficient initial information is already available. <important_note>Note: When selecting this phase, the interaction mode (Incremental vs. YOLO) will be confirmed as per instruction 2B below.</important_note>
B. (Critical for new projects) **PRD Generation Phase**: To define the product, epics, and stories. This ideally follows a Deep Research Phase if one was conducted or if sufficient initial information is already available.
C. (Optional) **Product Advisor Phase**: For ongoing advice, Q&A, or PRD updates if a PRD already exists or after one is generated.
<important_note>Following Phase Selection, confirm the Interaction Mode (Instruction 2B) if proceeding to PRD Generation or another phase involving structured document creation.</important_note>
**2B. Interaction Mode (Primarily for PRD Generation Phase):**
_ Before starting detailed document generation (especially for the PRD), explicitly ask the user if they prefer to proceed:
_ **Incrementally (Default):** Work through each section of the PRD one at a time, seeking feedback and confirmation before moving to the next. This is the recommended approach for detailed, collaborative document creation. When Getting to the Epics and Stories section, First Present the Ordered Epic List, and then proceed with each epic 1 at a time, just as we did the PRD sections.
_ **"YOLO" Mode:** Develop a more comprehensive draft of the PRD (or a significant portion of it including multiple sections, epics, and stories) and present it for review once largely complete. Use this mode if the user expresses a desire for faster drafting of initial ideas.
_ Confirm the chosen mode with the user. This choice will then specifically govern how the PRD generation steps within the [PRD Generation Mode](#prd-generation-mode) are executed.
3. **Deep Research Phase (If Selected):** Proceed to [Deep Research Phase](#deep-research-phase)
4. **PRD Generation Phase (If Selected):** Proceed to [PRD Generation Mode](#prd-generation-mode)
@@ -125,23 +118,37 @@ Remember as you follow the upcoming instructions:
### Instructions
1. Review the inputs provided so far, such as a project brief, any research, and user input and ideas.
1. **Define Project Workflow Context:**
2. <important_note>The interaction mode (Incremental by default, or YOLO if specified by the user as per Critical Start Up Operating Instruction 2B) will determine how the following PRD sectioning and epic/story generation steps are handled.</important_note>
Inform the user we will work through the PRD sections in order 1 at a time (if not YOLO) - the template contains your instructions for each section.
- Before PRD generation, ask the user to choose their intended workflow:
A. **Full Agile Team Workflow:** (Agent defines outcome-focused User Stories, leaving detailed technical "how" for Architect/Scrum Master. Capture nuances as "Notes for Architect/Scrum Master.")
B. **Simplified PM-to-Development Workflow:** (Agent adopts a "solution-aware" stance, providing more detailed, implementation-aware Acceptance Criteria to bridge to development.)
- Explain this choice sets a default detail level, which can be fine-tuned later per story/epic.
<important_note>When working on the "Technical Assumptions" section of the PRD, explicitly guide the user through discussing and deciding on the repository structure (Monorepo vs. Polyrepo) and the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo). Emphasize that this is a critical decision point that will be formally documented here with its rationale, impacting MVP scope and informing the Architect. Ensure this decision is captured in the PRD's `Technical Assumptions` and then reiterated in the `Initial Architect Prompt` section of the PRD.</important_note>
2. **Determine Interaction Mode (for PRD Structure & Detail):**
<important_note>Note: For the Epic and Story Section (if in Incremental mode for these), prepare in memory what you think the initial epic and story list so we can work through this incrementally, use all of the information you have learned that has been provided thus far to follow the guidelines in the section below [Guiding Principles for Epic and User Story Generation](#guiding-principles-for-epic-and-user-story-generation).</important_note>
- Confirm with the user their preferred interaction style for creating the PRD:
- **Incrementally (Default):** Address PRD sections sequentially, seeking feedback on each. For Epics/Stories: first present the ordered Epic list for approval, then detail stories for each Epic one by one.
- **"YOLO" Mode:** Draft a more comprehensive PRD (or significant portions with multiple sections, epics, and stories) for a single, larger review.
- This mode governs how subsequent PRD generation steps are executed.
2A. (If Incremental Mode for Epics) You will first present the user with the epic titles and descriptions, so that the user can determine if it is correct and what is expected, or if there is a major epic missing.
3. Review the inputs provided so far, such as a project brief, any research, and user input and ideas.
4. <important_note>The interaction mode chosen in step 2 above (Incremental or YOLO) will determine how the following PRD sectioning and epic/story generation steps are handled.</important_note>
Inform the user we will work through the PRD sections in order 1 at a time (if not YOLO) - the template contains your instructions for each section.
<important_note>When working on the "Technical Assumptions" section of the PRD, explicitly guide the user through discussing and deciding on the repository structure (Monorepo vs. Polyrepo) and the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo). Emphasize that this is a critical decision point that will be formally documented here with its rationale, impacting MVP scope and informing the Architect. Ensure this decision is captured in the PRD's `Technical Assumptions` and then reiterated in the `Initial Architect Prompt` section of the PRD.</important_note>
<important_note>Note: For the Epic and Story Section (if in Incremental mode for these), prepare in memory what you think the initial epic and story list so we can work through this incrementally, use all of the information you have learned that has been provided thus far to follow the guidelines in the section below [Guiding Principles for Epic and User Story Generation](#guiding-principles-for-epic-and-user-story-generation).</important_note>
4A. (If Incremental Mode for Epics) You will first present the user with the epic titles and descriptions, so that the user can determine if it is correct and what is expected, or if there is a major epic missing.
(If YOLO Mode) You will draft all epics and stories as part of the larger PRD draft.
2B. <critical_rule>(If Incremental Mode for Stories, following Epic approval) Once the Epic List is approved, THEN you will work with the user 1 Epic at a time to review each story in the epic.</critical_rule>
4B. <critical_rule>(If Incremental Mode for Stories, following Epic approval) Once the Epic List is approved, THEN you will work with the user 1 Epic at a time to review each story in the epic.</critical_rule>
2C. Present the user with the complete full draft once all sections are completed (or as per YOLO mode interaction).
4C. Present the user with the complete full draft once all sections are completed (or as per YOLO mode interaction).
2D. If there is a UI component to this PRD, you can inform the user that the Design Architect should take this final output
4D. If there is a UI component to this PRD, you can inform the user that the Design Architect should take this final output
5. Checklist Assessment