// 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 normalized resume material is ready and must be rewritten, organized, and assembled into a 1-2 page LaTeX resume without inventing facts.
Use when creating, rewriting, or converting a source-backed 1-2 page resume from chat, documents, PDFs, images, or mixed artifacts.
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-intake-and-extraction |
| description | 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. |
Normalize messy resume input into traceable working material. Extract first, map claims second, and stop before drafting when the source cannot safely support a concise 1-2 page resume.
.docx.pdfresume-crafter workspace that already has input/ and work/ directories.input/ and work/ exists, invoke or resume resume-crafter, or return a blocker asking for a workspace before writing files.docx for .docx inputs.pdf for .pdf inputs.work/extracted.md.work/requirements-summary.md.work/claim-source-map.md; authoring must later update this map to cover the final rendered resume claims.Mark each usable or requested fact as:
resolvedneeds-confirmationomitted-unresolvedmissing-blockingLegacy confidence labels may appear inside notes, but the state above controls whether drafting can proceed.
Use [confirm] only for needs-confirmation items in working notes. Do not use [confirm] to bypass missing-blocking, and do not allow [confirm] or needs-confirmation claims in final resume prose.
Final 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.Treat an uncertain fact as quality-critical when it affects identity/display name, localized name, target role/headline, required or user-visible contact-block choices, required photos, required language/style, user-explicit deliverable requirements, or any content whose omission would make the resume visibly worse or mismatched.
Quality-critical unknowns must be marked missing-blocking, not needs-confirmation, until the user confirms them or explicitly approves omission. Do not downgrade them merely to keep drafting moving.
Record the exact targeted question that should be asked in work/requirements-summary.md. Use a brainstorming-style question: clarify the purpose or constraint, ask one question at a time when it affects the next decision, and offer concise options when helpful.
Use this six-column table in work/claim-source-map.md:
| Claim | Source artifact | Source locator | Raw wording or user confirmation | State | Final handling |
|---|---|---|---|---|---|
| Candidate held role X at Y | input/source.pdf | p.1, experience section | "Role X, Y" | resolved | use |
| Led deployment for Z users | input/screenshot-01.png | visible project card, metric partly cropped | visible wording unclear; ask user to confirm Z | needs-confirmation | ask or keep out of final prose with working-note trace |
| Chinese display name for a Chinese resume is unknown | input/source.tex | header/name line | source only says LI Baichuan; ask user how to display name in Chinese resume | missing-blocking | ask before drafting |
This intake map covers source facts and uncertainties. After the final resume prose is drafted, resume-authoring-and-assembly must update the table so every final factual claim has a resolved row.
For every intentionally omitted blocking item, record in work/requirements-summary.md:
When the user answers clarification questions after intake:
work/extracted.md with the confirmation wording and date/context of the answeruser confirmation in work/claim-source-map.mdmissing-blocking or needs-confirmation to resolved only when the answer directly supports the final claimneeds-confirmation; keep unresolved quality-critical or blocking uncertainty as missing-blocking unless the user explicitly approves omission; do not silently delete unresolved rowswork/requirements-summary.md so resolved blockers, remaining blockers, and omission audits stay currentIf helpful, also label extraction snippets as commentary only:
high-confidencelow-confidencemissing-blockingLegacy high-confidence and low-confidence commentary never controls final output eligibility. The Confidence States above are authoritative.
work/.skills/, templates/, or other repository paths.