status-updatelisted
Install: claude install-skill teodstr/workbench
# Status update
A good update is read in a minute and leads to decisions. This skill puts the conclusion first, as Minto's pyramid principle recommends, and keeps the status colors honest.
## When to use
- Every week or two during a project, and before a steering meeting.
- When something slips and the people involved need to know.
- Not for a meeting agenda: use `meeting-toolkit`.
## Inputs
1. The plan (milestones, budget) and what actually happened since the last update.
2. The audience and what they need to decide or know.
3. Risks and issues from the `risk-register`.
## Method
1. **Lead with the status and one sentence**: on track, at risk or off track, using criteria written in advance (for example "at risk" when a milestone may slip by more than a week or the budget by more than the reserve).
2. **Say what changed** since the last update: milestones reached, milestones slipped, with the new dates and the reasons.
3. **Ask for the decisions needed**, each with the options, a recommendation and a date by which the decision is needed.
4. **Show the numbers that matter**: schedule (milestones), budget (planned, committed, paid), and one or two indicators specific to the project.
5. **List the top risks and issues** with their owners and next steps.
6. **Adapt the format to the reader**: five lines for a busy executive or a family group, a table for a client or a committee. The content stays honest; only the length changes.
## Output
```markdown
### <Project>: statu