Upward Reporting Script

The Problem

Engineers often complete solid work but report it as a list of activities: I optimized the service, I handled the incident, I shipped the feature. That framing hides outcomes, misses business impact, and makes it hard for leadership to prioritize what matters. This skill addresses that gap by turning scattered work results into upward-facing reporting language that is result-oriented, measurable, and scene-aware, rather than producing a generic weekly report or performance summary.

How It Works

The skill starts by collecting three inputs: the audience, the reporting context, and the concrete work results with available metrics. It then follows a what was done -> what value was created -> how to quantify it -> how to phrase it path, using STAR to separate situation, task, action, and result. It can reframe we fixed the pipeline into we reduced build failures and shortened delivery cycles, and prepare different versions for 30-second check-ins, meetings, or written updates. It also anticipates follow-up questions and drafts concise answers.

Boundaries

It does not invent achievements or replace judgment. Users should confirm the key value claims and provide real facts. If metrics are missing, the skill can help find angles such as time saved, scope affected, or stability improved, but it should not fabricate numbers. It is not a weekly-report generator, annual review writer, performance self-evaluator, or task assignment tool. Sensitive data should be masked, and internal project names can be codenamed.