Cover Letter Writer

Every cover letter goes through a rigorous 3-agent debate review process before submission. This isn't about producing generic letters — it's about crafting dense, specific, JD-mirrored arguments for why the applicant is the right fit.

Pre-Flight

If this is the first job-application skill invoked in this session, run the self-check skill first. The cover letter writer needs the user's latest project details, resume, and background — stale data produces generic letters.

Must-Write Rule

If config.cover_letter.must_write is true: whenever the application system allows uploading a cover letter, you MUST write one. No exceptions. Check the application form for a cover letter upload field before skipping this step.

User Background (for content)

Read from three sources:

1. config.yml — config.projects for structured project data, config.primary_strength + config.primary_strength_evidence for the user's key differentiator
2. Auto-memory (user_background.md) — for detailed project mechanics, narrative arcs, and debugging stories
3. config.registered_files — check for project_doc, portfolio, writing, or certificate type files. Read them for additional material that could strengthen the cover letter. For example, a portfolio PDF might have project details not captured in config.

The config provides the facts; the memory provides the storytelling material. Use both.

Writing Standards

What makes a great cover letter:

1. Mirror JD language exactly. If the JD says "Cursor and Codex," use those exact words in paragraph one. If they say "onboarding/offboarding," use that phrase. The reader should feel like the letter was written specifically for their posting — because it was.
2. Specific project mechanics, not generic claims. Never write "I am detail-oriented." Instead: "issuer ID and plan ID as only join key, silent record drops." The specificity IS the evidence.
3. Root cause → fix → lasting improvement arc. Use the user's best debugging/obstacle story from their projects. Adapt it to the JD context. This shows persistence, technical depth, and engineering discipline.
4. Confident day-one action closing. End with what the applicant will DO on day one, not what they hope to learn. Use "I will" or "I am ready to," never "I would be glad to" or "I hope to."
5. Under config.cover_letter.max_words words (default 330). Density beats length. Every sentence must earn its place.

What to avoid:

• Generic personality claims ("I am a hard worker," "detail-oriented," "team player")
• Advanced ML techniques for ops-focused roles — sounds overqualified and disconnected
• Passive language ("glad to own") — use "ready to own" or "I will"
• Stating obvious location info (if user is at a university in the job's city)
• Listing tools as skills without a concrete use case in the body
• Overly long sentences or paragraphs — keep it punchy

Also incorporate any user-specific writing preferences from feedback_cover_letter.md in auto-memory.

Cover Letter Structure

[Header: Name, Email, Phone, Date]
(Use config.personal.* for header fields)

Dear Hiring Manager,

[P1: Hook — connect the user's most relevant experience directly to the JD's
primary need. Mirror JD language. Establish credibility in 2-3 sentences.]

[P2: Debugging/obstacle story — adapt the root cause → fix → improvement arc
to the JD's domain. Show persistence and engineering discipline.]

[P3: Supporting projects — 1-2 more projects that reinforce the match.
Connect to specific JD requirements. Technical specifics, not summaries.]

[P4: Motivation + day-one action — why this specific role/company excites
the user, and what they will do immediately upon starting.]

Sincerely,
[config.personal.first_name] ([config.personal.preferred_name]) [config.personal.last_name]

3-Agent Debate Review Process

After writing the initial draft, spawn three agents in parallel:

Agent 1: Advocate (Opus)

You are the Advocate reviewing a cover letter for a job application.

Your job is to identify and defend the letter's STRENGTHS:
- Where does it effectively mirror JD language?
- Which specific details are most compelling?
- How well does the narrative arc work?
- Is the closing strong and actionable?

Score the letter 1-10 and explain what's working. Be generous but honest —
if something is mediocre, don't call it great.

JD: [paste JD]
Cover Letter: [paste draft]
User's Background: [paste from user_background.md and config.projects]

Agent 2: Devil's Advocate (Opus)

You are the Devil's Advocate reviewing a cover letter for a job application.

Your job is to find WEAKNESSES and GAPS:
- What JD requirements are NOT addressed?
- Where is the language generic instead of specific?
- Are there any claims without evidence?
- Does anything sound overqualified or disconnected from the role?
- Is the word count under 330? Is every sentence earning its place?
- Would a hiring manager for THIS specific role be convinced?

Score the letter 1-10 and list the top 3 most important improvements.
Be tough but constructive.

JD: [paste JD]
Cover Letter: [paste draft]
User's Background: [paste from user_background.md and config.projects]

Agent 3: Judge (Sonnet)

You are the Judge synthesizing two peer reviews of a cover letter.

You will receive an Advocate's defense and a Devil's Advocate's critique.
Your job is to:
1. Weigh both perspectives fairly
2. Give a final score (1-10)
3. Identify the single most important improvement that would raise the score
4. Decide: is this letter ready to submit, or does it need another round?

Threshold: both Opus critics should score 8+ before submission.

JD: [paste JD]
Cover Letter: [paste draft]
Advocate Review: [paste]
Devil's Advocate Review: [paste]

Iteration Rules

• Run all 3 agents in parallel for speed
• After receiving feedback, revise the draft addressing the top issues
• Re-run the debate until both Opus agents score >= config.cover_letter.score_threshold (default 8)
• Max config.cover_letter.debate_rounds_max iterations (default 3) — if scores plateau, present to user for final decision
• Track version numbers (v1, v2, v3...) so user can see the progression

PDF Generation

After the cover letter is finalized, generate a PDF using reportlab:

# Use config.cover_letter.font (default Times-Roman), letter size, 1" margins
# Header: Name centered, email | phone | date below (from config.personal.*)
# Body: justified text, proper paragraph spacing
# Save to: [config.files.cover_letter_dir]/[Company]_CoverLetter_[LastName].pdf

The PDF filename pattern: [Company]_CoverLetter_[config.personal.last_name].pdf