Individual skill
status-update-writer
Converts raw development notes into professional daily or weekly project status updates. Use when turning scattered notes/bullet points into a shareable update for a team or stakeholder.
skills/documentation/status-update-writer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 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)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 1,365 bytesSKILL.mdcore · 2,179 bytesexamples/example.mddoc · 1,418 bytes
Read excerpt
## Purpose
Turn raw, informal development notes (a scratch list of what got done, blockers, half-finished thoughts) into a clear, professional status update suitable for sharing with a team or stakeholder.
## When to Use
- Writing a daily/weekly status update from rough notes.
- Converting a stream-of-consciousness list of "did X, working on Y, blocked on Z" into something shareable.
- Standardizing status update format across a team.
## What to Analyze / Do
1. **Separate signal from noise** — not every micro-task belongs in a status update; group related work into meaningful lines (5 small bug fixes on the same feature become one line, not five).
2. **Organize into clear sections** — typically: Done (this period) / In Progress / Blocked / Next. Adapt if the team has an existing format.