compare-versions

Renamed: compare-versions was compare-resume-versions before v1.0.0 (see RIT-A-0005).

Inputs must be canonical JSON. This capability consumes a resume as a ResumeDocument JSON (build it from a PDF/DOCX/MD/text file with the parse-resume skill) and, where a job is involved, a JobDescription JSON (build it with parse-job so skills-coverage scoring works). Run those conversions in subagents, then pass the saved JSON paths here — they live under resume-kit/resumes/ and resume-kit/jobs/.

Prerequisites

Run the shared Prerequisites gate first — see _shared/prerequisites.md.

• Required inputs: two ResumeDocument JSONs (base vs candidate) and a JobDescription JSON (config.json active_job or an explicit path).
• If missing: STOP and name the upstream skill — any missing resume JSON → run parse-resume; missing job JSON → run parse-job.

Purpose

Produce a ResumeComparisonResult that shows how two resume versions differ in their job fit — useful for deciding whether a revised resume is an improvement.

When to use

• After editing a resume, to verify the new version scores better than the original.
• When a user wants side-by-side analysis of two variants before choosing which to submit.

Inputs

Field	Type	Notes
base	ResumeDocument	The reference (original) resume
candidate	ResumeDocument	The version being compared
job	JobDescription	The target job
base_label	str	Human label for base (default: "base")
candidate_label	str	Human label for candidate (default: "candidate")

Options (CapabilityOptions)

Option	Default	Effect
strict	false	Escalate advisory warnings to failures

no_llm has no effect — this capability is always deterministic.

How to invoke

CLI

resume-tool compare --base <base.json> --candidate <candidate.json> \
    --job <job.json> \
    [--base-label "original"] [--candidate-label "revised"] \
    [--output {json,text,md}] [--strict]