Work Summary Writer

Problem to solve

When writing weekly, monthly, quarterly, or annual reports, the hard part is not typing more text but making scattered work look verifiable: people often say 'I pushed the project forward' without numbers, turn problems into blame, or use the same tone for a manager, peers, and cross-team stakeholders. This skill is for office-efficiency workflows and helps turn rough updates into structured Markdown summaries.

How it works

It first asks for time scope, role type, priority area, and audience. Different audiences imply different depth: a direct manager may care about risk and decisions, while a cross-team reader may care about dependencies and interfaces. It then organizes content as 'results → issues → plan.' Core outputs should start with action verbs and include data, such as 'Completed service split and reduced P95 latency by 18%.' Issue reviews should use objective attribution and corrective actions, avoiding blame. Plans should include deliverables and dates, avoiding vague phrases like 'keep pushing.' Users can also provide a draft, and the skill can polish it, merge duplicate items, strengthen weak sections, and output Markdown by default, with plain-text or table variants when needed.

Boundaries

It works best when factual project materials already exist but need structure. If key facts, metrics, or legal/financial wording are unconfirmed, add them first; otherwise the output may present assumptions as conclusions.