Tailor Résumé to a Posting
Adapt an EXISTING résumé to a specific job posting — a fit map of must-hit requirements first, then a tailored variant that re-orders and re-words real experience without inventing any. Distinct from building a résumé from scratch (see Résumé / CV): this book starts from a base résumé plus a posting and produces the targeted variant along with honest gap notes for the cover letter and interview. Use per serious application in a job search.
Steps
Entry step: fit-map. Each step names the specialist role it wants; the full working prompt is expandable.
- Map the fitplannerentry
must-hit requirements classified strong / partial / gap against the base résumé
Show working prompt
Map the posting against the real résumé before touching a word. Step 1: locate the base résumé and the job posting in the workspace or project documents; if either is missing, ask for it briefly and stop until provided. Step 2: extract the posting's must-hit requirements and keywords — the skills, experience markers, and phrases a screener will scan for. Step 3: classify EVERY must-hit item against the base résumé: strong-match (already evidenced), partial (evidenced but buried or under-worded), or GAP (not evidenced — and it stays a gap; inventing experience is forbidden). Step 4: decide the tailoring moves for each strong/partial item — which bullet moves up, which summary line changes, which keyword gets woven where. Step 5: write an explicit '## Gaps' section listing every unmet requirement with how to address it honestly in the cover letter or interview instead. Step 6: close with an acceptance-criteria checklist ('every must-hit addressed or consciously in Gaps', 'no invented experience', 'page count unchanged or lower', 'summary rewritten for THIS role'). Write the fit map + checklist via write_task_note AND to notes/fit-map.md. - Tailor the résumécopywriter
the tailored variant — re-ordered, re-worded, nothing invented
Show working prompt
Produce the tailored variant as resume-tailored.md, working strictly from the base résumé and the fit map. Step 1: rewrite the professional summary to target this posting, weaving must-hit keywords naturally. Step 2: re-order experience bullets so the most relevant impact leads each role; re-word partial matches to surface the evidence the posting asks for — same facts, sharper framing. Step 3: cut or compress roles and bullets irrelevant to this posting rather than exceeding the base résumé's page count. Step 4: NEVER invent experience, titles, dates, or metrics — a gap identified in the fit map stays a gap. Step 5: keep the base résumé's format conventions (headings, date style) so the variant is drop-in. On a loop-back, fix ONLY the named issues. Write a short note confirming keyword coverage and page parity via write_task_note.
- Evaluatereviewer
Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
Show working prompt
QA the tailored résumé against the base and the fit map. Step 1: diff-read resume-tailored.md against the base résumé — FAIL immediately on any claim, title, date, or metric that the base does not support. Step 2: check keyword coverage — every strong/partial must-hit from the fit map appears naturally in the variant. Step 3: confirm the page count did not grow and the summary targets the posting's role. Step 4: confirm the Gaps section items were NOT smuggled into the résumé. Write PASS/FAIL per criterion with the specific line for any FAIL. Then route — this is the whole point of the loop: - **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`. - **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "tailor" })` to loop back. The builder fixes exactly those gaps. Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in. - Finishdeveloper
All acceptance criteria met. Stamp a short summary and report DONE.
Show working prompt
Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.
Triggers
Phrases that suggest this craftbook to a crew.
- tailor my resume
- adapt my resume to this job
- resume for this posting
- tailor cv to a posting
Source
View this craftbook on GitHub · MIT license