--- name: provenance-check description: Perform provenance check on a draft resume against comprehensive work histories disable-model-invocation: true --- ## Configuration Read `.jobops/config.json`. If missing, stop with: > JOBOPS NOT CONFIGURED > Run /jobops:setup to initialize your workspace. Use `config.directories.` for all file paths in this skill. Use `config.preferences.cultural_profile` if this skill generates resume-style content. Use `config.preferences.default_jurisdiction` if this skill has jurisdiction-sensitive logic (crisis/legal skills accept `--jurisdiction=` to override). ## Templates For each template used by this skill, resolve the full path as: {config.templates.base_dir}/{config.templates.active.}/ Templates referenced by this skill: evidence_verification_framework ## Application Path Resolution This skill writes to a per-application folder. Before writing any output: 1. Parse `{Company}_{Role}_{YYYYMMDD}` from the job-posting filename, or honor `--app=` if supplied. 2. Compose the app folder: `{config.directories.applications_root}/{app_slug}/`. 3. Resolve this skill's sub-folder by category: - resume-development (buildresume, provenance-check) → `resume/` - cover-letter (coverletter) → `cover-letter/` - rubric / assessment (createrubric, assessjob, assesscandidate, auditjobposting) → `assessment/` - briefing / interview prep (briefing, interviewprep) → `interview/` 4. If the app folder does not exist, `mkdir -p` it, then copy `{config.directories.job_postings}/{filename}` → `{app_slug}/job_posting.md` so the pinned JD cannot silently change under completed work. 5. Exact-slug collisions (same Company+Role+Date) are not auto-suffixed. If the folder already contains the same output type, require the user to pass `--app=`. ## Step 1: Loading Source Materials I'll first load all your comprehensive work histories from the {config.directories.resume_source} to use as the source of truth: **Source Documents**: All files in `{config.directories.resume_source}/` ## Step 2: Reading Draft Resume Now reading the draft resume to analyze: @$1 ## Step 3: Running Provenance Analysis I'm launching the step2-provenance-check agent to perform a comprehensive provenance analysis. This will: ### Analysis Scope: - **Evidence Verification**: Cross-reference every claim against master resume documentation - **Quantitative Accuracy**: Verify all metrics, numbers, and percentages - **Timeline Consistency**: Check date ranges and chronological accuracy - **Technical Claims**: Validate technology and skill assertions against documented experience - **Geographic Scope**: Verify location and jurisdiction claims - **Team/Budget Claims**: Confirm management scope and financial figures ### Risk Assessment Categories: - **High Risk**: Claims that could be easily challenged or verified as false - **Medium Risk**: Assertions lacking sufficient evidence or specificity - **Low Risk**: Minor issues or confidentiality concerns ### Deliverables: 1. **Detailed Risk Report**: Categorized list of all credibility issues 2. **Evidence Mapping**: Line-by-line verification against source materials 3. **Recommendations**: Specific fixes for each identified issue 4. **Defensibility Score**: Overall assessment of resume credibility The analysis will use the CV Provenance Hardening methodology to ensure your resume can withstand scrutiny during: - Background checks - Reference verification - Technical interviews - Behavioral interviews ## Output The provenance analysis will be saved with detailed findings including: - Specific line references to issues in the draft - Cross-references to supporting evidence in master documents - Actionable recommendations for each credibility concern - Priority ranking for addressing issues Start the report with: ```yaml --- draft_file: $1 generated_by: /provenance generated_on: output_type: resume_provenance status: analysis version: 1.0 --- ``` Update timestamps and `version` when re-running. This analysis ensures your resume maintains competitive positioning while being completely defensible under scrutiny.