Experience Narrative Distiller

Output Contract

Return two versions:

1. Readable draft

   • 1-2 sentence summary
   • 3-7 optional bullets

2. Structured payload (ready for experience[] in src/data/cv/content.ts)

{
  id: "<kebab-id>",
  organization: "<Organization>",
  period: "<Mon YYYY -- Mon YYYY|Present>",
  role: "<Role>",
  location: "<Location>",
  summary: "<Recruiter-facing summary>",
  highlights: [
    { text: "<Outcome bullet 1>" },
    { text: "<Outcome bullet 2>" }
  ],
  highlighted: <true|false>
}

Writing Rules

• Prefer outcomes over process.
• Keep summaries concise and skimmable.
• Include numbers only when they communicate clear impact.
• Avoid low-signal details (for example, weekly hour counts) unless user requests them.
• Use active verbs: built, led, launched, reduced, improved, scaled.

Style Variants

When useful, provide both:

• With numbers: includes key metrics.
• Without numbers: cleaner narrative tone.

Quality Gate Before Finalizing

Ensure each summary answers:

1. What did this person own?
2. What changed because of their work?
3. Why should a recruiter/partner care?

If any answer is weak, ask one targeted follow-up and refine.