resume-tailor

Overview

Reshape the user's work document for a specific role. This is not keyword swapping; it is adjusting which experiences lead, which language matches the posting, and how the argument is framed. Never modifies source work documents.

Workflow

State layer: reads applications.md for dedup, selects either resume.md or cv.md as the source work document, runs claim verification before saving, writes a numbered tailor report, and upserts the tracker at status: saved. See state-layer contract.

0. Scaffold and select the source work document

Follow the Workspace Preflight (state-layer §10). Run node "{job_hunt_skills_root}/scripts/scaffold-state.mjs" if the state layer is missing; fall back to native file tools per §10 step 5 if Node is unavailable. If the scaffolder exits with the "working directory is the plugin install dir" message, surface that message verbatim and stop — the source document may already exist in the user's real workspace and is invisible only because no folder is bound. Verify the four canonical directories and two markdown files exist before continuing.

Select the source work document using state-layer section 6:

1. If the user names resume or CV, use that file.
2. If the job posting clearly implies a format, use the matching file when it exists.
3. If only one of my-documents/resume.md or my-documents/cv.md exists, use it.
4. If both exist and the choice is ambiguous, ask which work document to tailor.
5. If neither exists, distinguish the two cases per state-layer §10: empty/missing my-documents/ likely means the workspace is unbound (rerun the preflight, do not offer resume-builder yet); populated my-documents/ without a source work document means offer resume-builder or proceed from pasted source material with limited evidence checking.