Provenance Check

Configuration

Read .jobops/config.json. If missing, stop with:

JOBOPS NOT CONFIGURED Run /jobops:setup to initialize your workspace.

Use config.directories.<key> 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=<ISO-3166-2> 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=<slug> if supplied. The slug MUST be canonical: a leading PascalCase {Company} token (matching the Company_Intelligence/{Company}/ folder so OSINT links), a PascalCase {Role} (underscores between words allowed), and a trailing compact 8-digit date (20260519 — no hyphens, no time). Reject leading date/time prefixes such as 2026-04-15_214414_...; if the source filename carries one, recompose it into canonical form ({Company}_{Role}_{YYYYMMDD}) before composing the folder path.
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. Ensure the pinned copy begins with YAML front matter carrying output_type: job_posting: if the source JD already has a front-matter block, add the key to it; otherwise wrap a new block (--- / output_type: job_posting / source_jd: {filename} / ---) above the JD body.
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=<distinct-slug>.
6. Output filename (fixed; only the sub-folder above is resolved dynamically): write the provenance analysis to resume/step2_provenance.md.

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 is saved to {app_slug}/resume/step2_provenance.md (step 6 of Application Path Resolution). I pass that resolved absolute path, along with the draft path $1, to the step2-provenance-check agent in its Task instruction. It includes detailed findings:

• 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:

---
draft_file: $1
generated_by: /provenance
generated_on: <ISO8601 timestamp>
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.