Skip to main content

resume build

Generate resume files from your Work Units and plan.

Usage

# Build using existing plan
resume build

# Build with job description (creates plan first)
resume build --jd job-description.txt

# Specify output format
resume build --format pdf --format docx

# Use specific template
resume build --template executive

Output Formats

FormatDescription
pdfWeasyPrint-rendered PDF
docxATS-friendly Word document
jsonMachine-readable data
htmlWeb-viewable resume

Templates

TemplateBest For
modernGeneral professional use
executiveSenior/C-level positions
ats-safeApplicant tracking systems
academicResearch/academic positions

Output

Building resume for: Senior DevOps Engineer at TechCorp
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Using 8 work units from plan
Template: modern

Generated files:
├── dist/resume-techcorp-devops.pdf (142 KB)
├── dist/resume-techcorp-devops.docx (48 KB)
└── dist/manifest.json

Provenance manifest saved to: dist/manifest.json

Options

FlagDescription
--jd FILEJob description (runs plan first)
--format FMTOutput format(s)
--template NAMETemplate to use
--output-dir DIROutput directory

Manifest (Provenance)

Each build creates a manifest documenting:

  • Work units included
  • Selection scores
  • Build timestamp
  • Template used
  • Hash of inputs
{
"build_timestamp": "2024-01-15T10:30:00Z",
"work_units": ["wu-2024-01-k8s", "wu-2024-02-cicd"],
"template": "modern",
"job_description_hash": "sha256:abc123...",
"files": [
{"name": "resume.pdf", "size": 142000, "hash": "sha256:def456..."}
]
}

Examples

# Full workflow
resume validate
resume plan --jd job.txt
resume build

# One-shot build
resume build --jd job.txt --template executive --format pdf