wtf is brag-doc?

brag-doc is a template repository built around two Claude Code skills that help an engineer keep track of their own accomplishments so review season is not a scramble to remember what happened months ago. The idea is to log daily wins in a couple of minutes, then turn those entries into a promotion case or self review draft when it is actually needed. It works in two steps. The daily eval skill, triggered with a slash command or just by saying something like let's log today's wins, asks a few quick questions and appends the answers to a dated markdown file under entries, organized by year and month. Entries are append only, so someone can log more than once a day or backfill a specific past date. The review builder skill then reads through those entries and generates a draft, either in a generic portable format or in a format that mirrors a specific employer's actual review questions, landing in a reviews folder that is not committed to git. The generated draft is meant to be read over and edited before submitting, since it can only be as complete as what was actually logged. Setting up the company specific format means swapping in your own employer's real review questions in place of the fictional example the repo ships with, optionally by dropping in a PDF of the official template and asking Claude to update the format to match it. The sample entries and sources included in the repo are entirely fictional, describing a made up company and made up people, purely to demonstrate the workflow. Because this is a public template, the README is explicit that once someone starts logging their own real work, those entries will contain real names and real manager feedback, and recommends moving to a private repository rather than pushing that real journal to a public one. The only requirement to use it is having Claude Code installed, since both skills live entirely inside this repo's .claude/skills folder and produce plain markdown as output.