borghei/Claude-Skills / project-management/execution/status-update-generator
status-update-generator
VerifiedRenders 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.0 KB |
| assets/sample_status.json | config | 2.3 KB |
| assets/weekly_status_template.md | markdown | 2.1 KB |
| examples/acme-search-platform-weekly.md | markdown | 7.9 KB |
| references/red-flags.md | markdown | 10.2 KB |
| references/status-structure-and-workflow.md | markdown | 4.8 KB |
| references/status-update-style-guide.md | markdown | 10.8 KB |
| references/tool-and-troubleshooting.md | markdown | 4.6 KB |
| scripts/status_generator.pyexecutable | script | 18.1 KB |
assets/sample_status.json
View on GitHub{
"period": "Week of 2026-05-18",
"project": "Acme Search Platform",
"author": "Jane Doe (PM)",
"status": "yellow",
"status_rationale": "Index rebuild succeeded and exceeded latency targets; Phase 2 rollout blocked on security review.",
"highlights": [
{
"title": "Search latency p95 down to 210ms",
"detail": "Index rebuild dropped p95 from 480ms to 210ms. Customer reports of slow search resolved.",
"ticket": "PROJ-1234"
},
{
"title": "Pilot tenant Acme Inc. migrated to v2 index",
"detail": "Zero downtime; tenant confirmed acceptance.",
"ticket": "PROJ-1240"
},
{
"title": "12 support tickets closed",
"detail": "All open 'slow search' tickets resolved post-rebuild.",
"ticket": null
},
{
"title": "SDK documentation refresh published",
"detail": "New partner docs live; first partner integration started.",
"ticket": "PROJ-1251"
}
],
"blockers": [
{
"what": "Phase 2 rollout to enterprise tenants",
"blocked_by": "Security review (InfoSec team)",
"need": "Schedule the threat-model review before Friday so rollout can begin next sprint."
}
],
"risks": [
{
"risk": "Cost overrun on infra during traffic ramp",
"likelihood": "M",
"impact": "M",
"mitigation": "Add auto-scale ceiling; alert at 80% budget",
"owner": "SRE lead",
"due": "2026-05-30"
},
{
"risk": "Index rebuild causes brief read latency on next refresh",
"likelihood": "L",
"impact": "M",
"mitigation": "Rebuild during off-peak window; pre-warm cache",
"owner": "Search infra eng",
"due": "2026-06-05"
}
],
"asks": [
{
"what": "Approval to onboard 3 pilot enterprise tenants",
"by_when": "2026-05-24",
"from_whom": "VP Sales",
"consequence": "Slips the Q2 enterprise revenue target by ~$80K if delayed past 2026-05-31."
}
],
"next": [
{
"title": "Complete security review and start Phase 2 rollout",
"detail": "Begin with the 3 pilot tenants pending VP Sales sign-off."
},
{
"title": "Q2 OKR mid-quarter readout",
"detail": "KR1 (latency) is met; KR2 (rollout) tracking on plan."
},
{
"title": "Begin Phase 3 design",
"detail": "Multi-tenant index sharding RFC drafted."
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |
| 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: 108k | Updated | Claude CodeCodex | Verified | Install |
| 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: 108k | Updated | Claude CodeCodex | Verified | Install |