Brag Sheet — Work Impact Writer

Quick Start

Agent Behavior Rules

1. DO confirm the time range and scope before scanning sources. Don't assume "last week" — ask.
2. DO check which tools are available (

   save_to_brag_sheet

   ,

   git

   ,

   gh

   ) before choosing a workflow.
3. DO always include all three parts: action → result → evidence. If evidence is missing, write

   (evidence needed)

   — never silently omit.
4. DO show drafted entries to the user before saving. Never auto-save without confirmation.
5. DO group related commits into a single entry. Ten commits on the same feature = one entry.
6. DO preserve the user's voice. Reframe for impact, but don't invent accomplishments or inflate scope.
7. DO NOT fabricate metrics, team sizes, or impact numbers. If the user doesn't provide a number, don't invent one.
8. DO NOT write entries for work the user only described verbally without verifying. Ask: "Did this ship? Is there a PR or doc I can reference?"
9. DO NOT skip the backfill scan steps or draft entries before scanning is complete.
10. DO NOT pad weak periods with trivial entries. An honest gap is better than inflated fluff.

Entry Format

Did [action] → [result/impact] → [evidence]

Anti-Patterns

(evidence needed)

Evidence Ladder

(evidence needed)

Categories

pr

bugfix

infrastructure

investigation

collaboration

tooling

oncall

design

documentation

How to Help the User

1. If

   save_to_brag_sheet

   tool is available → use extension tools directly (

   save_to_brag_sheet

   ,

   review_brag_sheet

   ,

   generate_work_log

   ). Do not reference or attempt to call these tools unless they are confirmed available.
2. If git or gh CLI is available → backfill from commits and PRs (see Backfill section below)
3. Otherwise → guided interview: "What did you work on?", "Who benefited?", "What's the evidence?"

Backfill Workflow

Step 1: Scan available sources

git --version 2>/dev/null         # for commit mining
gh --version 2>/dev/null          # for PR mining
ls ~/.copilot/session-state/ 2>/dev/null  # Copilot session logs

git log --author="$(git config user.email)" --since="2 weeks ago" \
  --pretty=format:'%h|%ad|%s' --date=short --no-merges

gh pr list --author @me --state merged --limit 20 \
  --json number,title,repository,mergedAt

• Path:

  ~/.copilot/session-state/<session-id>/workspace.yaml

• Read fields:

  summary

  ,

  cwd

  ,

  repository

  ,

  branch

• Skip sessions without a

  summary

  field
• Note: this directory may not exist on all machines

Step 2: Group related work

• Same PR + its commits → 1 entry
• Multiple commits on the same file/feature within 3 days → 1 entry
• Copilot sessions referencing the same repo + branch → merge into PR entry if one exists

Step 3: Draft entries

Step 4: Present and refine

Step 5: Output

## Week of 2025-04-14

### 🚀 PRs & Features
- **Migrated auth service to managed identity** → eliminated 3 secret rotation incidents/quarter → PR #312

### 🏗️ Infrastructure
- **Built CI pipeline for copilot-brag-sheet** → 107 tests across 3 OSes × 3 Node versions → shipped v1.0.0

Performance Review Prep

Structure

1. Gather — collect entries from the work log (or backfill using the workflow above)
2. Select — pick the top 3–5 highest-impact items
3. Rewrite each item with three parts:
   • What I did — the specific action
   • Why it mattered — who benefited, what changed
   • Proof — PR number, metric delta, dashboard link, customer outcome
4. Organize by impact theme (not chronologically):
   • Delivering results / operational excellence
   • Customer / team impact
   • Collaboration / mentoring / leadership
   • Growth / learning
5. Ask for gaps — if evidence is missing, prompt the user: "What metric changed?", "Who was unblocked?", "What's the PR or incident ID?"

Strong vs weak entries

Narrative format

Output Contract

1. Every entry has action → result → evidence (mark

   (evidence needed)

   if missing)
2. No fabricated metrics — only user-provided or source-verified data
3. Entries shown to user before saving
4. Time range explicitly stated
5. Output is pasteable markdown with categories assigned

Gotchas

No recent commits in the current repo

1. Ask if they want to scan a different repo or branch
2. Check

   gh pr list --author @me --state merged

   for cross-repo PRs
3. Fall back to the guided interview — not all impactful work leaves git traces (design docs, incident response, mentoring)

Review period doesn't match git history

git log --author="$(git config user.name)" --since="2024-07-01" --until="2025-01-01" --oneline

gh pr list --state merged

User can't quantify impact

Copilot session directory doesn't exist

~/.copilot/session-state/

"brag" might mean something else

Pair programming or co-authored commits

Automatic Session Tracking (Optional)

save_to_brag_sheet

review_brag_sheet

generate_work_log