Recover an old résumé and update it from career records

Why use this

1. An old résumé can be difficult to locate among email attachments, and later career details may be scattered across projects and correspondence. A rewrite that fills gaps from context can accidentally invent dates, inflate responsibility or expose confidential client work.

2. This job could recover the best available baseline and build a traceable update draft. A short change log and unresolved-fact list would let the user review substantive career claims separately from improvements to wording and layout.

Why an agent / simpler alternative

Useful judgment

Reconcile career chronology and translate documented work into concise, audience-appropriate descriptions.

Simpler alternative

Update the current résumé manually when recent changes are limited and already well documented.

Unsuitable when

The task requires fabricating achievements, qualifications or employment history.

Proposed inputs

1. Name

   Prior résumé candidates

   Owner

   User

   Minimum scope

   Authorized email attachments and identifying date or employer clues

   Quality check

   Distinguish the final résumé from drafts and versions tailored to older roles.

2. Name

   Career update brief

   Owner

   User

   Minimum scope

   Confirmed roles, dates, responsibilities and approved achievements

   Quality check

   Separate measurable evidence from estimates or aspirational language.

Access and setup — proposed or unknown

Proposed minimum

1. Search scoped authorized mail and edit a résumé copy; keep the recovered original intact.

Compatibility unknowns

1. Unknown: attachment extraction, mailbox coverage and current document-format support.

External actions requiring approval

1. Sharing the résumé, applying for roles or disclosing private client information.

Expected deliverable and review checks

Proposed artifact

Updated résumé draft with factual change log, source notes and unresolved dates or claims.

Critical checks

1. Chronology is internally consistent and current-tense wording matches actual status.

2. Impact figures and credentials are included only when the user can substantiate them.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   A role-specific old résumé is mistaken for the complete career record.

   Why it matters

   Relevant work may disappear or an outdated emphasis may dominate.

   Proposed response

   Compare candidate versions and ask the user to choose the baseline.

2. Signal

   A project email mentions a team result that becomes an individual achievement.

   Why it matters

   The résumé may overstate the user’s contribution.

   Proposed response

   Describe the confirmed role and request evidence before attributing the whole outcome.

Effort and cost — unknown

Setup work

1. Identify the baseline and collect approved factual updates.

Ongoing review

1. Review claims, dates and formatting for the intended audience.

Unknowns

1. Unknown: attachment quality, rewriting effort and need for additional career evidence.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Synthetic files include a short sales-focused résumé and a fuller general version; a later project note names a team achievement.

Acceptance checks

1. The baseline choice is explicit.

2. The team result is not converted into unsupported individual credit.

Stop conditions

1. Missing facts must be invented or the document would be sent externally.

Limits

1. A stronger draft remains subject to the user’s factual review and does not establish hiring effectiveness.