skills.rest
qa-aman
qa-amanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

stakeholder-update

Generate structured status updates from git history, tickets, and spec changes.

11|Updated Mar 20, 2026
Search Tags:#status report#project tracking#weekly report#stakeholder update#leadership communication#git log#progress summary
One-click install
npx skills add https://github.com/qa-aman/next-leap-claude-code --skill stakeholder-update-qa-aman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stakeholder-update
Source: https://github.com/qa-aman/next-leap-claude-code/tree/main/.claude/skills/stakeholder-update
Command: npx skills add https://github.com/qa-aman/next-leap-claude-code --skill stakeholder-update-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing weekly or fortnightly status updates for leadership is repetitive and time-consuming, requiring manual aggregation of progress across git commits, issue trackers, and spec files. This Skill automates that aggregation and formats the result into a consistent, leadership-ready report. ## Core Features & Use Cases - Multi-source aggregation: Pulls recent activity from git history, updated tickets, and modified spec files into one report. - Structured five-section format: Produces Highlights, In Progress, Blocked, Next Period, and Risks sections with enforced writing rules like action verbs and outcome-focused bullets. - Multi-project mode: Repeats the report structure per project when you manage several workstreams. - Use Case: Every Friday, run the skill to compile the past week's commits and ticket updates into a Slack-ready status update for your stakeholders, with blocked items naming who can unblock them. ## Quick Start Ask the assistant to generate a stakeholder status update for the last 7 days using recent git commits, tickets, and spec changes.

Frequently Asked Questions about stakeholder-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly status report from git history?▼

Run the skill with a target period, and it executes git log with a since filter to collect non-merge commits, then combines them with ticket and spec changes. The output is a formatted report with highlights, in-progress items, blockers, and risks.

What data sources does a stakeholder status update use?▼

The update aggregates three sources: git commit history via git log, recently updated issues from the ticket tracker, and recently modified spec files. These are categorized into the five report sections.

Can I generate status updates for multiple projects at once?▼

Yes, multi-project mode repeats the five-section structure per project within a single report. Each project gets its own Highlights, In Progress, Blocked, Next Period, and Risks subsections.

How do I change the reporting period for a status update?▼

Specify the desired period when invoking the skill, such as the last 14 days for a fortnightly update. The default period is the last 7 days, applied to the git log since filter.

What makes a good blocker or risk entry in a status report?▼

Blocked items must name the specific person who can unblock them, and risks must include a likelihood rating of high, medium, or low plus an impact assessment. Empty Blocked and Risks sections are omitted from the output.

Related Skills

Explore More Product & Management Skills→
ngochuy13ngochuy13

standup

Generate a structured yesterday/today/blockers standup update from work activity.

Community
Basic
readdlereaddle
136

spark-persona-project-manager

Extract action items and deadlines from email threads and meeting transcripts.

Official
Advanced
jtvarisjtvaris

retrospective

Generates structured sprint or milestone retrospectives from plans, git history, and blockers.

Community
Advanced
Knuckles-TeamKnuckles-Team

generate-status-report

Generate project status reports from Jira issues and publish to Confluence.

Official
Advanced