Prompt Important Note added to all prompt files

.ai-pm/prompts/0-research-assistant.md

@@ -5,6 +5,8 @@ model: Gemini 2.5 Pro Deep Research (or Similar from OpenAI or others)
 
 **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
 
+**Find and fill in all Bracket Pairs before submitting!**
+
 ## Prompt Follows:
 
 ### Role

.ai-pm/prompts/1-business-analyst.md

@@ -5,6 +5,8 @@ model: Gemini 2.5 (or other thinking model)
 
 **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.
 
+**Find and fill in all Bracket Pairs before submitting!**
+
 ## Prompt Follows:
 
 ### Role

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

@@ -4,6 +4,8 @@ persona: Technical Product Manager (Tech PM)
 model: Gemini 2.5 Pro (or specify preferred model)
 mode: Thinking
 
+**Find and fill in all Bracket Pairs before submitting!**
+
 ## Prompt follows:
 
 ### Role

.ai-pm/prompts/3-PM-UX-Ui.md

@@ -4,6 +4,8 @@ persona: UI/UX Expert & V0 Prompt Engineer
 model: Gemini 2.5 Pro (or specify preferred model)
 mode: Thinking
 
+**Find and fill in all Bracket Pairs before submitting!**
+
 ## Prompt Follows:
 
 ### Role

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

@@ -6,6 +6,8 @@ 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.
 
+**Find and fill in all Bracket Pairs before submitting!**
+
 ## Prompt Follows:
 
 ### Role

.ai-pm/prompts/5-Arch.md

@@ -4,6 +4,8 @@ persona: Architect
 model: Gemini 2.5 Pro (or similar thinking capable)
 mode: Thinking
 
+**Find and fill in all Bracket Pairs before submitting!**
+
 ## Prompt Follows:
 
 ### Role
@@ -16,9 +18,13 @@ The primary input for this task is the finalized Product Requirements Document (
 
 **Product Requirements Document (PRD):**
 """
-<Paste the complete finalized PRD content here. Ensure it includes detailed Functional Requirements, NFRs, and UI/UX Specifications.>
+<Paste the complete finalized PRD content here or reference it as attached. Ensure it includes detailed Functional Requirements, NFRs, and UI/UX Specifications.>
 """
 
+<ExpertModeConstraints>
+Delete this block unless you are sure you want to provide any specific constraints beyond the PRD. For example you may know already that you want to have a SPA + microservices, EDA, specific cloud technologies or providers, existing systems you need to interact with and provide more detail for than what is in the PRD etc...
+</ExpertModeConstraints>
+
 ### Goal
 
 Your goal is to collaboratively design and document an opinionated Architecture Document based _only_ on the provided PRD. The document must comprehensively address the following sections, providing specific and actionable details:

.ai-pm/prompts/6-PO.md

@@ -1,11 +1,11 @@
 # Product Owner Prompt
 
 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)
-
 mode: Standard Reasoning / Thinking Mode
 
+**Find and fill in all Bracket Pairs before submitting!**
+
 ## Prompt Follows:
 
 You are an Expert Agile Product Owner. Your task is to create a logically ordered backlog of Epics and User Stories for the MVP of `<Project Name>`, based on the provided Product Requirements Document (PRD) and Architecture Document.

.ai-pm/prompts/7-SM.md

@@ -2,6 +2,8 @@ persona: Technical Scrum Master / Senior Engineer
 model: Gemini 2.5 Pro (or similar thinking model)
 mode: Thinking
 
+**Find and fill in all Bracket Pairs before submitting!**
+
 ## Prompt Follows:
 
 ### Role

.ai-pm/prompts/8-SM-IDE.md

@@ -1,5 +1,9 @@
 # Prompt to Generate the Granular 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.
+
+## Prompt Follows for IDE Agent (Such as Claude 3.5 or 3.7):
+
 Review ./.ai-pm/stories.md and without changing ANY content, generate all of the
 individual story files to add to ./ai-pm/1-ToDo/. Each story in the file has a title, which will drive the file name. And each story has a separator between each story block. The content for each story block will be the only contents within each file you will create.