Skip to content
cccskills
FreePublished on GitHub

stakeholder-update

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

The English summary is being prepared. Showing the original description.

Works withSlack
See how to install

Files included (1)

  • SKILL.md2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Stakeholder Update

Generate status updates by aggregating data from git history, issue tracker, and spec file changes.

Workflow

  1. Determine period — Default: last 7 days
  2. 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
  3. Categorize items into the 5 sections below
  4. 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

See all skills by qa-aman

Report a problem with this skill