Add docs_writer model.

spicepod.yaml

@@ -18,7 +18,7 @@ datasets:
       github_client_id: ${secrets:GITHUB_CLIENT_ID}
       github_private_key: ${secrets:GITHUB_PRIVATE_KEY}
       github_installation_id: ${secrets:GITHUB_INSTALLATION_ID}
-      include: "website/docs/**/*.md"
+      include: 'website/docs/**/*.md'
     acceleration:
       enabled: true
       refresh_check_interval: 4h
@@ -47,7 +47,7 @@ datasets:
       github_client_id: ${secrets:GITHUB_CLIENT_ID}
       github_private_key: ${secrets:GITHUB_PRIVATE_KEY}
       github_installation_id: ${secrets:GITHUB_INSTALLATION_ID}
-      include: "**/*.md"
+      include: '**/*.md'
     acceleration:
       enabled: true
       refresh_check_interval: 4h
@@ -77,7 +77,7 @@ datasets:
       github_client_id: ${secrets:GITHUB_CLIENT_ID}
       github_private_key: ${secrets:GITHUB_PRIVATE_KEY}
       github_installation_id: ${secrets:GITHUB_INSTALLATION_ID}
-      include: "content/posts/**/*.md"
+      include: 'content/posts/**/*.md'
     acceleration:
       enabled: true
       refresh_check_interval: 4h
@@ -115,7 +115,7 @@ embeddings:
       openai_api_key: ${ secrets:OPENAI_API_KEY }
 
 models:
-  - name: openai
+  - name: assistant
     from: openai:gpt-4o
     params:
       tools: auto
@@ -147,3 +147,30 @@ models:
 
         General guidelines:
           1. If a query could be answered by either tool, prefer SQL for more precise, quantitative answers.
+
+  - name: docs_writer
+    from: openai:gpt-4o
+    params:
+      tools: auto
+      openai_api_key: ${secrets:OPENAI_API_KEY}
+      system_prompt: |
+        You are an AI assistant helping contributors to the Spice.ai open-source project write documentation, release notes, and blog posts.
+
+        **Write clearly, concisely, and precisely for a developer audience.**
+        Use objective third-person tense. Do not use “I” or “we” unless explicitly quoting or summarizing subjective viewpoints. Avoid vague qualifiers and revise text to maximize clarity, structure, and factual accuracy. Every sentence should reflect critical thinking and organized reasoning.
+
+        **Be specific. Prioritize detail without being verbose.**
+        Use plain, direct language. Avoid jargon, exaggeration, and promotional tone.
+
+        **Do not use the following words or their variants:**
+        - delve
+        - seamlessly
+        - empower / empowering
+        - supercharge
+        - countless
+        - enhance / enhancing
+        - allow / allowing (Use “helps” or “enables” when appropriate.)
+
+        **Always provide citations and references with links when applicable.**
+
+        Your output should read like a well-edited technical paper: factual, sharp, and to the point.