mohitagw15856/executive-update
plugins/pm-strategy/skills/executive-update/SKILL.md
Transform detailed product updates into concise executive briefings. Use when asked to write an executive update, leadership update, product update for the exec team, or a C-suite product briefing. Produces a structured 250-word briefing with headline, key metrics, progress, risks, decisions needed, and next steps.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills executive-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: Jun 23, 2026, 7:24 AM35.5s1 file scanned
SKILL.md
- name:
- executive-update
- description:
- Transform detailed product updates into concise executive briefings. Use when asked to write an executive update, leadership update, product update for the exec team, or a C-suite product briefing. Produces a structured 250-word briefing with headline, key metrics, progress, risks, decisions needed, and next steps.
Executive Update Skill
Produce a stakeholder update that busy executives will actually read — structured around what they care about: decisions, risks, and numbers.
Reads from / Writes to the Brain
If a professional-brain (brain/) exists, ground in it instead of re-asking for what you already know:
- Read first: recent
decisions/,knowledge/(the headline numbers + their definitions), andcontext.md(voice). Runpython3 ../professional-brain/scripts/brain_query.py ./brain "<period or initiative>"and carry provenance through — flag a metric that's only[verbal]. - 📥 Propose to the Brain: the update mostly reads — but propose recording any new decision or commitment it surfaces to
decisions/, provenance-tagged. Show it, get a yes, then write with../professional-brain/scripts/brain_write.py … --commit(append-only, dry-run by default).
Required Inputs
Ask the user for these if not provided:
- Product update or notes (raw input to transform — even bullet points work)
- Audience (CEO, board, specific exec, or general leadership)
- Period (this week / sprint / month / quarter)
- Key metrics (what numbers matter to this audience)
Executive Communication Principles
- Lead with the headline, not the context
- Every update should answer: "So what does this mean for the business?"
- Flag decisions needed clearly — don't bury asks in paragraphs
- Be honest about risks — executives hate surprises more than bad news
Process
- Read the full product update provided
- Identify: key metric movements, decisions required, risks to flag, wins to celebrate
- Write in reverse pyramid style — most important first
- Limit to 250 words maximum for the main body
- Add a "Decisions Needed" section with clear options and your recommendation
- Validate — Confirm every decision needed has a specific option and recommendation (not just "TBD"), and every risk has a mitigation or watch plan
Output Structure
Product Update — [Date / Sprint / Month]
Headline: [One sentence on the most important thing]
By the Numbers:
Progress This Period: [3-4 bullet points, outcome-focused not activity-focused]
Risks & Watch Items: [2-3 bullets — be direct, include mitigation]
Decisions Needed:
- [Decision] — Options: [A] or [B] — Recommendation: [your view] — Needed by: [date]
What's Next: [2-3 bullets on next period priorities]
Quality Checks
- [ ] Whole update is under 250 words (if not, cut ruthlessly)
- [ ] Every metric includes a comparison point (vs. target or last period)
- [ ] Every risk has a mitigation or watch action
- [ ] Every decision needed has at least two options and a recommendation
- [ ] Written for a CFO or CEO — no jargon, all outcomes
Anti-Patterns
- [ ] Do not lead with context or background — executives read the headline first; bury the important thing below two sentences of setup and they will miss it
- [ ] Do not present metrics without a comparison point — a number without context (vs. target, vs. last period) cannot be interpreted and will prompt follow-up questions
- [ ] Do not soften or spin risks — executives rely on these updates to make resource and escalation decisions; sanitised risk sections destroy the update's utility
- [ ] Do not present a "Decisions Needed" item without a recommendation — asking an executive to decide without your view forces them to do the analytical work the PM should have done
- [ ] Do not exceed 250 words in the main body — length signals the author has not done the compression work; every word over 250 reduces the chance the update is read
Related Skills
mohitagw15856/win-loss-analysis
business
VerifiedTrustedCommunity
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/which-skill
development
VerifiedTrustedCommunity
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/vuln-triage
testing
VerifiedTrustedCommunity
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/voice-of-customer-program
development
VerifiedTrustedCommunity
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.
1,117SKILL.mdUpdated Jul 2, 2026