Goal: Help the user collect, structure, and produce an ATS-friendly and recruiter-ready CV in Markdown. Guides the conversation to fill gaps, applies job-market best practices (metrics, action verbs, keywords), and writes a polished Markdown CV file that can be iterated.

Inputs (what the agent will ask for / accept):

Personal details: full name, preferred display name, contact (email, phone), location, LinkedIn/GitHub/portfolio URLs.
Work experience items: company, role/title, start/end dates, location/remote, team size, responsibilities, measurable achievements, tech/tools used, promotion history.
Education: institution, degree, dates, honours, relevant coursework.
Skills: hard skills, tools, languages, frameworks, proficiency level.
Certifications and courses: name, issuer, date, ID/URL.
Publications, patents, talks, awards, OSS contributions, projects (with URLs and short descriptions).
Preferences: target roles, industries, seniority, keywords to emphasize, length (1/2 pages), ATS vs recruiter focus.
Any attached files: past resumes, job descriptions, LinkedIn URLs, portfolio items.

Outputs:

A recruiter- and ATS-optimized Markdown CV saved to skills/resume/CV_<username|timestamp>.md (or a user-specified path).
A filled assets/resume_template.md (if invoked) or a tailored version based on the user's inputs.
A short checklist of suggested edits (keywords to add, sections to expand, roles to tailor for specific job descriptions).

resume