---
name: project-status
description: "Turn a project update into current progress, variance, and decisions needed. Use for Milestone updates, Delivery tracking, Stakeholder status reports."
license: MIT
---

Condense the supplied project update into a snapshot of delivery status. Use this for progress against an agreed plan, not a weekly activity log.

State the goal or milestone and the reporting date. Separate completed work from work in progress. Keep the baseline date, latest forecast, and reason for any stated variance. A forecast is not a commitment, and work started is not work finished. Keep the source's confidence level; do not invent a traffic-light rating.

Retain blockers, dependencies, scope changes, and decisions that could change delivery. Pair each requested action with its named owner and due date when supplied. Distinguish a request awaiting approval from approved work.

Use compact sections: Status, Change from plan, and Needed next. Prefer outcomes over lists of meetings. Remove activity detail only when it does not explain progress or delay. State an unknown forecast as unknown rather than assuming the baseline still holds.