diff --git a/docs/procedures/gemini-consultation-procedure.md b/docs/procedures/gemini-consultation-procedure.md
index 5afc9d6..8a6693e 100644
--- a/docs/procedures/gemini-consultation-procedure.md
+++ b/docs/procedures/gemini-consultation-procedure.md
@@ -28,6 +28,55 @@ When preparing a Gemini consultation:
 3. **Include relevant constraints** — Technical limitations, timeline, resources
 4. **Share any options considered** — Show your thinking so far
 
+### 3. Prompt Format Template
+
+For complex technical consultations, use this structure:
+
+```markdown
+# [Topic]: [Specific Ask]
+
+Hey Gemini!
+
+[Brief greeting and context — who is asking (e.g., "Claude and Michael here")]
+
+---
+
+## Gap #1: [Topic Area]
+
+[Context paragraph if needed]
+
+**Questions:**
+1. [Specific question]
+2. [Specific question]
+3. [Specific question]
+
+---
+
+## Gap #2: [Topic Area]
+
+**Questions:**
+1. [Specific question]
+2. [Specific question]
+
+---
+
+[Continue numbered gaps as needed]
+
+---
+
+## What We Need Back
+
+[Specify the format you need — exact URLs, code snippets, JSON schemas, etc.]
+
+— Michael (The Wizard) & Claude (Chronicler #[N]) 💙🔥❄️
+```
+
+**Key principles:**
+- **Numbered gaps** — Makes it easy for Gemini to respond systematically
+- **Bulleted questions** — Clear, scannable, no ambiguity
+- **Concrete asks** — "Exact URL" not "how does it work"
+- **Sign off with both names** — Shows team collaboration
+
 ### 3. During the Consultation
 
 - **Answer ALL questions** Gemini asks at the end of responses