Documents

---
name: career-documents
description: Produce tailored LaTeX and PDF documents with evidence, readable extraction, paired inactive output and every-page visual review.
---

# Document production

## Select content and structure

Read current confirmed facts, approved claims/variants, style, template and campaign policy. For a general CV select representative breadth; for a vacancy extract role, level, duties, must-haves, preferences, hard filters and roughly twenty useful terms. Classify each requirement as direct evidence, honest transfer, confirmed gap or unknown. Do not manufacture ATS scores or use hidden keyword text.

Choose industry, academic or portfolio structure. Offer two or three relevant preview variants with visible differences in section order and emphasis, not only colours. Show expected length and tradeoffs; save the person's selection. Actual call requirements override defaults (anonymity, exact sections, page/word limits, publication style, file type). Explain conflicts before proceeding.

Lead the summary with the target identity in two to four concise lines where suitable. Order skills and achievements by relevance. Use exact truthful terms naturally in summary, skills and the strongest achievements. Retain useful breadth when space allows. Include languages only at confirmed levels. A publication under review is not published. A portfolio is separate supporting evidence, not an image-only substitute for a parseable CV.

## Editorial and build order

1. Produce canonical visible content with claim references and language. Audit dates, titles, metrics, ownership and proficiency qualifiers against evidence.
2. Apply `skills/humanizer/SKILL.md` and `prompts/voice.md`: save draft, brief remaining-tells audit and final rewrite privately. Preserve meaning, metrics, dates and valuable terms; use concise professional wording.
3. Render escaped content to `.tex` and ordinary PDF with useful contact links. By default also create a separate inactive `.tex`/PDF with identical visible wording: no active-link package, links/actions/annotations/scripts/forms/embedded files/images. Never use hidden text or unnecessary active content in either version.
4. Compile with the selected engine and record tool versions. Fix errors, missing glyphs, clipping and overflow. Store source/PDF/extracted text/report durably in the external workspace.
5. Check extracted reading order, contacts, section headings, every role/date/bullet and bold-adjacent spaces. Compare both versions' visible wording. Assert key complete phrases, not merely nonempty extraction. Check ordinary contact links and inactive PDF internals with actual tools.
6. Render and inspect **every page**. Check hierarchy, wrapping, whitespace, density, alignment, orphaned headings, natural role/list breaks and page limits. Add next-most-relevant verified evidence before stretching content to fill a page. Do not force breaks that strand useful space; the final page may end with whitespace.
7. Obtain independent content/fit/visual review through `review.md` and `prompts/document-review.md`. Correct supported material issues, rebuild and repeat affected checks. Explain unsupported findings or optional refinements without endless editorial churn.
8. Run final deterministic Unicode/metadata hygiene. Inspect first; preserve meaningful script controls, characters and typography. If changes occur, recheck wording, extraction, rendering, links and inactive internals. Record optional detector/service availability accurately. No universal watermark removal, detector-evasion or human-authorship guarantee.

Eligibility requires actual pass results for mandatory gates bound to the final content/artifact hash. Unavailable checks are unavailable, never pass. Content/layout changes invalidate affected checks. A generated PDF is not ready merely because compilation succeeded.

Pass the selected complete `--profile` and `--workspace` to document builds. Runtime binds each visible factual unit to current claim/fact versions; exact approved wording can be linked automatically. For a rewritten unit supply its JSON-pointer dependency during tailoring. Use direct fact references for header/chronology. Missing/stale provenance prevents production use. Register the exact standard/inactive artifact selected for the CV field; a reviewed bundle cannot authorize another PDF. `documents finalize --workspace` checks freshness; an unrelated fact edit need not invalidate the CV.

Choose the independent agent or human review route early in setup. `documents review-pack` exports exact private page paths, content and hashes. A missing reviewer leaves a draft. With no usable browser/upload route, deliver a reviewed manual-submission package with exact files and form answers instead of claiming automation is ready.

Prepare required letters/statements via `prompts/letters-and-statements.md`. General supporting documents remain distinct from CV/letter fields. Originals must be authorized and preserved without rewriting.