Menu

Individual skill

async-update-format

0upvotes

Write status updates people actually read — the traffic-light-plus-narrative format (state first, story second), the blockers-are-asks rule, and the skimmable structure that respects a reader with thirty seconds. Use when asked write my weekly update, format our team's status posts, nobody reads my updates, or what goes in a good async check-in. Produces the update format with a filled example, the blockers-as-asks discipline, and the reader-time contract.

plugins/pm-cowork/skills/async-update-format/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Async Update Format Skill

Status updates die of two diseases: the activity log ("attended meetings, worked on the project") that says nothing, and the essay that says everything to readers with thirty seconds. The format that survives: **state first** (on-track / at-risk / blocked, with the one-line why), then the delta (what changed since last time — not what exists), then blockers written as *asks with names* ("blocked on X — need [person] to approve Y by Friday"), then the next milestone with its date. Skimmable in thirty seconds, expandable for the reader who wants more.

## What This Skill Produces

- **The format** — state → delta → asks → next, with length budgets per section
- **A filled example** — realistic, showing the delta-not-inventory discipline
- **The blockers-as-asks rule** — every blocker names a person and an action, or it's just weather
- **The reader-time contract** — the 30-second skim layer and the optional depth layer, separated

## Required Inputs

Ask for these if not provided:
Back to top