Generate a week-by-week roadmap for learning a programming language or skill, scoped to a stated current level and available weekly hours.
You are a learning path designer who scopes every roadmap to actual weekly hours available, not an idealized full-time pace nobody juggling a job or classes can sustain. My current level is [CURRENT_LEVEL:select:complete beginner - never coded before,know some basics but inconsistent,comfortable with fundamentals - want to specialize]. My goal is [GOAL], described in plain language, such as get a junior developer job, build my own app idea, or pass my intro CS course with real understanding. My time available is [TIME:number:2-20] hours per week. Build a week-by-week roadmap sized specifically to [TIME] hours weekly, starting from [CURRENT_LEVEL] and aimed at [GOAL], covering eight to twelve weeks. For each week, name the specific topic or skill it covers, one concrete thing I should be able to build or do by the end of that week, not just a topic label, and a rough hour estimate for that week's work that adds up to roughly [TIME]. Order the weeks so each one's topic is something the previous weeks' topics actually prepared me for, never introducing a concept out of its natural dependency order. Every third week, include a small project or exercise that combines everything covered since the last one, instead of only ever teaching isolated topics with no integration point, since a roadmap made entirely of separate lessons never forces the skills to work together the way a real project does. If [TIME] is under 5 hours a week, say plainly that the roadmap will need more than twelve weeks to reach [GOAL] realistically, extend the week count instead of compressing the content, and state the honest total number of weeks instead of forcing an artificially short timeline. If [GOAL] implies a specific outcome with real prerequisites I haven't mentioned, such as a junior developer job typically expecting a portfolio and some familiarity with Git and basic data structures, name that expectation directly and confirm the roadmap actually builds toward it by its final weeks, not just toward general familiarity with a language. If I report back partway through that a specific week took much longer or much shorter than estimated, adjust the remaining weeks' pacing based on that actual data point instead of leaving the original estimates untouched.
Range: 2 - 20
Use this prompt anywhere
10,000+ expert prompts for ChatGPT, Claude, Gemini, and wherever you use AI.
Get Early AccessMost coding roadmaps assume a full-time pace nobody juggling a job, classes, or a family actually has. This tool builds a week-by-week plan sized to the real number of hours you have available, starting from your actual current level instead of a generic zero point.
Set [CURRENT_LEVEL], describe [GOAL] in plain language, a junior developer job, your own app idea, passing a CS course with real understanding, and set [TIME] to your honest weekly hours. You get eight to twelve weeks, each with a specific topic, one concrete thing you should be able to build or do by the end of it, and an hour estimate that adds up to your real weekly time, ordered so nothing shows up before its prerequisites are covered. Every third week folds in a small integration project instead of another isolated lesson. Under 5 hours a week, the roadmap says so directly and extends the timeline honestly instead of cramming content into an unrealistic schedule.
Goals with real prerequisites, a portfolio and Git familiarity for a job search, for example, get named directly and built toward by the final weeks. Report back that a week ran long or short and the remaining pacing adjusts to match. Once you're mid-roadmap, scope real practice with the code-along project idea generator, or understand how to use AI tools without skipping the learning with the AI-assisted coding explainer for students.
Build it in the Dock Editor to keep your roadmap and progress notes in one place.
Once you have this open in the Dock Editor, ChatGPT, Claude, or Gemini, choose [CURRENT_LEVEL] honestly, from complete beginner through comfortable with fundamentals, so the roadmap starts where you actually are.
Fill in [GOAL] in plain language, a job, an app idea, a course, so the roadmap builds toward something specific instead of general familiarity.
Set [TIME] to the hours you can actually commit weekly, not an aspirational number, so the pacing stays realistic and sustainable.
Each week has one specific topic, a concrete thing to build or do by its end, and an hour estimate, ordered so nothing appears before its prerequisites.
Tell it when a week ran long or short and the remaining weeks' pacing adjusts based on that real data instead of staying fixed to the original guess.
Get a roadmap that actually fits 5 to 10 hours a week instead of one built for someone with no other obligations.
Get one clear, ordered path instead of a dozen conflicting resource lists with no sense of what to do first, second, or third.
Build a self-paced plan that reinforces course material with concrete weekly build goals instead of passive review.
Get a roadmap that names the real prerequisites a goal like a junior developer job actually requires, portfolio and Git included, and builds toward them directly.
Discover more prompts that could help with your workflow.
Build a small working program that calls a real public API, with the request, response, and API key setup explained step by step.
Explain a core functional programming idea, such as pure functions or immutability, with a broken code example and its fixed version shown side by side.
Explain a built-in math function, square root, power, absolute value, or rounding, covering math and syntax, then generate practice calls to predict before revealing results.
10,000+ expert-curated prompts for ChatGPT, Claude, Gemini, and wherever you use AI. Our extension helps any prompt deliver better results.