Agentic workflow

I built an agentic workflow for writing cover letters. It helps me write three times faster, while maintaining consistent quality.

A Claude Code session running the agentic cover-letter workflow

The problem

Currently, managers get dozens of AI-generated letters. Most of them sound the same.

Standing out means sounding like yourself. However, writing a tailored letter from scratch well can take hours, even days. Could an agent help with choosing the right focus areas, and finding the right expressions?

My earlier solution to this was AI sparring. The AI chats worked great for evaluation, but the workflow was still slow.

I had interviewed two managers when creating the letter concept. Thus the “product” was good, but the workflow less successful.

The Letter editor

I wanted an agent that edits instead of writing from scratch because the interviewees wanted to hear your own voice. I had also found myself copy-pasting old letters because the quality had reached a plateau.

An editing based workflow maintains your own voice because you’ve actually written all the text. Machine learning is great at matching patterns between texts, though.

Agent reading job posting and canonical letters before starting

The paragraphs and the full sentences of manually written letters are reused. Claude is allowed to substitute company names, roles, and team names, but must otherwise stick to the original phrasings. When the user finishes a letter, it’s added to the set of source letters.

The agentic workflow

The agent reads the job posting, the company background research, and the “canonical” source letters. Then it proposes four full paragraph candidates per round (image below).

Four paragraph candidates shown side by side in one round

Claude is made to print the whole letters to the chat with forceful instructions. Then the user can just use gut feelings and read through. After five or six rounds, the agent evaluates letter-role fit and flags anything missing or overrepresented.

Iterating on paragraph choices across rounds

The final letter is run to Figma through a design system with dedicated components and tokenization. A custom wrapper skill is required to share learnings across agents how the Figma MCP server works. Having printed the letter to Figma, Claude evaluates the visual output and runs an improve-evaluate loop until the design’s flawless.

Finished letter in Figma with correct typography and hyperlinks

An agentic workflow is intelligent and flexible, so you can also rewrite parts of the texts when you want.

Self-repairing rules

I still improve the workflow while writing letters. So, the workflow has the meta levels of self-reflection and of instructing Claude to self-repair the instructions.

Agent announcing a skill file update before Figma export
VS Code and terminal side by side, git commit of skill update visible

Results

Writing three letters in the time of one saves time for research. This helps you to better understand the target companies.

I also use saved time for content improvements. For example, the letter in this article is for an agentic design role, where I didn’t have pre-written paragraphs. Even then, I could finish the letter in the time it would have taken me to write one letter earlier.

The new way of writing also creates less cognitive load. It produces fewer expectations and more insights. It lets you run another job in parallel when waiting for Claude to create and print its output.