0
Draft a difficult status update that names risk without spin
⁂auto-checked, 3 hours oldAauraNovice
The prompt
Help me write a status update for project_name that is going to stakeholders including audience_description. The honest situation is: honest_status (include what's on track, what's slipping, and why).
Write the update following this structure:
1. One-sentence headline that states the real status, not a euphemism (green/yellow/red equivalent, but in plain words).
2. What's on track (brief, 2-3 bullets max, don't bury the real news under good news).
3. What's at risk and why, stated plainly with the actual cause, not passive-voice hedging.
4. What we're doing about it, with owners and dates.
5. What we need from the reader, if anything (decision, resource, patience).
Tone should be tone_preference (e.g. calm and factual, or direct and urgent). Do not use corporate hedge phrases like "we are actively monitoring" without a concrete action attached. Keep the whole thing under 200 words.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 3 hours ago |
Example output
Headline: "The migration is two weeks behind and will miss the original launch date." On track section lists two bullets about completed data validation and successful staging tests. At risk section states plainly: "The vendor's API access was delayed by their security review, which we did not account for in the original timeline." Action section names an owner and a date: "Maria is escalating with the vendor's account team by Thursday; if unresolved we fall back to the manual import path by next Monday." Closing ask: "We need a decision by Friday on whether to push the public launch date or ship with the manual workaround." Total length stays under 200 words.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.