Resume Tailor

Take a job description and a career profile, produce a tailored resume in markdown, .docx, and .pdf. The whole workflow is roughly 15 minutes for a user who already has a profile. The skill orchestrates: JD analysis → gap scorecard → minimal targeted discovery → draft → ATS pass → render → optional git commit.

Why this skill exists separately from career-profile-builder

The profile interview is exhausting and only happens occasionally. The tailoring workflow is fast and happens dozens of times. Different cadences, different mental models. Mashing them together means recurring users get re-asked profile questions every time, which is the worst-of-both-worlds.

This skill assumes the profile already exists. If it doesn't, the skill stops and points the user at career-profile-builder — it does not try to do a profile interview from inside a tailoring session.

Output contract

For each tailoring session, the skill produces (in the user's chosen working directory):

1. resume_<JD-ID>.md — the canonical source-of-truth for this tailored version
2. resume_<JD-ID>.docx — pandoc-rendered, ATS-friendly (the recruiter / ATS upload format)
3. resume_<JD-ID>.pdf — for emailing to humans (the "looks good in preview" format)
4. resume_<JD-ID>.html — the intermediate (kept around because it's free and useful)