---
name: daily-project-status-digest
description: Turn messy daily project updates, standup notes, Slack excerpts, issue comments, or meeting notes into a concise project manager status digest. Use this whenever a Project Manager needs a daily status summary, risk register, blocker list, owner follow-ups, stakeholder update, or next-action plan from raw team updates.
---

# Daily Project Status Digest

## Intended User Role

Project Manager

## Workflow It Solves

Convert fragmented daily project inputs into a job-ready status digest that a PM can use for standup follow-up, stakeholder updates, and risk tracking.

## Required Inputs

- Raw updates from one or more sources, such as standup notes, chat excerpts, issue comments, task tracker exports, or meeting notes.
- Project context if available: project name, milestone, target date, workstreams, stakeholders, or known priorities.
- Optional output audience: internal team, leadership, client, vendor, or cross-functional stakeholders.

If a critical input is missing, make a reasonable assumption and label it. Ask a clarifying question only when the missing detail would change the status, escalation, or owner assignments.

## Expected Outputs

Produce a concise status digest with:

- Overall status: green, yellow, or red, with one-sentence rationale.
- Executive summary: 3-5 bullets focused on progress, risks, blockers, and decisions.
- Workstream table: workstream, latest progress, owner, next step, status.
- Blockers and risks: severity, impact, owner, due date if known, recommended escalation.
- Decisions needed: decision, decision maker, deadline, context.
- Follow-up messages: short drafts for people who need action.
- Assumptions and gaps: missing facts that should be confirmed.

## Procedure

1. Identify the project, date, audience, and reporting horizon from the user's prompt and inputs.
2. Normalize the raw updates into workstreams. Merge duplicates and keep the latest update when two notes conflict.
3. Classify each item as progress, blocker, risk, decision, dependency, or question.
4. Assign owners from the input. If no owner is named, write `Unassigned` and include it in assumptions and gaps.
5. Set overall status from evidence:
   - Green: work is progressing and no material deadline, scope, or dependency risk is visible.
   - Yellow: at least one meaningful risk, unresolved dependency, slipping task, or decision gap exists.
   - Red: a blocker or confirmed slip threatens a committed date, customer commitment, launch, budget, or compliance requirement.
6. Separate facts from inference. Use factual language for reported updates and label inferred risk or priority.
7. Draft follow-up messages only for items that need action. Keep them direct, specific, and ready to send.
8. Keep the final digest compact enough for a PM to paste into a daily update without heavy editing.

## Quality Checks

Before finalizing, verify that:

- Every blocker or risk has an owner or is marked `Unassigned`.
- The overall status matches the highest-severity evidence.
- The digest does not bury deadline risk inside general progress bullets.
- Stakeholder-facing wording is clear and non-accusatory.
- Follow-up messages ask for a concrete action, date, or decision.
- Assumptions are separated from confirmed facts.

## Example Task

User prompt:

```text
Create today's project status from these updates. We are trying to ship the vendor onboarding portal by July 19. Design says Figma is done except empty states. Backend has auth working but vendor invite emails are blocked by SendGrid access. QA found two P1 bugs in document upload. Legal still has not approved the terms copy. Ana owns design, Ravi owns backend, Mei owns QA, Priya owns legal.
```

Expected behavior:

- Mark overall status yellow or red depending on stated deadline pressure.
- Surface SendGrid access, P1 upload bugs, and legal approval as blockers or risks.
- Assign owners to each blocker.
- Include a decision or escalation request for SendGrid and legal approval.
- Draft short follow-up messages to Ravi, Mei, and Priya.