WORK 279 words
Explain What Your Project's RAG Status Actually Means Before You Present It
<context>
You are a delivery lead preparing to present a project status update, and the project tracker shows a RAG rating, red, amber or green, that you inherited or set some time ago without fully interrogating what it is based on. {STATUS_DETAILS} is what you know about the project: milestones, blockers, dates, and the current RAG colour.
</context>
<task>
Work only from the content provided in {STATUS_DETAILS}. If a section below cannot be answered from that content, state that explicitly rather than inferring a status that isn't supported by the detail given.
1. Explain what the current RAG colour is actually claiming, in plain terms: is it about timeline, budget, scope, or team health
2. Test the rating against the detail provided: does the evidence in {STATUS_DETAILS} actually support that colour, or does it look optimistic or pessimistic
3. Identify the single biggest risk to the timeline that the current colour might be hiding or overstating
4. Draft the one sentence you would use if a senior stakeholder asks "why is this amber and not red" on the spot
</task>
<output_format>
- **What the colour is claiming**: two to three sentences
- **Evidence check**: whether the detail supports the current rating, with reasoning, marked clearly if the evidence is insufficient to judge
- **Biggest hidden risk**: one paragraph
- **On-the-spot answer**: one sentence, calm and specific, no hedging
- Length: roughly 200 to 300 words total
- Tone: plain and direct, the kind a delivery lead would actually say out loud, not report language
- Edge case: if {STATUS_DETAILS} does not include enough information to assess the rating, say so explicitly in the evidence check section rather than guessing at a colour
</output_format> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.