brag-doc
Keep a running brag document of your accomplishments so reviews and promo cases write themselves. Use when asked to start or update a brag doc, log a win, track accomplishments, or prep evidence for a review/promotion. Produces a structured, dated accomplishment log — impact-first entries with metrics, scope, and the evidence link — grouped so it drops straight into a self-review or promo packet.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/brag-doc && cp -r /tmp/brag-doc/plugins/pm-career/skills/brag-doc ~/.claude/skills/brag-docSKILL.md
# Brag Doc Skill
Nobody remembers in December what they shipped in March — so good work goes uncredited at review time.
A brag doc is the fix: a running, dated log of what you did and the impact it had, captured while it's
fresh. This skill turns a pile of "stuff I did" into impact-first entries you can paste straight into a
[`self-review`](../self-review/SKILL.md) or [`promotion-packet`](../promotion-packet/SKILL.md).
## Required Inputs
Ask for these only if they aren't already provided:
- **The win(s)** — what you did (rough notes are fine; the skill structures them).
- **Impact** — the outcome and any metric (before → after, time saved, revenue, users) — even a rough one.
- **Scope & role** — your specific contribution vs. the team's, and who it affected.
- **Date / period** and any **evidence** (PR, doc, dashboard, kudos, ticket link).
## Output Format
### Brag Doc — [your name], [period]
Entries newest-first, grouped by theme (or quarter). Each entry is **impact-first**:
> **[Verb-led headline — the outcome, not the task]** · *[date]*
> - **What I did:** [the specific action and your role in it]
> - **Impact:** [metric / outcome — before → after where possible]
> - **Scope:** [who/what it affected — team, org, customers]
> - **Evidence:** [link]
> - **Maps to:** [the competency / ladder level it demonstrates — e.g. "cross-team influence"]
Example:
> **Cut onboarding drop-off 18% → 9%, unlocking ~$140k ARR** · *Mar 2026*
> - **What I did:** led the redesign of the 3-step signup flow; wrote the PRD, drove eng + design alignment.
> - **Impact:** activation 41% → 52%; drop-off halved (measured over 6 wks, 20k users).
> - **Scope:** owned end-to-end; affected all new signups.
> - **Evidence:** [PRD] · [dashboard]
> - **Maps to:** drives measurable product outcomes; cross-functional leadership.
End with a **"Themes this period"** summary — the 3–4 narrative threads your wins ladder up to.
## Quality Checks
- [ ] Every entry leads with **impact/outcome**, not the activity
- [ ] Metrics include the baseline (before → after), not a bare percentage
- [ ] Your specific contribution is distinguished from the team's
- [ ] Each entry links real evidence
- [ ] Entries are tagged to a competency/ladder level, so the doc feeds a review or promo case directly
## Anti-Patterns
- [ ] Do not log tasks ("attended planning", "wrote code") — log outcomes ("shipped X, which moved Y")
- [ ] Do not wait until review season — capture wins within a week, while the metrics and context are fresh
- [ ] Do not inflate or claim team wins as solo — overstated credit is worse than none when a manager checks
- [ ] Do not omit the metric because it's imperfect — a rough, labelled estimate beats "improved things"
- [ ] Do not bury the evidence — an unlinked claim is one a busy manager can't verify or champion
## Based On
Brag-document practice (Julia Evans) and impact-first accomplishment tracking.Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.