Brag Doc

Two living docs the user maintains:

• projects/side/brag/<employer>.md — employment, one file per employer (e.g. acme.md). For perf/promo cycles; shared with the manager.
• projects/side/brag/side-projects.md — public work (OSS, content, shipped apps). Feeds the 2026 job search and cv-craft.

Invocation: /brag-doc <mode> [target]. target is work or side — ask if the mode needs one and it's unclear. For work, resolve to the employer file in projects/side/brag/; ask which if more than one exists. (Personal skills take space-separated args, so /brag-doc draft work, not :draft.)

Why the extra fields

A brag doc written only as "shipped + impact" is enough for a perf review and not enough for an interview. A 2026 post-rejection audit had to dig through git, PR threads, a PM tool and a billing ledger to answer three questions the monthly entries never recorded: what exactly was mine, is it live or on staging, and how was that number measured. Each answer was cheap at the time and expensive months later. The fields below capture them while the evidence is still fresh. The full interview method lives in cv-craft's STORIES.md.

Modes