work-chronicler-update-resume

name	work-chronicler-update-resume
description	Use when updating an existing resume with recent accomplishments from work history. Matches existing resume format and tone.
user-invocable	true
disable-model-invocation	true

Update Resume

Update the user's existing resume with accomplishments from their work history.

Workspace

Active profile: !work-chronicler workspace profile Work log: !work-chronicler workspace work-log Analysis: !work-chronicler workspace analysis

For non-Claude tools: Run work-chronicler workspace work-log to get your data path.

User Input

You can optionally provide:

• Resume file path: Specific resume to update (e.g., resume-2025.md)
• Time period: Date range for new accomplishments (e.g., "last 6 months", "2025")
• Focus areas: Specific types of work to emphasize

Example: /work-chronicler-update-resume resume.md, focus on platform and infrastructure work from 2025

Data Location

Work data is stored in the workspace work-log directory:

<work-log>/
├── filtered/               # ⭐ USE THIS IF IT EXISTS (pre-filtered subset)
├── .analysis/
│   ├── stats.json      # Impact breakdown, repo stats
│   ├── projects.json   # Detected project groupings
│   └── timeline.json   # Chronological view
├── pull-requests/
│   └── <org>/<repo>/*.md
├── jira/
│   └── <org>/<project>/*.md
├── resumes/            # ⭐ FIND EXISTING RESUME(S) HERE
├── performance-reviews/ # Past reviews for context (prioritize recent)
└── notes/              # User's goals and highlights

Instructions

Step 1: Find and Read Existing Resume

1. Search for resume files:

   • Check resumes/ directory in the work-log
   • Look for common filenames: resume.md, resume.pdf, *.resume.*, cv.*
   • Ask user if no resume is found

2. Understand current resume structure:

   • Note the formatting style (markdown, bullets, sections)
   • Identify existing experience entries and their format
   • Note the level of detail and tone used
   • Identify which sections need updating (usually recent experience)

Step 2: Gather Context from Supporting Documents

1. Read recent performance reviews (prioritize by recency):

   • Prioritize reviews from the last 1-2 years - these reflect current role and impact
   • Use older reviews only for career progression context, not accomplishments
   • Extract themes: what was valued, what feedback was given, growth areas

2. Read notes (if present):

   • Note what the user wants to highlight or emphasize
   • Check for career goals that accomplishments should support

Step 3: Analyze Work Data

1. Read analysis files (from filtered/ if exists):

   • stats.json - Impact distribution
   • projects.json - High-confidence project groupings
   • timeline.json - Recent activity trends

2. Focus on high-impact work:

   • Flagship PRs: Major initiatives, lead with these
   • Major PRs: Significant features worth highlighting
   • Skip minor/standard unless they support a larger narrative

Step 4: Generate Resume Updates

1. Match the existing resume format exactly:

   • Use same heading styles, bullet formats, and tone
   • Maintain consistent level of detail
   • Keep the same section structure

2. Create new accomplishment bullets:

   • Start with strong action verbs
   • Quantify impact when possible
   • Connect technical work to business outcomes
   • Group related PRs into cohesive achievements

3. Prioritize recency:

   • Most recent accomplishments should come first
   • Phase out older accomplishments that are less relevant
   • Suggest which older items might be condensed or removed

Output Location

IMPORTANT: You must do BOTH of the following:

1. Respond in-thread with the resume updates (for immediate feedback and MCP integration)
2. Save to file: <profile-root>/outputs/resume-updated-YYYY-MM-DD.md

Get the profile root with: work-chronicler workspace root

This ensures users have both immediate feedback AND a persistent file they can reference later.

Output Format

## Resume Update Suggestions

### Context
- **Resume file**: [path to resume found]
- **Work data period**: [date range analyzed]
- **Recent reviews referenced**: [list of review files, by recency]

### New Experience Bullets

These accomplishments from your work history should be added to your resume:

#### [Most Recent Position/Company Section]

**Add these bullets** (suggested placement: top of section):

- **[Achievement 1]** - [Action verb + what you did + impact/outcome]
  - *Based on*: [PR refs or project name]

- **[Achievement 2]** - [Action verb + what you did + impact/outcome]
  - *Based on*: [PR refs or project name]

#### Suggested Removals/Condensing

To keep resume length appropriate, consider:
- Condensing: [older bullet that could be shortened]
- Removing: [bullet that's now less relevant]

### Updated Resume Section

Here's how the [relevant section] of your resume would look with these changes:

---
[Full updated section in exact format of original resume]
---

### Review Alignment

These additions align with themes from your recent reviews:
- [Theme from recent review] → [Which accomplishments support it]
- [Growth area from review] → [Evidence of growth in new work]

Tips

• Recency matters: Recent performance reviews (1-2 years) are most relevant for current role framing
• Don't just list PRs: Group related work into cohesive narratives
• Match tone exactly: A formal resume needs formal language; a casual one can be more conversational
• Business impact > technical details: "Reduced costs by 40%" > "Migrated to microservices"
• Show growth: If reviews mentioned areas for improvement, highlight work that shows that growth
• Keep it scannable: Hiring managers skim; front-load the most impressive parts of each bullet