status-updaterlisted

# Status Updater ## Purpose Regular status updates are the cheapest retention tool a freelancer has — clients who see steady, legible progress rarely churn or dispute invoices. This skill turns a raw commit log, task tracker export, or a rough bullet list of what got done into a client-ready update that reads as progress, not a technical diary. ## Inputs to ask the user for - Client name and project name - The raw material: paste commit messages, task list, done/in-progress/ blocked items, or just a rough list of what happened this period - The reporting period (e.g., "this week," "since last update on 8/6") - Any blockers or items waiting on the client (approvals, missing content, unanswered questions) — these need to be visible, not buried - The next milestone or delivery date, if known - Whether this project is on track, at risk, or delayed, and why (if the user doesn't say, infer conservatively from blockers and flag it as a question rather than guessing at severity) ## Step-by-step instructions 1. Translate raw/technical input into outcomes the client cares about. A commit like "fix checkout button z-index bug" becomes "fixed a bug where the checkout button was unclickable on mobile" — state the user-facing effect, not the technical cause, unless the client is technical. 2. Structure the update in three sections: **Done this period**, **In progress / next up**, **Needs from you** (only include this section if there's something outstanding — d