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

prompt title consistency with file names

Browse Source
This commit is contained in:
Brian Madison
2025-04-13 16:58:37 -05:00
parent 71220e51d3
commit 325dec1d9c
9 changed files with 23 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.ai-pm/prompts/0-research-assistant.md
View File

@@ -1,7 +1,8 @@
# External Context Gathering Pre Brainstorming (Optional - Deep Research Prompt)
# Prompt 0: Market Research Assistant BA
persona: Research Assistant (BA)
model: Gemini 2.5 Pro Deep Research (or Similar from OpenAI or others)
model: Gemini 2.5 Pro Deep Research (or Similar from OpenAI, Perplexity or others)
mode: Deep Research
**Note:** Use this prompt _only_ if you need broad external information _before_ defining the specific product idea. The output of this research should be used as context for business analyst prompt. Use the _same specific product concept_ here as you plan to use in the business analyst prompt

3
.ai-pm/prompts/1-business-analyst.md
View File

@@ -1,7 +1,8 @@
# Prompt: Project Brief Generation
# Prompt 1: Business Analyst (BA) Brainstorm Project Brief
persona: Business Analyst (BA)
model: Gemini 2.5 (or other thinking model)
mode: Thinking
**Note:** Use this prompt to brainstorm and define the specific product idea and MVP scope. If you ran Prompt 0 (Deep Research), provide its output as context below.

2
.ai-pm/prompts/2-PM.md
View File

@@ -1,4 +1,4 @@
# Template 1: Generating the Product Requirements Document (PRD)
# Prompt 2: Product/Project Manager (PM) PRD
persona: Technical Product Manager (Tech PM)
model: Gemini 2.5 Pro (or specify preferred model)

19
.ai-pm/prompts/3-PM-UX-Ui.md
View File

@@ -1,16 +1,21 @@
# Template 2: Generating an Optimized V0 Prompt from the PRD
# Prompt 3: Optional V0 Prompt Engineer UI/UX Expert Addendum to PRD
persona: UI/UX Expert & V0 Prompt Engineer
model: Gemini 2.5 Pro (or specify preferred model)
mode: Thinking
This is optional even if building a UI depending on how comfortable you are prompting and having the agent do it all within your IDE or using a specialize site AI to generate your front end scaffolding and then trying to work with it into the workflow stories and architecture. Even if you do not use the output - it can give you a general idea to use as inspiration for the architect.
**Find and fill in all Bracket Pairs before submitting!**
**Note on Other UI AI Generators Prompts:**
This prompt can be used as is potentially, or tweaked a bit, for similar AI UI platforms such as lovable and bolt if choosing to use them to get a jump start on the front end. You could even apply the prompt to all three and see what produces the best output.
## Prompt Follows:
### Role
You are an expert UI/UX specialist and prompt engineer, skilled at translating detailed Product Requirements Documents (PRDs) into highly effective prompts for Vercel's V0 AI UI generation tool. You understand V0's capabilities, its default stack (React, Next.js App Router, Tailwind CSS, shadcn/ui, lucide-react icons), and how to prompt it for specific layouts, components, interactions, styling, and responsiveness based on PRD specifications.
You are an expert UI/UX specialist and prompt engineer, skilled at translating detailed Product Requirements Documents (PRDs) into highly effective prompts for Vercel's V0 AI UI generation tool. You understand V0's capabilities, its default stack (React, Next.js App Router, Tailwind CSS, shadcn/ui, lucide-react icons), and how to prompt it for specific layouts, components, interactions, styling, color palets, similar site inspiration images and responsiveness based on PRD specifications.
### Context
@@ -23,7 +28,7 @@ Assume the target component/page to be generated is: **<Specify the target compo
### Goal
Based on the provided PRD, your task is to generate a single, optimized text prompt suitable for direct use in V0 to create the specified target component/page.
Based on the provided PRD, your task is to generate a single, optimized text prompt suitable for direct use in V0 to create the specified target components/pages needed for the front end of the application.
Your process should be:
@@ -40,12 +45,13 @@ Your process should be:
- Detailed instructions for Key Components & Behavior (referencing PRD states, interactions, using `shadcn/ui` component names where applicable). Specify necessary `lucide-react` icons by name if known.
- Explicit mention of Accessibility requirements (e.g., WCAG 2.1 AA).
- Any relevant Constraints.
- Similar Apps screenshots to give idea of look or to provide further inspiration (or to suggest the user include with the prompt that will be proposed).
- Specification of the Output Format (e.g., single React component file using TypeScript).
### Interaction Style
- Be meticulous in extracting details from the PRD.
- **Crucially, ask targeted clarifying questions** if the PRD is insufficient for generating a high-fidelity V0 component _before_ attempting to generate the final prompt. List the specific information needed.
- **Crucially, ask targeted clarifying questions** if the PRD is insufficient for generating a high-fidelity V0 application and components _before_ attempting to generate the final prompt. List the specific information needed.
- Once all information is clear (either from the PRD or my answers to your questions), generate the final, optimized V0 prompt.
### Output Format
@@ -55,8 +61,3 @@ Generate a single block of text representing the final, optimized prompt ready t
### Task
Analyze the provided PRD for the target component/page: **<Re-specify the target component or page name here>**. Ask clarifying questions if needed. If the PRD is sufficient, generate the optimized V0 prompt.
---
**Note on Lovable AI Prompts:**
Generating prompts for Lovable AI, which often involves full-stack considerations (backend logic, database interactions), typically requires context from the **Architecture Document** in addition to the PRD. Therefore, prompts for Lovable should be generated _after_ the Architecture Document (Phase 3 artifact) is finalized.

4
.ai-pm/prompts/4-Arch-Deep.md
View File

@@ -1,10 +1,10 @@
# Architect Optional Deep Research Prompt (Run Separately Before Main Arch prompt)
# Prompt 4: Optional Architect PRD Updates with Deep Research before generating Architecture Document
persona: Architect (performing research to inform PRD and Core Rules)
model: Gemini 2.5 Pro (or other Deep Research tool)
mode: Deep Research
**Note:** Use this _only_ if the main arch prompt indicates that external research is recommended _before_ generating the Architecture Document. Copy this section into a new prompt instance.
**Note:** Use this _only_ if the main arch prompt indicates that external research is recommended _before_ generating the Architecture Document. Copy this section into a new prompt instance. If you are doing something very niche or out of the ordinary tech stack wise or that there is not a lot of development in github for the models to really give good suggestions, this could be useful. But it is best to stick with well known tech stacks when possible especially if starting with a greenfield and you are not too opinionated.
**Find and fill in all Bracket Pairs before submitting!**

2
.ai-pm/prompts/5-Arch.md
View File

@@ -1,4 +1,4 @@
# Architect Prompt
# Prompt 5: Architect Architecture Document
persona: Architect
model: Gemini 2.5 Pro (or similar thinking capable)

2
.ai-pm/prompts/6-PO.md
View File

@@ -1,4 +1,4 @@
# Product Owner Prompt
# Prompt 6: Product Owner Epic Stories List
persona: Expert Agile Product Owner specializing in decomposing complex requirements into logically sequenced Epics and User Stories based on value and technical/UI/setup dependencies.
model: Gemini 2.5 Pro (or similar advanced LLM)

2
.ai-pm/prompts/7-SM.md
View File

@@ -1,3 +1,5 @@
# Prompt 7: Senior Engineer Scrum Master Detailed Stories
persona: Technical Scrum Master / Senior Engineer
model: Gemini 2.5 Pro (or similar thinking model)
mode: Thinking

2
.ai-pm/prompts/8-SM-IDE.md
View File

@@ -1,4 +1,4 @@
# Prompt to Generate the Granular Stories
# Prompt 8: Optional IDE Generate the Granular Stories from a single file of stories
Depending on which LLM and IDE you are using, you might want to split up your stories file if it is too large for the LLM to handle and you are using a lower context model to keep cost down or remain under free usage tiers. This is not a difficult task for LLM and does not require thought or deep research whatsoever.