status-reporting

This skill is for anyone who regularly writes progress updates — team leads, project managers, individual contributors, and anyone reporting to management, executives, or clients. It solves the recurring pain of turning messy raw material (standup notes, ticket exports, metrics, last week's report) into a clean, consistent, honest status report without reinventing the format each time.

It's particularly useful for teams that want reports to look like they came from one disciplined author regardless of who wrote them, and for automated weekly reporting pipelines that generate updates from ticket data on a schedule. The emphasis is on signal over noise and honesty over spin.

When invoked, the skill first establishes the frame: it identifies the audience/altitude (team, management, executive, board, or client) and whether a house format exists to match. If these aren't clear and a human is present, it asks once concisely; in batch/non-interactive mode it proceeds with supplied or defaulted values and states its assumptions. It then runs an intake process to collect and synthesize inputs — grouping items into sections, deduplicating, separating done from planned, attaching numbers to claims, and diffing against any prior report to compute deltas, carry-forward, and status trends.

It routes to one of three modes — weekly status, executive summary, or house-format setup — and applies its writing and honesty/RAG principles throughout. The output is a polished, bottom-line-up-front report using the appropriate template, surfacing risks and slippage near the top, distinguishing facts from projections, and never fabricating progress. Reports are delivered as clean copy-pasteable content by default, matching a supplied house format exactly or a strong default template.