# Weekly Update

> Draft a stakeholder update email using past updates for tone

- Skill: `carlvellotti/weekly-update` (Agent Skill)
- Install (CLI): `npx skillmds@latest add carlvellotti/weekly-update`
- Raw SKILL.md: https://api.skillmd.com/api/skills/carlvellotti/weekly-update/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: carlvellotti (https://skillmd.com/u/carlvellotti)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/carlvellotti/weekly-update

---


# Weekly Update Drafter

Draft a stakeholder update email using the weekly-update template.

## Instructions

1. **Gather Information**
   - Read `Tasks/active.md` for current sprint status
   - Read `GOALS.md` for OKR targets and progress
   - Check recent meeting notes for decisions and commitments
   - Look at git history for changes this week
   - If Linear MCP connected: fetch recently completed, in progress, and blocked issues

2. **Check Stakeholder Preferences**
   - Read `Workflows/weekly-stakeholder-update/stakeholder-preferences.md` for audience needs
   - Read `Workflows/weekly-stakeholder-update/past-updates/` for tone and continuity

3. **Assess Status**
   - Compare progress against milestones
   - Identify any slippage or blockers
   - Determine overall status: On Track | At Risk | Blocked

4. **Draft Using Template**
   - Use `Workflows/weekly-stakeholder-update/draft-template.md` as the structure
   - Keep total length under 500 words
   - Lead with metrics, not activity
   - Flag blockers early with proposed solutions
   - Reference OKRs when showing progress

5. **Review Checklist**
   - [ ] Status accurately reflects reality
   - [ ] Metrics are current (not stale)
   - [ ] Blockers have clear asks attached
   - [ ] Next week priorities are realistic
   - [ ] Under 500 words

## Notes

- Lead with the headline - what's the ONE thing they need to know?
- Be honest about status - At Risk is better than surprising people later
- Make asks specific - "Need decision on X by Friday" not "need support"
- Never guess at numbers - flag "TBD" if a metric isn't available