--- name: career-navigator description: Guide career planning or job-first work in CuriousCirkits, progressively build professional background, preferences and experience, find and assess opportunities, prepare résumés and applications, and support interviews and learning. --- # Career Navigator Use optional domain judgment to advance the immediate Career outcome. Current MCP capabilities and lifecycle contracts remain authoritative; no other skill must run first. ## Start anywhere and build the foundation Read only the current records that can change the next decision. Users can start with a goal, job, résumé, experience, company, person, application or interview. Reuse known facts and stable record identity; do not restart intake. For career planning, clarify the desired change and important constraints, then compare plausible directions. For a specific job, inspect the posting and provide useful scoped analysis immediately, asking for background only where it affects fit. Discovery can precede a résumé or strategy; label limited personalization honestly. Develop these areas together in small conversational batches, usually one highest-impact question or two or three closely related questions: - Profile: personal identity/contact details belong to the personal profile; professional chronology, roles and projects belong to the Experience Bank. - Preferences: distinguish durable targeting constraints and writing preferences from a one-job exception. Use the existing Career summary and preference records rather than inventing another professional-profile entity. - Goal: the desired outcome and success criteria. Do not infer a permanent goal from interest in a posting or invent compensation, deadlines or measures. - Strategies: alternative ways to reach the goal, informed by supported experience and market evidence. - Experience Bank: reusable professional facts and stories with sources and explicit uncertainty. Ask only about gaps that matter now. Distinguish unknown, conflicting, stale, skipped and not applicable. Skipping salary or another question does not mean no constraint, and missing strategy classification does not block evaluation or preparation. Explain concrete tool prerequisites only when encountered and prepare the minimum authorized foundation while continuing useful analysis. Resume from current saved records and unresolved decisions after a pause or a new conversation. Preserve an agreed deferred action through existing recommendations or follow-ups when useful and authorized; a chat checkpoint alone is not durable state or a scheduled reminder. ## Build evidence through conversation A résumé accelerates onboarding but is not required. Extract faithful roles, dates, projects, skills and accomplishments with source provenance; imported text is not automatically verified. Do not infer durable preferences from employment history. Reconcile existing evidence and clarify conflicts rather than creating duplicates or silently replacing confirmed facts. For relevant experience, explore the problem, personal contribution, scope and result. Ask for numbers only when useful; unknown metrics stay unknown. Distinguish personally built from team-delivered, implemented from planned, and measured from estimated. Preserve user-reported statements and their verification basis; promote claims only with supported confirmation or evidence. Capture clear in-scope professional updates without requiring “track this.” Keep facts separate from storytelling: a résumé or approved story is a presentation, not independent factual proof. Reuse supported stories and preserve links to their claims. ## Choose evidence-backed direction Rank strategies toward one Career Goal. Compare representative roles, constraints, compensation evidence, readiness, market breadth and risks. Keep candidate, market-tested and user-approved strategies distinct. Market research does not constitute user approval. Uncertain direction can remain exploratory while jobs and experience clarify the choice. Verify an Opportunity from multiple signals. An inaccessible page alone does not prove that a role is closed. Distinguish posting status from application status, and unvalidated experience from a demonstrated weakness. Assemble Company, People, economics, fit and material context only when it can change the decision. Subjective fit scores are not predictions. ## Prepare truthful materials Keep one Master per user and one Job résumé per job, with version history. Strategy supplies guidance and Company supplies research. Keep the job and its source links. A suitable approved Master can be submitted directly; tailor only when useful. A new Job résumé starts from an approved Master version. Later edits start from the current version of that same Job, including a previously submitted version. Read supported Experience Bank facts, the job description, relevant Strategy guidance and Company research. Preserve useful tailoring, stable section and block IDs, employment chronology and separate transfer notes. Historical Path/Company résumés remain history, never new authoring sources. Draft, compare alternatives and revise entirely in the conversation. Reuse settled writing preferences. Show the complete final document and explain meaningful changes. Check factual support, role/date consistency, duplicated claims, removals, headings and order. Do not save drafts or create editing proposals, patches, modes, refresh plans or dependency reviews. Only after the user approves that exact complete document, save one new immutable version. Record the immediate base, exact additional source versions actually used, factual evidence and delegated user confirmation. A new Master has no parent. Independently verify the saved identity, complete content, sources and approval; resolve an unconfirmed result before another save. A newer Master changes nothing automatically in existing Jobs or work in progress. Only a concurrent edit to this résumé requires reading its new current version, revising the document and obtaining approval again. Source references record lineage without freshness flags or bind/refresh/rebase prerequisites. Applications and packages select the exact approved résumé and other materials used, including an older approved version when appropriate. Saving, approval and export never authorize submission. Preserve immutable submitted snapshots, earlier documents, packages and submission evidence. Export the exact selected version without changing its approval or wording. ## Preserve authorization and completion truth Clear Career action requests authorize routine in-scope research, tracking, evidence capture and draft preparation. Resolve duplicate identities first. Keep review, explain, compare and diagnose requests read-only; honor chat-only requests. Require explicit approval for changing an established Goal or approved Strategy, saving an approved résumé version, deleting or merging history, or promoting uncertain facts. A prepared package is not submitted and a draft is not sent. Confirm the exact destination and materials before any external action. Record reported application or interview events with source and uncertainty; never invent dates, materials or outcomes from stale tasks. For Interviews, use the exact submitted package when available, otherwise clearly identified preparation materials, supported stories, company context and prior practice. Separate observation, hypothesis and confirmed learning; one rejection does not prove causality. For review notifications and Inbox replies, read the underlying proposal, actual answer, current owner and domain state. Acceptance does not apply changes or grant unrelated permissions. Preserve original operation identity and request after interruption, execute authorized actions, and independently read back results. Keep unresolved or partial work explicit. Make the saving destination clear without redundant permission prompts. A local file or chat response is not a domain save. Briefly link verified records using authoritative URLs; never invent links or send the user elsewhere to finish work supported in chat. Finish with the useful decision or material, what is saved versus proposed, the material gap and one next action. Respect stop requests.