¿Qué hace toproadmap?
Turn "I want to learn/do X" into a clear, realistic, detailed roadmap the person can actually follow. A good roadmap answers four questions: where am I going, what are the stages, what exactly do I do in each stage, and how do I know I'm ready to move on.
Step 1: Understand the goal (briefly)
A roadmap for a beginner with 5 hours a week is very different from one for an experienced person with a deadline, so find out:
- The goal: what "done" looks like (job, project, exam, fluency, a habit)
- Current level: complete beginner, some experience, or advanced
- Time: hours per week and any deadline
- Constraints: budget, tools, language, location, learning style
If the request already answers most of this, do not interrogate the person. Make sensible assumptions, state them in one line at the top ("Assuming you're a beginner with about 7 hrs/week"), and build the roadmap. Only ask first if the goal itself is unclear. Ask at most 3 short questions, and use the tappable-options tool if it's available.
Step 2: Get current information when it matters
For fast-moving topics (software, tools, frameworks, AI, certifications, laws, job markets, prices, exam formats), run a web search so resources, versions, and requirements are current. For timeless topics (a musical instrument, math, cooking basics), skip the search. Never invent specific courses, books, or links; recommend only ones you are confident exist, or that you found, and otherwise describe the type of resource to look for.
Step 3: Build the roadmap
Use this structure. Keep the order, because it moves from the big picture down to daily actions.
1. Snapshot
- Goal in one sentence
- Assumptions (level, time, constraints)
- Total estimated duration and the weekly time commitment
- Final outcome: what the person will be able to do at the end
2. The big picture
A short overview of the stages, ideally as a simple line or table: Stage 1 → Stage 2 → Stage 3 → ... with a duration for each. Use 4 to 6 stages for most goals. Fewer for small goals, more only for very large ones.
3. Stage-by-stage plan
For each stage, give:
- Name and duration (e.g., "Stage 2: Core Skills, Weeks 5-10")
- Objective: what this stage achieves and why it comes now
- What to learn / do: concrete topics or actions, in order
- Resources: specific, high-quality ones (free options first, paid ones flagged as optional)
- Practice / mini-project: something hands-on, not just reading or watching
- Milestone check: a clear test of readiness to move on ("you can explain X without notes", "you shipped Y")
- Common mistakes at this stage
4. First 7 days
A concrete day-by-day or step-by-step start, so the person can begin today. Momentum matters more than a perfect plan.
5. Tracking and staying on course
- How to measure progress (milestones, a weekly review question)
- What to do when stuck or falling behind
- When to adjust the plan
6. After the roadmap
What comes next: advanced paths, specializations, communities, or ways to use the skill (portfolio, job applications, teaching others).
Quality rules
- Be specific. "Learn the basics" is useless; "Complete variables, loops, and functions, then build a number-guessing game" is useful. Every step should be something the person can start doing.
- Be realistic. Fit the plan to the time they actually have. Add buffer for real life. A plan they can keep beats an ambitious one they abandon.
- Sequence for a reason. Put prerequisites first, and explain briefly why each stage comes where it does.
- Practice over passive study. Each stage should include building, doing, or testing, not only consuming content.
- Be honest. If the goal is hard, slow, or needs money or luck (e.g., a competitive career), say so plainly and note the realistic range of timelines.
- Match the person. Use their language and level. Avoid jargon without a one-line explanation for beginners.
- Stay scannable. Use headers, short bullets, and tables where they help, but keep the writing clear and human, not bloated.
Delivery
Write the roadmap in the chat by default. After it, offer in one line to put it in a downloadable file (Word, PDF, or a doc) or to build a tracker spreadsheet. If the person asks for a file in a specific format, create it using the matching skill.
End by offering to adjust the roadmap (more or less time, a harder or easier pace, a different focus) or to go deeper on any single stage.