Career Transition Roadmap Prompt

Create an evidence-based career transition roadmap from the following inputs.

Required inputs:
- Transition objective: [Transition goal]
- Career history, transferable experience, education, and current employment status: [Career background]
- Roles, functions, industries, seniority levels, or geographies under consideration: [Target role options]
- Financial runway, location, accessibility needs, schedule, risk tolerance, compensation floor, and other boundaries: [Constraints and non-negotiables]
- Resume content, portfolio items, work samples, quantified outcomes, credentials, references, and other available proof: [Evidence inventory]
- Relevant job descriptions, salary data, employer research, labor-market reports, interview feedback, or professional conversations: [Market evidence]
- Target date and realistic hours available each week: [Timeline and weekly capacity]
- Conditions that would make the transition successful: [Success criteria]

Input gate and evidence rules:
1. Treat the career background, evidence inventory, and market evidence as supplied information, not independently verified truth. Separate documented facts, self-reported claims, assumptions, hypotheses, conflicting evidence, and unknowns.
2. The blocking minimum is a transition objective, a usable career background, at least one target-role direction, material constraints, and timeline or capacity. If any of these are absent or materially contradictory, ask no more than five consolidated clarification questions and do not present a finalized roadmap. You may provide a clearly labeled preliminary framework that preserves the unknowns.
3. Helpful but non-blocking inputs include job postings, compensation sources, performance evidence, portfolio artifacts, prior interview feedback, network strength, and preferred learning methods. If these are unavailable, identify the resulting confidence limits and add collection tasks to the roadmap.
4. Do not invent employers, credentials, achievements, salary figures, hiring demand, skill proficiency, network relationships, project results, or personal motivations. Never convert an intended activity into a completed one.
5. Use current market claims only when supported by supplied sources or by browsing that is actually available in this ChatGPT session. Cite URLs, publishers, and access dates for browsed evidence. If browsing is unavailable, work from the supplied material and mark external validation as pending rather than relying on presumed current knowledge.

Roadmap method:
1. Define the transition decision. Convert the objective into a decision statement that identifies the starting point, intended destination, target geography or work arrangement, timing, constraints, and measurable success conditions. Surface conflicts such as compensation versus speed, seniority versus evidence, or geographic flexibility versus market size.
2. Establish the baseline. Summarize transferable capabilities, domain knowledge, leadership scope, credentials, work preferences, and demonstrated outcomes. For every important capability, distinguish possession of a skill from credible evidence that another person could inspect.
3. Compare target-role options. Build a weighted scorecard using criteria relevant to the supplied objective, such as demonstrated fit, evidence strength, gap severity, market signal, compensation compatibility, transition time, accessibility, personal constraints, and downside risk. Explain the weighting and show how uncertain evidence affects the result. Recommend a primary path, a fallback or adjacent path, and any option that should be deferred.
4. Reconcile role requirements with market evidence. Extract recurring responsibilities, tools, domain knowledge, credentials, seniority signals, and outcome expectations from relevant job descriptions or other sources. Count patterns only within the material actually inspected. Where practical, seek a validation sample of at least ten recent relevant postings across three employers; if the market is too niche or the evidence set is smaller, disclose the limitation instead of implying broad coverage.
5. Build the skill-and-evidence map. For each high-priority requirement, record current capability, supporting artifact or example, evidence quality, confidence, gap type, and response. Distinguish true skill gaps from terminology gaps, recency gaps, experience gaps, credential filters, weak proof, and weak positioning. Do not recommend training when reframing or stronger evidence would solve the problem more efficiently.
6. Select a bridge strategy. Compare direct application, adjacent-role entry, internal transfer, contract or volunteer experience, credentialing, and proof-of-work routes where applicable. Evaluate time, cost, opportunity cost, signaling value, probability of useful feedback, and reversibility. Do not assume that unpaid work, expensive education, or a lower salary is necessary.
7. Design proof-of-work projects. Specify only projects that demonstrate requirements important to the selected role. Each project must name the employer-relevant claim it supports, intended audience, artifact, scope, source data, completion criteria, review method, estimated effort, and privacy or intellectual-property boundary. Prefer compact, inspectable artifacts over large speculative projects. Never use confidential employer data, proprietary materials, personal customer information, or work the user lacks permission to disclose.
8. Build positioning assets. Draft a target-role value proposition, LinkedIn headline and About-section outline, resume emphasis changes, portfolio structure, and three interview-story outlines. Tie every statement to supplied evidence. Preserve placeholders or evidence-needed notes where metrics and outcomes are unknown; do not fabricate polished achievements. Adapt language to the selected role without falsely inflating title, seniority, ownership, or proficiency.
9. Plan market validation and relationship development. Define informational-interview questions, networking segments, outreach drafts, application experiments, and feedback capture. Distinguish relationship building from transactional requests. ChatGPT may draft messages and plans but must not claim to contact people, submit applications, edit profiles, publish content, enroll in courses, make purchases, or accept offers.
10. Sequence the transition. Produce a weekly plan that fits the stated capacity and dependencies. Include research, evidence collection, skill development, proof projects, positioning, outreach, applications, interview practice, and review gates as appropriate. Reconcile estimated hours with weekly capacity and identify what should be reduced if the plan does not fit.
11. Define decision gates. Include explicit points for continuing, narrowing, pausing, or changing the strategy based on evidence such as response quality, interview conversion, recurring objections, project review, compensation findings, or changes in personal constraints. Avoid treating application volume alone as proof of progress.
12. Stress-test the plan. Address likely failure modes, including selecting a role from aspiration rather than evidence, overtraining, building irrelevant portfolio work, disclosing confidential information, relying on stale market claims, underselling transferable experience, applying before positioning is coherent, networking without a clear learning goal, burnout, and making irreversible financial or employment decisions too early.

Authority, privacy, and safety boundaries:
- Produce analysis, drafts, recommendations, and a proposed roadmap only. The user retains authority over profile edits, publication, outreach, applications, purchases, credential enrollment, compensation decisions, resignation, relocation, and offer acceptance.
- Flag decisions involving material spending, debt, immigration or licensing requirements, benefits, contract terms, discrimination concerns, or resignation for qualified human review where appropriate. Do not present career planning as legal, immigration, mental-health, or individualized financial advice.
- Minimize personal data. Recommend removing addresses, identification numbers, private contact details, health information, confidential employer information, and third-party personal data before material is shared with ChatGPT.
- Stop and request clarification when target options are irreconcilable, essential claims conflict, a proposed artifact may breach confidentiality, or the roadmap would depend on an unverified high-consequence assumption.
- Keep editable drafts and source references so claims can be corrected. Place human approval gates before any public, financial, contractual, or employment action.

Required deliverable:
A. Decision brief
- Transition decision, primary target path, adjacent fallback path, timing, central rationale, major constraints, and confidence level.
- A short register of supplied facts, assumptions, unknowns, conflicts, and validation priorities.

B. Target-role decision scorecard
- One row per option with weighted criteria, score rationale, evidence source, uncertainty, major trade-off, and disposition: pursue, validate, defer, or reject.

C. Market requirement synthesis
- Requirement or signal, observed frequency within inspected sources, representative source references, relevance to the target, evidence limitations, and implication for the roadmap.

D. Skill-and-evidence matrix
- Role requirement, priority, current capability, proof artifact or example, evidence strength, confidence, gap type, gap severity, and recommended response.

E. Bridge strategy
- Chosen route and alternatives, expected signaling value, time, cost range if supported, opportunity cost, reversibility, dependencies, and decision rationale.

F. Proof-of-work portfolio plan
- For each project: supported role claim, audience, deliverable, permitted source material, scope exclusions, milestones, estimated hours, acceptance criteria, reviewer or feedback route, and confidentiality check.

G. Positioning kit
- Evidence-grounded value proposition, draft LinkedIn headline, About-section outline, resume emphasis changes, portfolio narrative, and three interview-story outlines with situation, action, result evidence, relevance, and missing-proof notes.

H. Networking and application experiments
- Segment or channel, learning objective, proposed message or action, personalization input, weekly volume compatible with capacity, response measure, feedback capture method, and adjustment rule. Label every item as proposed until the user supplies execution evidence.

I. Weekly transition roadmap
- Week, intended outcome, actions, estimated hours, dependency, artifact or evidence produced, success measure, decision gate, and contingency. Show total hours per week and reconcile them with stated capacity.

J. Risk and safeguard register
- Risk, early warning sign, probability, impact, mitigation, stop condition, recovery action, and decision owner. Include financial, privacy, confidentiality, reputational, workload, and evidence-quality risks where relevant.

K. Verification and acceptance dashboard
- Check, expected signal, source or method, current observation, status, evidence location, review date, and action if the check fails.
- At minimum, test whether the recommended role is supported by inspected market evidence; priority gaps trace to recurring requirements; every positioning claim traces to evidence; proof projects demonstrate target-role capabilities; weekly hours fit capacity; costs respect constraints; private or confidential material is excluded; and each major assumption has a validation action.
- Use only not assessed, pending, supported, contradicted, or verified as status labels. Reserve verified for a check actually performed with cited evidence. Report unresolved or conflicting results rather than forcing acceptance.

L. Handoff
- List decisions requiring user approval, outstanding questions, unavailable evidence, proposed external validation, and the smallest safe next action that can be completed within the stated weekly capacity.

Completion language:
Keep proposed, drafted, scheduled, attempted, completed, measured, and verified states distinct. Do not say a profile was updated, a person was contacted, an application was submitted, a project was completed, a result was measured, or the roadmap was approved unless the conversation contains direct evidence that the action occurred. When evidence is unavailable, state what remains unverified and what would establish it.