qa-aman/stakeholder-update
skills/by-role/pm/stakeholder-update/SKILL.md
Generate structured weekly or fortnightly status updates for leadership and stakeholders. Use this skill when: - You need to prepare a weekly or fortnightly status report - You want to summarize recent progress across git commits, tickets, and spec changes - You need a formatted update ready for Slack, email, or a stakeholder meeting - You want multi-project updates in one report
$ install --global
skillsauthnpx skillsauth add qa-aman/claude-skills stakeholder-updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 2:22 PM307.7s1 file scanned
SKILL.md
- name:
- stakeholder-update
- description:
- |
Stakeholder Update
Generate status updates by aggregating data from git history, issue tracker, and spec file changes.
Workflow
- Determine period — Default: last 7 days
- Gather data from 3 sources:
- Git:
git log --since="{period}" --oneline --no-merges - Tickets: Search for recently updated issues
- Specs: Find recently modified spec files
- Git:
- Categorize items into the 5 sections below
- Write update — Print to conversation
Output Format
# Status Update — {Start Date} to {End Date}
## Highlights
- {What shipped/completed — 2-5 bullets, lead with outcomes}
## In Progress
- {Active work with brief context — 2-5 bullets}
## Blocked
- {What needs unblocking + WHO can unblock}
## Next Period
- {Planned work — 2-4 bullets}
## Risks
- {Anything leadership should know — include likelihood H/M/L and impact}
Omit "Blocked" and "Risks" sections if empty.
Writing Rules
- Start each bullet with an action verb: Shipped, Completed, Started, Drafted, Reviewed, Fixed
- Include ticket keys where relevant
- 1-2 lines per bullet max
- Blocked items: always include WHO can unblock
- Risks: include likelihood and impact
- Highlights focus on outcomes, not activities
- No filler language — leadership reads fast
Multi-Project Mode
If multiple projects, repeat the 5-section structure per project:
## Project: [Project A]
### Highlights
...
## Project: [Project B]
### Highlights
...
Anti-Patterns
- Don't list activities without outcomes — "Wrote tests" vs "Increased test coverage to 85%"
- Don't leave Blocked items without naming who can unblock
- Don't include risks without likelihood/impact
Quality Checklist
- [ ] Highlights lead with outcomes
- [ ] Blocked items name the unblocker
- [ ] Risks include likelihood and impact
- [ ] Bullets start with action verbs
- [ ] Under 2 lines per bullet
Related Skills
qa-aman/webinar-planner
development
VerifiedTrustedCommunity
Plan a webinar end-to-end using April Dunford's Obviously Awesome positioning framework to find the topic angle that makes the webinar obviously valuable to the right audience. Produces topic positioning, abstract, speaker brief, registration page, promotion sequence, day-of run-of-show, and post-webinar follow-up. Use when the user asks to plan a webinar, virtual event, online workshop, "we need a webinar on X", host a webinar, online masterclass, or any live virtual event with promotion and follow-up. Reads ICP, services, and brand voice from knowledge/.
13SKILL.mdUpdated May 5, 2026
qa-aman/thought-leadership-writer
development
VerifiedTrustedCommunity
Write long-form thought leadership articles, opinion pieces, industry POV essays, and CEO/founder bylines using the Made to Stick SUCCESs framework (Chip and Dan Heath). Use when the user asks for a long-form article, executive byline, opinion piece, industry POV, manifesto, "explain our point of view on X", or wants to publish an authority-building piece (1200-2500 words). Reads brand voice and positioning from knowledge/.
13SKILL.mdUpdated May 5, 2026
qa-aman/social-calendar
development
VerifiedTrustedCommunity
Plan a monthly content calendar across channels using the Content Marketing Matrix (Dave Chaffey, Smart Insights) - Entertain/Inspire/Educate/Convince. Every post gets a quadrant label. The monthly calendar must hit 40% Educate, 40% Inspire+Convince, 20% Entertain. Produces a week-by-week posting schedule with topics, formats, channels, and asset links. Use when the user says "content calendar", "social calendar", "plan next month's content", "what should we post", "content plan", "editorial calendar", "schedule posts for the month", or wants a structured posting plan for LinkedIn, Twitter, email, or blog. Reads brand voice, ICP, and past learnings from knowledge/.
13SKILL.mdUpdated May 5, 2026
qa-aman/seo-article-writer
development
VerifiedTrustedCommunity
Write SEO-optimized long-form articles targeting specific keywords using the They Ask You Answer Big 5 framework (Marcus Sheridan). Articles are categorized by Big 5 type (Cost, Problems, Versus, Best/Reviews, How-To) and structured accordingly. The "answer first" rule applies to every article. Use when the user asks for an SEO article, blog post for ranking, "rank for keyword X", organic content, search-optimized post, pillar page, or content for organic traffic. Includes keyword targeting, search intent matching, internal linking suggestions, and meta tags.
13SKILL.mdUpdated May 5, 2026