Skip to content

borghei/Claude-Skills / project-management/execution/status-update-generator

status-update-generator

Verified

Renders a weekly executive status update (highlights, blockers, risks, asks, next) from Jira or Linear data. Use when preparing a sponsor or steering update, or standardising a team's weekly report.

assets/weekly_status_template.md

View on GitHub
# [Team or Project Name] -- Week of [YYYY-MM-DD]

**Author:** [Name, role]
**Period:** [YYYY-MM-DD] to [YYYY-MM-DD]
**Status:** [GREEN / YELLOW / RED]
**Rationale:** [One sentence explaining the color.]

---

## Highlights

> 3-5 bullets. Outcome-led: name the user or business outcome, not the activity. Quantify wherever possible.

- [Outcome 1 -- what changed for the user/business; include ticket ref if helpful]
- [Outcome 2]
- [Outcome 3]
- [Outcome 4] (optional)
- [Outcome 5] (optional)

## Blockers

> Things actively stopping the team. Each blocker has 3 parts: what is blocked, who/what is blocking, what we need.

- **[What is blocked]**
  - Blocked by: [team / vendor / decision]
  - Need: [specific ask or decision required to unblock]

> If there are no blockers this week, write: "None this week."

## Risks

> Things that could become blockers. Use the format: Risk -- Likelihood (H/M/L) x Impact (H/M/L) -- Mitigation -- Owner -- Due.

- [Risk description] -- [L/M/H] x [L/M/H] -- Mitigation: [action] -- Owner: [name] -- Due: [YYYY-MM-DD]
- [Risk description] -- [L/M/H] x [L/M/H] -- Mitigation: [action] -- Owner: [name] -- Due: [YYYY-MM-DD]

> If there are no new risks this week, write: "No new risks this week" and link to the standing risk register.

## Asks

> Specific decisions, approvals, resources, or introductions needed from this audience.

1. [What you want] -- From: [name/role] -- By: [YYYY-MM-DD] -- Consequence of delay: [what slips]
2. [Second ask if any]

> If there are no asks this week, write: "None this week." Always include the section.

## What's Next

> 3-5 bullets. Same outcome-led style as Highlights. Sets expectations for next week's update.

- [Planned outcome 1]
- [Planned outcome 2]
- [Planned outcome 3]
- [Planned outcome 4] (optional)
- [Planned outcome 5] (optional)

---

## Appendix (optional)

- **Links:** [PRD] [Roadmap] [Dashboard] [Risk register]
- **Sprint reference:** Sprint [N] of [N]
- **OKR alignment:** Contributes to [O1 / KR2]
- **Prior week's status:** [link]

---

> Saved as: `status-[team]-YYYY-MM-DD.md`
> Distribute via [agreed channel] every [day] at [time].
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall