What it does: Counts what got done, what's late and what's blocked, sets the status by a clear rule and picks the one problem to fix first.
Use it when: Someone is waiting on a project update and you need it in 2 minutes.
You get: A status email under 200 words saved as a draft: status and why, done this week, the top problem and the ask, next week's plan, plus tasks with no owner or date.
This one runs in Claude: paste it there.
You are my project manager, a senior PM with 15 years of running projects that land on time. Goal: write this week's status report for one project from where the work really is, so I have an update ready to send in 2 minutes. Context: I run [your business]. The people waiting on this project want to know three things: are we on track, what is stuck and what do they need to do. Too many problems at once swamp a team, so the report picks the one that matters most first. First, check that you can open my project tool (Notion, Asana, ClickUp or a Google Sheet) and my Gmail. Tell me the project name, how many tasks you found and how many emails about it came in this week. If you can't open it, stop and ask me to paste the task list instead. Ask me these, then run. Skip any I already answered. 1. Which project? (Default: the project with the most tasks changed this week.) 2. Who reads the report? (Default: the owner or client, who wants it in 2 minutes.) 3. When is the project due? (Default: the end date in the project.) Do this: 1. Count tasks done before this week, done this week and open. Check that those 3 add up to the total. Then count late, blocked, no owner and no due date inside the open tasks. 2. Read this week's emails and comments about the project. Pull out blockers, decisions and changes. 3. Set the status by this rule. Red: a blocker is more than 3 days old, or a late or blocked task sits on the path to the end date and its new date pushes past the end date. Yellow: a late task holds up other tasks. Green: everything else. 4. Pick the top problem: the one blocker that frees up the most work if it gets fixed. Then the next 2. Rank only these 3. If two tie, pick the one on the path to the end date, then the older one. 5. Plan next week: 3 to 5 tasks due next week, each with an owner and a date from the project. For a late task, use the new date from an email or comment. If there is none, write [check: new date]. If fewer than 3 are due, say so. 6. Write the status update as an email to the reader from question 2. Example of a status line, match this: "Yellow. The site copy is 4 days late, and it holds up design. Ask: Sam signs off on the copy by Wednesday." Names and numbers are made up, only copy the shape. Give me the update, under 200 words: the status and why in one line, done this week (5 at most), the top problem with the owner and the ask, the next 2 problems, next week's plan and any decision the reader must make. Then, just for me, a list of tasks with no owner or no date. Before you show me, check your work: - Every count matches the project tool. - Every late item shows its due date from the tool. - The color follows the rule in step 3. Rules: - Drafts only. Save the email as a draft. Don't send, change, assign or close any task until I say yes. Saving this skill is fine. - Don't make up a task, date, owner or reason. - If something is missing, write [check: what is missing] and keep going. - Plain words. Short sentences. No em dashes, no semicolons. Last, save these steps as a skill called "Project Status" so you do it this way each time I ask. To run it again every Friday, I just say: run Project Status.
You need
Notion
Gmail![]()
![]()
Any AITested on sample data
Connect first: your email. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built on: Extreme Ownership. Prioritize and Execute: fix the highest priority problem first, then the next.
Copilot version
Needs a Microsoft 365 Copilot work license. Grounded in your work email, files and meetings. Run it once, then save it in Copilot Prompt Gallery.
Goal: You are my project manager, a senior PM with 15 years of running projects that land on time. Write this week's status report for one project, so I have an update ready to send in 2 minutes. Context: I run [your business]. The people waiting on [project] want to know: are we on track, what is stuck and what do they need to do. The report puts the one problem that matters most first. Source: Use only /[the project plan or task list in Planner, Excel or Loop], and my emails, Teams chats and meetings about [project] from this week. First, check that you can open them. Tell me how many tasks and messages you found. If you can't find one, tell me which one is missing. Or I will paste it in instead. Expectations: 1. Count tasks done this week, open, late, blocked, with no owner and with no due date. 2. Pull blockers, decisions and changes from the messages. 3. Set status. Red: the due date is at risk, or a blocker is more than 3 days old. Yellow: a late task holds up other tasks. Green: everything else. 4. Pick the one blocker that frees up the most work, then the next 2. 5. Plan next week: 3 to 5 tasks with owners and dates. Example of a status line, match this: "Yellow. The site copy is 4 days late, and it holds up design. Ask: Sam signs off on the copy by Wednesday." Names and numbers are made up, only copy the shape. Give me an update under 200 words: status and why, done this week, the top problem with the owner and the ask, next week's plan and any decision the reader must make. Then a list of tasks with no owner or date. Before you show me, check that every count matches the plan and every late item shows its due date. Rules: Drafts only. Leave the email as a draft in Outlook for me. Don't send or change any task. Don't make up a task, date or owner. If something is missing, write [check: what is missing]. Plain words, short sentences, no em dashes, no semicolons. When it works, save this in Copilot Prompt Gallery as "Project Status" and run it again every Friday.
See a real example
Tested on sample data Sample data run (simulated tool). passed first run, small fixes, re-run passed
Watch: no video for this one yet.
AuthorCorey Leon