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.
npx skills add mohitagw15856/pm-claude-skills --skill brag-doc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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:**
- Required Inputs
- Output Format
- Brag Doc — [your name], [period]
- Quality Checks
- Anti-Patterns
- Based On
What does the brag-doc skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill brag-doc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.