skills.rest
m-de-graaff
m-de-graaffCOMMUNITY
Explore all skills by this author →
GitHub

reporting-work

Structure status updates and work reports with an outcome-first format.

Updated Aug 3, 2026
Search Tags:#communication#evidence#status report#summary#concise writing#outcome-first#work update
One-click install
npx skills add https://github.com/m-de-graaff/skills --skill reporting-work-m-de-graaff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reporting-work
Source: https://github.com/m-de-graaff/skills/tree/main/skills/reporting-work
Command: npx skills add https://github.com/m-de-graaff/skills --skill reporting-work-m-de-graaff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Status updates and task summaries often bury the answer under preamble, restate the request, or pad findings with filler, forcing readers to hunt for the actual outcome. This Skill enforces a fixed report shape so the conclusion always comes first. ## Core Features & Use Cases - Outcome-first structure: Every report opens with one line stating what is now true, followed by evidence, detail, and next steps in a fixed order. - Evidence discipline: Claims must be backed by a command and its result, such as test counts, exit codes, or before-and-after metrics. - Density rules: File paths with line numbers, concrete numbers, and named identifiers replace vague descriptions and adjectives. - Use Case: After fixing a bug and running the test suite, produce a report that opens with the fix, cites the passing test output, lists the numbered changes, and flags one related out-of-scope issue. ## Quick Start Summarize the work you just completed as a concise status report with the outcome first, evidence, and next steps.

Frequently Asked Questions about reporting-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a concise status update on completed work?▼

Open with one line stating what is now true, then add the command output as evidence, a numbered or bulleted detail list, and any blocked or undecided next steps. Omit any section that has no content rather than padding it.

How should I report the result of a long multi-step task?▼

Lead with the outcome in past tense, cite the verification command and its result, then list steps as numbered items the reader could follow or repeat. When findings exceed about five items, switch from a list to a table with one row per finding.

What makes a good evidence line in a work report?▼

An evidence line pairs the command with its concrete result, such as a passing test count, an exit code, or a before-and-after latency figure. A claim without a verifiable number means the verification step has not actually been run.

When should a report use a table instead of a list?▼

Switch to a table when there are more than about five findings, with one row per finding and columns for location and description. Prose repeated with different subjects is a table that has not been written yet.

Does this reporting format apply to commit messages or PR descriptions?▼

No, commit messages, PR bodies, and tickets follow their own conventions defined elsewhere. This format governs conversational status reports and summaries of completed work, and it never overrides an explicit request for a full explanation or walkthrough.

Related Skills

Explore More Content & Communication Skills→
LerianStudioLerianStudio
205

verification-before-completion

Require fresh verification command output before claiming task completion.

Official
Basic
ai-analyst-labai-analyst-lab
21

close-the-loop

Embed follow-up plans into run-analysis recommendations with next steps and owners.

Official
Basic
ultramaxoAIultramaxoAI

verification-before-completion

Run verification commands and attach evidence before claiming task completion.

Official
Advanced
videojsvideojs
931

write-design-doc

Writes compact Video.js architecture and decision records with non-inferable rationale.

Official
Basic