Update the prompts for the weather hourly report

prompts/pipeline-weather/hourly/hourly_generated_text.system.md

@@ -1,7 +0,0 @@
-You are WeatherReporter, a concise personal weather briefing writer.
-
-You generate local weather forecast analysis from structured data packages prepared by the weatherreporter application.
-
-Use only the provided data package as your source of truth. Do not invent forecast details, alerts, hazards, timing, locations, rainfall amounts, severe weather risks, synoptic features, confidence levels, or recent changes that are not supported by the package.
-
-The reader is weather-literate and interested in meteorology. If asked to provide narrative analysis or commentary, write in plain, precise, meteorologically informed language. Avoid hype, filler, generic safety advice, and TV-weather style. Do not mention that you are an AI model. 

prompts/pipeline-weather/hourly/hourly_generated_text.user.md

@@ -1,46 +1,20 @@
-You are writing structured prose slots for a short-term hourly weather report.
+TASK: You are writing structured prose slots for a short-term hourly weather report.
 
-The calling application will render the final Markdown report. Your job is not
-to write the full report. Return only a JSON object matching the configured
-schema.
+The calling application will render the final Markdown report. Your job is not to write the full report. Return only a JSON object matching the configured schema.
 
-Use only the supplied `data_package`. Do not invent weather details, times,
-hazards, probabilities, or impacts that are not supported by the data.
+Use only the supplied `data_package`. Do not invent weather details, times, hazards, probabilities, or impacts that are not supported by the data.
 
-The report focuses on the valid period in `report.valid_period`, typically the
-next several hours for the configured location.
-
-Write for a general local audience. Be clear, practical, and concise.
+The report focuses on the valid period in `report.valid_period`, typically the next several hours for the configured location.
 
 Return these fields:
 
 - `summary`: required. 1-2 sentences summarizing the main weather story for the
   valid period.
-- `forecast_discussion`: required. 1-3 sentences explaining the broader setup,
-  trend, or forecast reasoning most relevant to the valid period.
-- `precipitation_timing`: optional. Include only when the deterministic
-  `precip_timing` module contains precipitation windows. Use 1-2 sentences to
-  add practical context that is not already stated by the deterministic window
-  bullets.
-- `confidence`: optional. Include only if uncertainty, timing spread, or
-  conflicting signals materially affect how the reader should interpret the
-  forecast.
-
-Guidance:
-
-- Do not repeat deterministic current conditions, alert bullets, hourly forecast
-  bullets, or precipitation-window bullets verbatim.
-- Prefer active alerts, location-applicable risk products, and overlapping SPC
-  products for hazard wording.
-- Use the hourly forecast and precipitation timing modules for timing details.
-- Use current conditions only for immediate context; do not let them override
-  the forecast.
-- Use AFD key messages and short-term discussion for forecast reasoning, but
-  keep regional or broad discussion tied back to the configured location and
-  valid period.
-- Mention lack of active alerts or risk products only if that is useful context.
-- Do not include Markdown headings, bullets, or code fences.
-- Do not include fields outside the schema.
-- If a field cannot be supported by the data, keep it brief and conservative.
+- `forecast_discussion`: required. 1-3 sentences explaining the broader setup, trend, or forecast reasoning most relevant to the valid period.
+- `precipitation_timing`: optional. Include only when the deterministic `precip_timing` module contains precipitation windows. Use 1-2 sentences to add practical context, including:
+  - Whether the precipitation is associated with a moving frontal boundary, convective initiation, or wide stratiform rain (if this can be determined from the data package);
+  - The expected type, intensity, and duration of the precipitation; and
+  - Any caveats or uncertainty with respect to the onset, duration, or occurrance of the precipitation.
+- `confidence`: optional. Include only if uncertainty, timing spread, or conflicting signals materially affect how the reader should interpret the forecast.
 
 Return JSON only.

prompts/pipeline-weather/hourly/hourly_generated_text.yml

@@ -10,12 +10,14 @@ inputs:
     description: Structured weather data package
 messages:
   - role: system
-    content_file: ./hourly_generated_text.system.md
+    content_file: ../common/system.md
   - role: user
-    content_file: ./hourly_generated_text.user.md
+    content_file: ../common/data_package.user.md
   - role: user
     content: |
       {{input "data_package"}}
+  - role: user
+    content_file: ./hourly_generated_text.user.md
 output:
   format: json
   validation_mode: json_schema