Experience

---
name: career-experience
description: Build a confirmed experience knowledge base from historical CVs, evidence and a supportive resumable interview before producing a general CV.
---

# Experience intake

Use `prompts/intake.md`. Store originals and notes in the selected external private workspace. Ask permission to use supplied material and record disclosure limits. Do not demand a CV: a plain-language narrative is an equally valid starting point.

## Intake sequence

1. Request several CV versions from different periods, authorized reference/education/portfolio/publication materials and any existing professional profile. Record each source's type, hash, date, authorship, confidentiality and extraction status. A polished CV is a set of assertions, not proof.
2. Extract a provisional chronology with roles, projects, education, publications, skills, methods, outcomes and uncertainties. Preserve source attribution at fact level. Compare overlapping assertions: title, dates, personal ownership, numbers and delivery status. Keep disagreements visible rather than choosing the strongest wording.
3. Ask the person to describe one experience in ordinary language. Work through every substantive role/project using context → personal action → method → result → evidence. Save progress and unanswered questions after each session. Reuse confirmed answers.
4. Probe contribution without diminishing it: who asked for the work, what did you personally decide/build/write/research/organize, what changed, who used it, how was it assessed? Ask for measured outcomes, before/after, volumes, budget, deadlines, reach or quality evidence where appropriate. Distinguish team totals from individual contribution and observed effects from estimates. If no number is known, keep a specific qualitative result.
5. Confirm facts and safe claims with the person, focusing on conflicts, critical role skills and implied seniority/ownership. Candidate confirmation is valid evidence. A confirmed absence closes a question; an unknown remains unknown. Prototypes, assistance, courses and collaborations retain their qualifiers.
6. Create variants using `claims.md` and recurring answers using `prompts/application-answers.md`. Record prohibited interpretations and confidentiality labels.
7. Collect authorial samples with `prompts/voice.md`. Offer two or three relevant structure previews, obtain template choice, then generate a general CV through `skills/documents/SKILL.md`. Deliver the inspectable KB and durable CV before activating a search campaign.

## Supportive interviewing

Say what is already supported: “You designed the study and interpreted its results; we can state that directly. What decisions were yours?” Offer stronger evidence-bounded verbs instead of inflated titles. Avoid asking the person to invent a percentage or treating missing documents as a failure. Ask one focused set at a time; do not force a long questionnaire in one sitting.

Exit only when each included claim has resolved evidence/confirmation, remaining questions are listed, and the general CV passes required gates. Unsupported material may stay in private notes, never in sent documents.