// Use when creating, rewriting, or converting a source-backed 1-2 page resume from chat, documents, PDFs, images, or mixed artifacts.
Use when normalized resume material is ready and must be rewritten, organized, and assembled into a 1-2 page LaTeX resume without inventing facts.
Use when resume source material arrives as chat requirements, a Word file, a PDF, screenshots, or mixed artifacts and must be normalized before any 1-2 page resume drafting begins.
Use when a LaTeX resume draft exists and needs factual review, ATS or research-resume risk checks, build validation, packaging, and final delivery.
| name | resume-crafter |
| description | Use when creating, rewriting, or converting a source-backed 1-2 page resume from chat, documents, PDFs, images, or mixed artifacts. |
Coordinate a four-skill workflow for mainstream 1-2 page resumes. Clarify blocking unknowns before drafting, keep every claim traceable to source material, and keep all generated artifacts inside one fresh workspace.
.docx, .pdf, images, screenshots, or mixed source files for resume conversion..tex and final .pdf outputs..tex plus .pdf and wants a cleaned or rebuilt resume.Do not produce cover letters, slide decks, portfolios, unrelated document work, or long academic CVs. If the user asks for a long CV, explain that this package targets 1-2 page resumes and ask whether to create a concise research resume instead.
CV_SKILL_ROOT as the absolute path to this skill package.CV_SKILL_ROOT in this order: first use an explicit user-provided CV_SKILL_ROOT if present; otherwise use the known repository/package checkout location if the runtime exposes the loaded skill path or the skills are still installed under the repo; if neither is available, ask the user for the absolute asset root before using bundled templates.CV_SKILL_ROOT.templates/... from the current working directory.resume-workspace-YYYYMMDD-HHMMSS unless the user provides another folder.input/, work/, and output/ inside the workspace.input/ and keep notes, extraction, and drafts under work/.resume-intake-and-extraction before any drafting.missing-blocking items and quality-critical unknowns before authoring.work/extracted.md, work/requirements-summary.md, and work/claim-source-map.md with the user confirmations.resume-authoring-and-assembly only after all missing-blocking items are resolved or audited as omitted with explicit approval.resume-review-and-delivery to review, build, and package the outputs.work/extracted.md: normalized source materialwork/requirements-summary.md: target, template choice, gaps, omissions, and user confirmationswork/claim-source-map.md: every resume claim mapped to source material and confidence statework/resume.tex: draft LaTeX sourceUse this six-column header in work/claim-source-map.md:
| Claim | Source artifact | Source locator | Raw wording or user confirmation | State | Final handling |
|---|
resolved: confirmed and safe to useneeds-confirmation: non-blocking, visible in working notes, not final prose unless confirmedomitted-unresolved: unresolved and intentionally left out of final prosemissing-blocking: blocks drafting or finalizationFinal output eligibility:
resolved: may appear in final resume prose.needs-confirmation: may appear only in working notes, never in final prose.omitted-unresolved: records an intentional omission and must not appear in final prose.missing-blocking: blocks authoring and finalization until resolved or audited as omitted with explicit user approval.Some unknowns are too important to silently omit. If an unknown affects identity, headline, target role, language-localized presentation, required or user-visible contact-block choices, user-explicit requirements, or any content whose omission would make the resume visibly worse or mismatched, mark it missing-blocking and ask a targeted question before drafting.
Do not resolve quality-critical uncertainty by guessing. Do not resolve it by silently deleting the field. Omission is allowed only after explicit user approval recorded in the omission audit.
Use a brainstorming-style question approach: ask questions that clarify purpose, constraints, and success criteria; ask one question at a time when the answer changes the next decision; use concise multiple-choice options when they reduce friction; and batch only the minimal independent blocking facts needed to unblock drafting.
Record every intentionally omitted blocking item in work/requirements-summary.md with:
resolved facts or conservative wording supported by resolved claim-map entries.resolved entry, missing-blocking items are resolved or audited with clear approval, [confirm] markers are cleared, the omission audit is complete, and output/resume.pdf exists after a clean output-local build.skills/, templates/, docs/, examples/, or repo root paths.Unresolved high-risk items must be resolved or audited as omitted with explicit user approval and absent from final prose:
resume-crafter, resume-intake-and-extraction, resume-authoring-and-assembly, and resume-review-and-delivery.docx only when .docx input requires it.pdf only when .pdf input requires it.output/resume.pdf as the required final deliverable, plus corresponding source files output/resume.tex and output/common/resume.cls.resume-review-and-delivery must attempt to install or activate a XeLaTeX-capable environment. If installation or compilation cannot complete, return a blocker; do not present source files alone as final delivery.work/resume.tex and output/resume.tex use \documentclass{common/resume}.work/review.md and work/build.log when review or build runs.resume-intake-and-extraction and update work/extracted.md, work/requirements-summary.md, and work/claim-source-map.md.resume-authoring-and-assembly.resume-review-and-delivery may fix and rebuild if no new facts or scope changes are needed.resume-crafter and do not finalize.