Brag Document — Work Impact Writer

Turn engineering work into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. This skill is part of the spec-driven workflow: when you point it at a feature, it pulls that feature's PRD, tech spec, tasks, and implementation notes from Obsidian so the entries are grounded in what was actually built and why it mattered. Otherwise it interviews you and mines git history and PRs.

DO NOT USE FOR: project management, sprint planning, time tracking, ticket creation, or writing a launch announcement to "brag to the team" about a feature (that's marketing copy, not a work-impact entry — confirm intent if ambiguous).

Two ways to start

(A) With a feature/task reference — the user names a feature (e.g. "brag about the queue-routing work", "write impact statements for the prd-queue-routing feature"). Read that feature's documents from the vault and use them as the primary source of context (what shipped, why, and the evidence trail). See Feature-grounded workflow below.

(B) Without a reference — the user asks generally ("what did I do last week?", "prep for my review"). Drive it from git/PRs and a guided interview, asking the questions needed to produce strong entries. See Backfill workflow and Guided interview below.

If it's unclear which applies, ask: "Do you want this tied to a specific feature/project doc, or a general scan of your recent work?"

Output to Obsidian

All output goes to a single brag document in the user's Obsidian vault, written directly on the local filesystem (no MCP). Unlike the other ai-* skills, this one is not grouped by project — your accomplishments across every repo accumulate in one place.

Vault root (default): $HOME/Documents/obsidian/obsidian — override by telling the skill a different absolute path. Use the Read/Write/Edit tools with the absolute path.