What it does
You paste in this week’s notes. It gives back a RAG table: one row per workstream with a status in words, a one-line reason and an ask with an owner, plus an overall rating and a list of questions.
This is the short version of the /status playbook. It’s one prompt, one paste, one table. It doesn’t compare against last week’s report, doesn’t write the asks section or the “what changed” bullets, and doesn’t need your RAG definitions. Use it when you want a quick read on where things stand, or a first pass at the table before a sync.
When to use it
| Use it when | Skip it when |
|---|---|
| You need a quick RAG table for a sync or a hallway update | You’re writing the full weekly report: use the /status playbook |
| Your notes cover every workstream, even briefly | You haven’t heard from half the leads this week |
| The notes are safe to paste into your company’s approved AI tool | The notes hold anything your AI policy keeps out |
The prompt
You are helping a technical program manager turn this week's notes into a RAG status table.
Use only the notes I paste below. Do not invent dates, names, numbers or progress. If something you need is missing, write [MISSING: what is needed] in its place.
Ratings:
- Green: on track for the next milestone date.
- Amber: the date holds only if a named problem is fixed soon.
- Red: the date will slip without a decision or help from outside the team.
Rate against the date, not the effort. If the notes are unclear, pick the less optimistic rating and say why.
Output:
1. Overall: one rating and one sentence on why. One Red that blocks launch makes the overall at least Amber.
2. A table with columns Workstream, Status, Why, Ask. Write the status as a word. Every Amber or Red row needs an ask with an owner role and a date.
3. Questions for me: anything you could not rate, or that the notes contradict.
Keep it short. No introduction, no summary at the end.
NOTES:
[paste]Setup notes. Paste the prompt and your notes in one message. Notes can be rough: bullet points, chat excerpts and half sentences all work. If you run it every week, save everything above NOTES: as a saved prompt, project instruction or text file so you only paste the notes.
A filled example
From the running example, Lantern: five teams moving a support assistant onto in-house inference. The TPM pasted these notes before the Thursday sync.
| Source | What it says |
|---|---|
| Data lead | Index rebuild running about half the planned speed. Trying a batch-size fix. |
| Cutover sync | Shadow run 1 done; two runbook steps were out of order and are fixed. |
| Security thread | No reviewer yet. Nobody owns scheduling it. The review gates customer traffic. |
| Plan review | All five teams signed off on the migration plan. |
And the table it gave back:
| Workstream | Status | Why | Ask |
|---|---|---|---|
| Migration plan | Green | Signed off by all five teams | None |
| Index rebuild | Amber | Rebuild at about half the planned speed; fix in progress | Data lead to confirm the fix worked by [MISSING: date] |
| Cutover runbook | Green | Shadow run 1 done; two step-order issues fixed | None |
| Security & privacy review | Red | No reviewer and no owner for scheduling; gates customer traffic | Security lead to name a reviewer by [MISSING: date] |
It rated the program Overall: Amber and asked when shadow run 2 is planned, since the notes didn’t say. Fair question: Green on the runbook means little if the next shadow run has no date.
What to verify
| Check | Item |
|---|---|
| Every rating matches what you heardYou were in the meetings. Overrule anything that surprises you. | |
| Every Amber and Red row has an owner and a dateFill each [MISSING] or drop the ask. | |
| Nothing was inventedCheck each name, number and date against your notes. | |
| Missing workstreams are missing on purposeA workstream with no notes doesn’t show up. Silence isn’t Green. | |
| Questions answeredEach question is a gap in your notes; close it before the sync. |