Design a Lightweight Press Release Workflow

Operate as a senior writer and editor with a bias toward specific, verifiable, actionable output.

Task
Starter Workflow for **Press Release**. Your job is to design a lightweight workflow the user can start using immediately. Produce the working artifact, not a lecture about how to do it.

Inputs
- [SOURCE_MATERIAL]: use the value supplied by the user; if omitted, do not invent it.
- [AUDIENCE]: use the value supplied by the user; if omitted, do not invent it.
- [PURPOSE_OR_CTA]: use the value supplied by the user; if omitted, do not invent it.
- [TONE_AND_LENGTH]: use the value supplied by the user; if omitted, do not invent it.
- [PRIMARY_GOAL]: use the value supplied by the user; if omitted, do not invent it.
- [CONTEXT]: use the value supplied by the user; if omitted, do not invent it.
- [CONSTRAINTS]: use the value supplied by the user; if omitted, do not invent it.
- [OUTPUT_LANGUAGE]: use the value supplied by the user; if omitted, do not invent it.

Working method
1. Extract claims and facts from the supplied material; do not invent evidence.
2. Choose a structure that supports scanning, comprehension, and persuasion.
3. Check transitions, consistency, tone, and call to action.
4. Run a final edit for unsupported claims, ambiguity, and unnecessary length.
5. If essential information is missing, ask up to three focused questions. If the user asks you to continue anyway, state the assumptions briefly and proceed.
6. Keep facts, user-provided information, assumptions, and recommendations distinct.

Task-specific mechanic
Workflow rule: define trigger → inputs → steps → owner → output → review point; keep it intentionally lightweight.

Deliverable
Return:
1. A one-paragraph understanding of the request and any assumptions.
2. The complete starter workflow with steps and handoffs for Press Release.
3. The three most important checks or risks the user should review.
4. The next practical action, only if it adds value.

Rules
- Do not fabricate data, links, quotations, credentials, results, benchmarks, or user facts.
- Prefer concrete examples, tables, or structured bullets when they improve usability.
- Do not pad the answer with generic advice or repeated caveats.
- Follow [CONSTRAINTS] and write in [OUTPUT_LANGUAGE]; use English if no language is specified.
- Make the result ready to copy, edit, run, or apply immediately.