Prompts To Pro RSS: turn an editorial brief into feed-ready records

Describe the draft you need

Write the brief around a reader and a decision. “Summarize this announcement for maintainers deciding whether to upgrade” gives the draft a purpose. Supply the announcement text, its source label, and the relevant product version. Ask for a headline, a concise summary, and any unresolved questions. Avoid requesting a finished feed as the first output: that combines editorial judgment with metadata and XML construction.

Define what each field means. A headline should identify the change; the summary should describe its practical effect; unresolved questions should expose missing evidence. Specify that unsupported dates, measurements, and claims must remain absent. This gives a reviewer concrete acceptance criteria.

Keep identity with the application

The publishing application should assign the internal record ID, canonical page URL, permanent feed identifier, and approved publication time. These values describe an actual publication event. A writing model should not invent them because an example happened to include a plausible URL or date.

Task: Draft one update for website maintainers.
Evidence: S01, supplied announcement text.
Return: headline, summary, source_ids, unresolved.
Use only supplied evidence. Leave unknown facts unresolved.
Do not assign publication metadata.

Store the response as a candidate beside the source material. Reject unknown field names or source labels when the agreed record format requires a fixed structure. Read the summary against the source even when its structure passes validation.

Publish through a repeatable sequence

1. Approve the text and resolve questions that affect its meaning.
2. Create the public article page and confirm its canonical address.
3. Serialize approved fields with an XML library.
4. Check the resulting feed with a parser and compare its entry to the published page.

The RSS specification describes the channel and item elements your serializer must produce. Keep that mapping in application code so identical records receive consistent escaping and element structure.

After a correction, update the existing record under the same identifier instead of asking a prompt to recreate the publication from scratch. The feed maker workflow guide explains how a stable source record can serve both the page and its feed entry. That shared record is the durable output of the process.